The following hardware and tools are used.
VESC6MKV (FW version:5.3)
VESC Tool Free (version:3.01)
After writing app config to the VESC６MKV using the VESC tool, reboot the VESC6MKV will not retain the written app config and will initialize it.
*If I don't power down the VESC6MKV, it will work with the app config I wrote.
Is there any way to fix this?
Regards,
Maybe you should try to fully erase and flash the unit. Do you have a second VESC to hand? Than you could program the device via SWD PROG.
Thanks for the advice.
I tried to erase & upload the firmware from SWD Prgorammer of VESC Tool by referring to the following URL.
https://www.youtube.com/watch?v=PFFiVxFHDM4
As a result, erasing the flash seemed to be successful, but it showed a flash write error.
Now, the VESC that caused the flash write error is in the following state.
1)Only the blue LED on the main unit lights up, and the green LED is off.
2)Unable to connect via USB. (COM port is not recognized).
3)Cannot connect via SWD Programmer.(At this time, a part of the log data displayed in VESC Terminal of VESC Dev Tool is shown below.)
~Log data from here
AP transaction in progress. Target may not be usable.
AP 0: IDR=ffffffff CFG=ffffffff BASE=ffffffff CSW=ffffff48
AP transaction in progress. Target may not be usable.
AP 1: IDR=ffffffff CFG=ffffffff BASE=ffffffff CSW=ffffff48
AP transaction in progress. Target may not be usable.
AP 2: IDR=ffffffff CFG=ffffffff BASE=ffffffff CSW=ffffff48
AP transaction in progress. Target may not be usable.
AP 3: IDR=ffffffff CFG=ffffffff BASE=ffffffff CSW=ffffff48
AP transaction in progress. Target may not be usable.
AP 4: IDR=ffffffff CFG=ffffffff BASE=ffffffff CSW=ffffff48
~Log data up to here
It seems that the internal firmware has been erased.
The VESC that caused the flash write error is in the state described above and cannot be connected.
Is there a solution?
Did you use a programmer or a second VESC device?
I worked with two VESCs.
The following figure shows the connection diagram between PC and VESC and the operation procedure of VESC Tool at that time.
*No.1 VESC and No.2 VESC are powered from different batteries.
I have three VESCs, and as a result of rewriting the firmware of No.2 and No.3 using the same method, both of them stopped working
Make sure to press Disconnect after the procedure (next to your number 5). So that is Step 6!
I had the same problem with configuration files being lost on original hardware. Some smart people are investigating this rare issue on the discord right now. I still don't know why this happens or how to stop it from happening.
Sounds like you tried to fix that with the vesc to vesc swd program procedure, which failed and now you can't even connect to swd in the first place and have two bricked vescs. Been there. If you still have at least ONE good vesc to use, this information may help: https://vesc-project.com/node/3461
Hello ,
I have the same ADC configuration missing after reboot problem. I tried full flash erase using stlink, although flash erase and firmware upload successful, problem of ADC still existing.
eguven