Okay, so I uploaded the bootloader as explained in the tutorial.
However, I didn’t use the .hex file he linked since the link is broken, so I used this one instead:
Now the VESC shows only Blue LED light (there should be also a Green one) and when I plug
the VESC to my PC nothing happen, it can’t be recognized. What’s wrong?
SWD Prog is the solution.
Go to Benjamin Vedders YouTube channel and browse for the SWD tutorial. Minute 5:30 onwards…
I will take a look at that, but I think the issue is that I uploaded a .hex file that only contains the bootloader and has no firmware on it, does it make sense?
When update firmware,with Flipsky esc , is better also to disconnect motors and sensors …
It wasn’t connected to any motors or sensors.
With swd prog you upload the FW and bootloader in one hit. You need a working ESC though. That ESC can be bricked, but you need to be able to connect to it. The ESC becomes a programmer to program other ESCs or dongles or …
Edit: YES! I shortened the cable to 15cm and now there is a connection! My VESC is back to life!!!
I’m receiving the following error when I try to connect:
What can be the reason for that? Here is the cable I made:
And also here is the diagram for the Flipsky Dual VESC:
Not quite sure why it can’t be connected. Could be the wires are too long?
8 cm cable is about the max. And maybe the SWD on the Flipsky ESC has no GND, so you need to connect to another GND pin.
15cm worked fine!
When it comes to VESCs, I guess size do matter 
