Hi,
I have a vesc from the "torque" vesc from diyelectricskateboard dot com. I'm controlling the vesc over can and needed to add a custom packet, so I clone the vesc git repo, added my function, changed the following preprocessor define:
`#define HW_VERSION_410 // Also for 4.11 and 4.12`
And then did a `make`
I used the vesc tool to upload the resulting binary from the build directory to the board. I waited about a full minute after the upload and then powered the board down. After this, I powered the board up and there are no signs of life other than the blue LED. With the board connected via USB, the usual USB Vcom port did not enumerate.
After this, I used my STLinkV2 and the STLinkV2 utility to erase the chip completely and then I loaded the bootloader hex file from the bootloader repo (After cloning and building it) onto the board. Again, there were no signs of life.
I'm guessing I've missed something, but at this point I'm not exactly sure what. Any ideas?
Thanks,
Chris
Maybe try compiling in chibi studio?
An update:
Messing with the code and uploading it, the stm32 is definitely running code. I can turn LEDs on and off. But the USB vcom port thread isn't starting so obviously I cannot communicate with the vesc over usb. any ideas why this would be?
Has the latest version "ChibiStudio_Windows_2020-04" be proven to compile this VESC firmware ??
@chris1seto have you found a solution to your problem?
I also seem to not get a USB connection when i flash the firmware after compiling myself, although everything works perfectly when flashing the prebuilt FW from the repo...
Ditto. Are you building on windows with chibi studio? Seems like this tool chain no longer works, someone smarter then I hopefully figures it out.