@Trampa I have seen another case of this issue today.
Seems that @abusfullofnuns is having a similar issue. What’s more concerning is that I think he is trying up upload over SWD and is still experiencing the issue.
Hopefully this as an issue with the upload function on the tool rather than a firmware issue on the VESC. If it’s a firmware issue and it’s stopping SWD uploads then there are people bricking esc’s by updating.
@Trampa can you confirm that you and Ben are aware of this?
Thanks Q. I’m am indeed experiencing said behavior. I’ll attempt this again today and report back results.
What is the HW and what was the old FW?
For me it was an Escape going from 5.1>5.2. One worked and one did not. I was not able to get it updated through can or directly connected. I also was not able to get it to flash through swd with a known good 5.2 Escape. It gives the same time out error regardless of function. I have not had experience flashing through swd before but did not use the boot loader tab on 5.2 as its new and I only followed BV instructions for older vesc tool.
Additionally, I tried updating a TB6 last night. It also failed and locked into the erase time out error. I used same cable and a good tb6 with 5.1 to repair the bricked tb6. Obviously using vesc 2.06. I can’t guarantee there wasn’t a power error during the initial tb6 fw update. I noticed this morning that the tb6 powers on just by connecting the usb. It was 2am when I gave the tb6 a shot(after bricking escape) and I may not have plugged in the loop key to give full power. Either way, that one was salvaged this morning. Will try escape next.
Wrong, I was thinking of the firmware section and not the swd programming session. Like I said, it was way late.
That was the same with the first batch of escapes and was caused by R1 being populated. It was later removed. It’s usually not good if the vesc based esc powers on by usb only.
If it powers up via the USB, it can fry your PC or Laptop or ESC via GND loop. So that is a problem with the PCB, since the voltage line should not be connected on the PCB.
I would flash them via SWD prog. Make sure the cable is short ( about 8cm)
Watch minute 5 onwards
Thanks, Frank. I did use this method and used a very short cable. It may be 9cm instead of 8cm. Process worked on TB6. Does not work with Escape. For shits and giggles,I downgraded the good escape to 5.1 and tried to flash with 2.06. Still same error.
Are you saying that I should try with a programmer instead of another vesc based esc?
You should reset the chip. Attach a cable to RST and one to any GND pin. Just before flashing, let the cables touch for a short time. Timing is important and you probably need several tries.
Thanks. I’ll play with it a bit.
In our tests we got better speed with FOC.
This wasn’t always the case (2years ago)?
BTW, we are now testing the KICK ASS startup for you guys. So far BV is happy with the results and our crew is itching to take the first FW upgraded boards into the woods.
No noise, full torque, no chance of failing sensors.
No luck with first five attempts at resetting the chip. Any tips on timing and how long to short?
Edit to add that I used ground on comm plug. No idea of uart is enabled but assume it won’t matter.
A fraction of a second before you flash. Just a short touch.
0 for 20. Think this one is a shitty boat anchor.
Just want to add to this conversation that i couldn’t update either vesc 6 from 5.1 to 5.2 over bluetooth, but after updating the bootloader on both, it worked flawlessly. I have no idea from what version bootloader it changed or even if it flashed the exact same file but it seems to have done the thing
For the ones who want to try some kick ASS sensorless startup:
https://vesc-project.com/node/2859
On the VESC 6 MKV and HD it will perform best, but also older designs will have a much nicer startup now. Just run a detection and switch to sensorless. Nothing else is needed.
This is Beta software for the ones who like to play around a bit and test the bleeding edge stuff.
