Hi,
When I connect the VESC-6 to vesc-tool I am informed that the VESC has too old firmware and that the tool will only allow firmware update.
When I go to the firmware page I see Hardware version 60 with firmware VESC_default.bin in the two Included Files panes. I go to apply the firmware which it uploads to the device, taking less than 10 seconds and then the VESC disconnects with only the blue power light lit on the VESC. The tool claims fw upload done.
After I power cycle the VESC and try to connect, I am told the firmware is still too old and it seems the firmware update did not apply.
In each case, when I go to the firmware page the connected VESC firmware is 3.24 and the tool claims it only supports 3.25.
I have tried both in Windows and Linux with the same result.
I see other firmwares in the non-default firmwares view but none of them will update the firmware version on the connected VESC.
The tool version is 0.77.
Thanks,
Neil.
I am also having this problem, seems a simple update will fix, cant wait to get everything working!
OK thanks for confirming! Hopefully it's just something easy to fix then.
Cheers,
Neil.
Same problem.
Can we download this 3.25 firmware version from anywhere?
Perhaps if we upload this firmware as "Custom file" it solves the problem?
I had a look, and it seems like the test bench did not upload the bootloader properly. I had a look at the code, and I think it is possible to upload the bootloader from VESC Tool as it can write to any location in the second half of flash memory when storing the firmware for the bootloader, including to the location where the bootloader is located. The problem is that VESC Tool cannot erase the flash memory at the bootloader location, but I think the flash memory is already erased when the stm32 comes from the factory. If this solution works I should be able to update the VESC Tool download later today, which will have a "install bootloader" menu option. Otherwise, the backup solution is to upload a VESC Tool version that supports FW 3.24 and send stlink v2 usb adapters to the beta testers so that everyone can upload the bootloader.
I just unpacked the VESC6 and found this issue. Luckily I have a ST-link laying around and was able to fix it.
I flashed the VESC4 bootloader ( wit the ST-Link utility ) and did the upgrade from 3.24 (the firmware that was shipped) to 3.25 with VESC-TOOL V0.77 .
It's a happy VESC-Tool now :)!
Any Eta on when the problem will be fixed for all us not ST-Link owners :P ?
I have plenty of STLinks here. So if it comes to that, no need to send me one.
Given how much STM32 stuff I have around here an STLink2 looked like a good thing to have around, so one arrives today.
Same problem here.
The last time i did this, i did it in linux (which i'm a noob) following Ben's copy/paste instructions...
How easy is it to do in the new tool if we have the STLink already?
It would be as easy as last time.
I think it is not possible to fix a not available boot loader. But lets see what Benjamin the magician does. I think the fastest would be uploading the appropriate VESC Tool for FW3.24.
Or you just send to all of us the Raspberry Pi with the touch interface, so we can flash the new firmware ourselves. :D (Just kidding if it is not obvious)
But I think that most serious BETA tester have a STLink laying around. That is what set them apart form "normal" VESC end users.
I got a box of VESCs today and had a chance to experiment a bit. Since the flash memory is erased by default I was able to add a hackish way to VESC Tool to upload the bootloader by using the firmware upload command and adjusting the offset. I have tested this on a few VESCs, and it seems to work. The new versions of VESC Tool are compiling now, and should be ready for download in 20 minutes or so.
The change is that there is a bootloader tab in the firmware page of VESC Tool where the bootloader can be uploaded. So, to get the new VESCs running, first go to the bootloader tab in the firmware page and upload the bootloader, then go back to the included files tab and upload the firmware. After a reboot everything should work.
I'm sorry about the inconvenience. The source of the problem was that I had a small typo in the test bench that would upload the bootloader to the wrong address and then overwrite it with the firmware.
I confirm it worked for me. I have 3.25 firmware and ESC is working!
Amazing that it worked. Great to hear that. You are now a proven magician Benjamin. :D
Hi Frank, many thanks to you and Benjamin for the the swift response and fix! I'm up and running now so will be out on my emtb tomorrow and start giving some feedback.
Sanjoy.