Hi, i have a old 4.12 vesc. The vesc works since 2017 with FW3.29.
Today i want update to 5.02. My steps below (Ubuntu 20.04 & STLinkV2:
git clone https://github.com/vedderb/bldc.git bldc-firmware
Edit conf_general.h ->
#define HW_SOURCE "hw_410.c" // Also for 4.11 and 4.12
#define HW_HEADER "hw_410.h" // Also for 4.11 and 4.12
make upload
** Programming & Verified OK **
But now i cant connect to the Controller.
Hi,
You could flash bin file FW3.29 via ST-Link, first, then Vesc-tool could connect. Next, via Vesc-tool bootloader to be updated. Wait 15 seconds, and reconnect. Finally, via Vesc-tool fw to be updated, Wait 15 seconds again.
Hi, back to FW3.29 works.
I want to use later my custom app (works fine in FW3.29), but the compiled FW 5.02 does not work (without my custom app)
Is it enough to modify the "conf_general.h" to use FW5.02 with HW 4.12?
Thanks
Edit: sudo apt-get install gcc-arm-none-eabi binutils-arm-none-eabi libnewlib-arm-none-eabiIs
Is this the right compiler?
https://vesc-project.com/node/310
Hello, i can not use the ppa team-gcc-arm-embedded on ubuntu 20.04.
The gcc-arm-none-eabi does not compile a runnable firmware. Should i try a ubuntu 18.04 virtualbox vm?
right
What abour downloading a different version of the toolchain from the arm website?
This problem seems to be cropping up more and more now as people are often trying to compile on newer versions of the toolchain.
I have the same problem as sirAnton. Where can I find a compiled version of a recent firmware that should work? On my toolchain (ubuntu 18.04) I can use make without problems for the newest branches, but it fails if I checkout to fw3.29 for example.
You can find built versions of all the firmwares on Benjamin's github.
Awesome, is this the file you are refering to?
https://github.com/vedderb/bldc/blob/master/build_all/410_o_411_o_412/VE...
I am using the hw-version 4.12.
How can I upload a bin file to the VESC? So far I have just use "make upload" from the bldc folder. But no extra commands to specify which file, etc.
I am using an ST-Link to access the SWD-port.
I have also tried to use a healthy VESC in order to reflash the bricked one as explained here by Benjamin. But this always resulted in an erase time out error.
Do I need to use the openocd command? If yes what is the exact command I need to use?
Thanks for your help!
for those building for HW:60? what hardware are you choosing? it surely is not one of:
is it this one?