Code:
{
"board_name": "test_PWM_GPIO",
"baseclass": "firmware.boards.RV901T",
"clock_frequency": 50000000,
"ethphy": {
"tx_delay": 0
},
"etherbone": {
"ip_address": "10.0.0.10",
"mac_address": "0x10e2d5000000"
},
"gpio_in": [
{
"name": "rapid_override_reset",
"pin":"J601:7"
},
{
"name": "feed_override_reset",
"pin":"J601:8"
},
{
"name": "spindle_override_reset",
"pin":"J601:9"
}
],
"gpio_out": [
{
"name": "rapid_override_active",
"pin":"J601:15"
},
{
"name": "feed_override_active",
"pin":"J601:16"
},
{
"name": "spindle_override_active",
"pin":"J601:17"
},
{
"name": "stepgen_shared_enable",
"pin":"J600:39"
}
],
"pwm": [
{
"name": "test_otherwise_no_compile",
"pin":"J601:36"
}
],
"stepgen": [
{
"name": "stepgen_0",
"step_pin": "J600:38",
"dir_pin": "J600:36",
"soft_stop": true
},
{
"name": "stepgen_1",
"step_pin": "J600:34",
"dir_pin": "J600:32",
"soft_stop": true
},
{
"name": "stepgen_2",
"step_pin": "J600:37",
"dir_pin": "J600:35",
"soft_stop": true
},
{
"name": "stepgen_3",
"step_pin": "J600:33",
"dir_pin": "J600:31",
"soft_stop": true
}
],
"encoders": [
{
"name": "rapid_override",
"pin_A": "J601:7",
"pin_B": "J601:8"
},
{
"name": "feed_override",
"pin_A": "J601:9",
"pin_B": "J601:10"
},
{
"name": "spindle_override",
"pin_A": "J601:11",
"pin_B": "J601:12"
},
{
"name": "MPG",
"pin_A": "J601:13",
"pin_B": "J601:14"
}
]
}
While developing I found a few bugs which need to be resolved: when no GPIO, PWM or Stepgen is defined, the firmware crashes as it is trying to create a register with a width of 0. At this moment at least one of each have to be defined. When the encoder driver software is finished, I'll tackle this problem as well.
Another nice feat: I'm making a hat for the RV901T, so all the stepper drives, switches and user input can be connected easilty. This board also contains a FTDI232 chipset so it can be reprogrammed on the fly.
). This new module has a different layout then the previous layouts, making it faster and more concise to develop;
. Have made some changes to the firmware, so I have to cross-reference with the 5A-75E to see whether the problem is board specific or that I broke the firmware...
