# how update from 2.18 to the latest firmware

17 posts / 0 new
aysubscriber@ic...
Offline
Last seen: 5 years 3 months ago
Joined: 2017-10-01 19:35
Posts: 12
how update from 2.18 to the latest firmware

Hi, for a couple days I try to figure out how to upgrade the firmware. I have 4.12 vesc with 2.18 fw.

Could you give me clear direction how to upgrade to latest fw?

This question is rized becouse the latest bldc-tool I uploaded from benjamin git-hub (don't know how to see the version of the bldc-tool ) can upgrade to 2.18 fw.

The latest vesc-tool from vesc-project.com show message it can work properly only with 3.x version of the fw.

I tried to upgrade the fw with latest vesc-tool, it show upload of the fw completed and disconnected vesc.

After manual rebooting it (poweroff , poweron) the vesc-tool show the version of fw don't change it is 2.18 fw.

Probably there is some intermediate steps what I miss how to upgrade fw from 2.18 to latest 3.x version of fw.

Thank you.

ThierryGTLTS
Offline
Last seen: 4 years 4 months ago
Joined: 2017-09-06 14:18
Posts: 116

Did you simply use the small button with a "up arrow" (bottom of firmware page) to load from the VESC and check the version.

Retry and perhaps you'll 3.xx version.

That's what happened with mine :-)

Have a Nice Day.

Thierry

aysubscriber@ic...
Offline
Last seen: 5 years 3 months ago
Joined: 2017-10-01 19:35
Posts: 12

I pushed small button "up down arrow" and saw uploading process (green bar fulfill and shown "FW Upload Done" )

after that I noticed my vesc became not connected.

I manually rebooted the vesc

then noticed the version didin't change it still 2.18

there is an screenshot below

Linux and windos in virtual machine have same problems.

Probably this because I use parallel desktop.

frank
Offline
Last seen: 3 days 22 hours ago
Joined: 2016-12-27 20:19
Posts: 822

Does your HW 4.12 have a bootloader?  Is your ESC fom Maytech? No bootloader as standard!

If you have no bootloader aboard you can update it from the bootloader tab.

Remember: If it has a bootloader this procedure will kill your existing bootloader and you will need an ST-Link V2 to fix the issue. So make sure if you have a bootloader installed otr not.

VESC-Tool usually tells you that when you connect.

Frank

Philthefer
Offline
Last seen: 2 years 10 months ago
Joined: 2017-10-16 15:29
Posts: 1

i have exacly the same problem when i try to download the firmware , this message appear in red at the bottom of the page : serial port error the I/O operation has been aborted because of ether a thread ext or an application request.my esc is a maytech

pek
Offline
Last seen: 1 year 5 months ago
Joined: 2017-10-10 20:20
Posts: 1

here is the good manual http://vesc-project.com/node/179

GunnarW
Offline
Last seen: 1 month 2 days ago
Joined: 2017-09-06 13:50
Posts: 8

(I have a Phoenix VESC 4.12 FW 2.18 which comunicate with BLDCTOOL via VESC-COM13 without problems.)

But I have the same problems updating with VESC-TOOL as the other guys...

Pc is a laptop workstation running W7 64bit.
Without VESC-TOOL running I connect the VESC to the serial port.
The device manager tells via sound and text that the device is connected to STMicroelectronics Virtualport COM13.
Starting VESC-TOOL and connecting to the VESC-COM13, limited mode (what "limited mode" means is beyond me, googling

does not give any clue, but I think it is the problem)
Connection established and I get the message that "The connected VESC has too old firmware. etc
Go to Firmware
Select hardware 410&411&412 and firmware VESC_default.bin
Clicking on down arrow and the green bar moves to the right and at the end the connection disconnects instantly
with the message "Serial port error: No such file or directory"

The only way to establish connection again is to disconnect and reconnect the battery to the VESC. But the firmware is still the

same 2.18 as before trying to update, and the VESC still works as before.

The above has been tested with another laptop workstation running W7 32bit with exactly the same result.
Surely there must be some people here that have the knowledge to guide us unknowing in the right direction.
The devicedriver is downloaded directly from ST Microelectronics website... and the VESC-TOOL is 0.82

And the note about the tutorial above this does not help this case. I used it the very day i appeared in this forum and I appreciate it in all other regards.

benjamin
Offline
Last seen: 6 days 16 hours ago
Joined: 2016-12-26 15:20
Posts: 487

Sounds like your VESC is missing the bootloader. You can upload it from the bootloader tab on the firmware page, and then do the same thing.

GunnarW
Offline
Last seen: 1 month 2 days ago
Joined: 2017-09-06 13:50
Posts: 8

According to this message my VESC does have a bootloader

[img]https://up.picr.de/30690469xh.png[/img]

Edit: The links does not seem to work, but the message says "The connected VESC has too old firmware. Since the connected VESC has firmware with bootloader support , it can be updated from the firmware page. Until then, limited communication mode will be used where only the firmware can be changed." Which is just what I have tryed a number of times... and what does not work.

Is it still advisable to load the bootloader supplied with VESC-TOOL considering the message below. There are threads here from people who have done this and got themselves into trouble...

[img]https://up.picr.de/30690468mi.png[/img]

And this message says: "This will attempt to upload a bootloader to the connected VESC. If the connected VESC already has a bootloader this will destroy the bootloader and firmware updates cannot be done anymore. Do you want to continue?"

I answered NO to this question but that leaves me on square 1 again. What to do???

benjamin
Offline
Last seen: 6 days 16 hours ago
Joined: 2016-12-26 15:20
Posts: 487

The first message is always shown, but it does not mean that the bootloader actually is installed. If the progress bar in the firmware upload finishes and the vesc does not reboot after 10 seconds AND it boots back into the old firmware after a power cycle, then the bootloader is most likely missing. It sounds exactly like what happens to you, so I think you can upload the bootloader safely.

GunnarW
Offline
Last seen: 1 month 2 days ago
Joined: 2017-09-06 13:50
Posts: 8

That solved my problem! Thank you very much!

aysubscriber@ic...
Offline
Last seen: 5 years 3 months ago
Joined: 2017-10-01 19:35
Posts: 12

I contacted with my seller, he said this my vesc is mytech and it has blocked bootloader and I have no chance to open bootloader on my side.

Have no Idea what to do.

hexakopter
Offline
Last seen: 1 month 2 weeks ago
Joined: 2017-05-24 12:13
Posts: 95

Flashing the bootloader manually with an STLink should always work when everything else failed. But normally I hear that maytech ESCs don't have a bootloader installed and you can choose the new option in VESC Tool to flash without a bootloader.

Tampaesk8er
Offline
Last seen: 5 months 3 weeks ago
Joined: 2017-10-18 22:03
Posts: 4

I’m having the same issues with my Maytech vesc, scared to install bootloader cause of the warning, dont want to mess up my vesc.

flatonmyface
Offline
Last seen: 5 years 5 days ago
Joined: 2018-01-18 12:05
Posts: 1

Hey GunnarW, I was having the same problem as you were. I read most of the comments, and YES I have been frustrated with this update firmware stuff as well.

I got the same message as you about having a bootloader. Turns out I don't. My VESC units (I have 3) http://e-greenmotion.com/index.php?route=product/product&path=111_125&pr...

I bit the bullet and did my spare. Do OK and YES where necessary with the screen prompts.

1. Plug it in, USB and power. 2. Goto the Bootloader page and use the line with 411 in it, hit upload, it's quick. 3. After 15 seconds power cycle. 4. Connect and go to the firmware page and have a go updating firmware. First time fails for me every time. 5. Power cycle VESC again. 6. refresh COM port and connect again, do the firmware again. It will upload as usual, then disconnect as usual. 7. Power cycle after 15 second. 8. Power up and connect, should be good to go.

I followed this process that I just wrote for my third unit and it went through with no real issue.

That's 3 successful upgrades, except it now tells me my hardware version is 4.10 not 4.12, Eh who cares.

I hope this helps you or anyone else.

roteron
Offline
Last seen: 4 years 12 months ago
Joined: 2018-02-05 12:28
Posts: 1

I had the same problem, downloaded the bootloader as per Benjamins advice,  then went back to firmware and all came good...thanks

JohnDip67
Offline
Last seen: 1 year 8 months ago
Joined: 2021-04-08 18:42
Posts: 1

I was having the same setup problem and so I searched and searched and found this 3+ year old thread,  thanks, it solved my same issue.