I'm trying to re-use some old 4.7 VESCs for my brother's board we are building together.
It will connect correctly, but warns the firmware is too old, so i select the correct "46 & 47" in Firmware, then VESC_default.bin.
It seems to upload correctly - the progress bar goes to about 100%, but then quickly flashes a red error message in bottom right:
Serial port error: The I/O operation has been aborted because of either a thread exit or an application request.
Appreciate any suggestion on steps to get this to work?
Thx All!
After the upload is done the vesc should reboot, and then that error is shown since the serial port disconnects then. What happens if you wait until it boots? Does it boot back into the old firmware?
Thanks Ben! I've left everythign powered/connected for a few minutes after trying to update... It will not let me reconnect after the error, when i try it says: Invalid serial port: \\.\COM5.
When i disconnect power and reconnect power it lets the VESC Tool reconnect, but is still the old firmware.
It could be that the bootloader is missing. Is this vesc from my very first batch from a long time ago, or where did you get it? I think I put the bootloader on them back then.
I looked at the bootloader tab in the firmware section of the new VESC Tool... but wasn't sure.
They are pretty old - unsure how to check if they have bootloader or not? The firmware on them was 1.10 to give a bit of a timeframe last they were used.
I have a STLink v2 and can connect through it, or any steps for updating bootloader?
Thx!!!
You can try the bootloader tab first. The stlink will always be able to recover the bootloader if that fails.
The problem with the bootloader tab is that it is kind of a hack that I added. If there is no bootloader writing a new one is no problem, but if there is one trying to overwrite it will most likely mess up the bootloader as it has to be erased first and there is no way to tell the old firmware to erase the bootloader section in flash. It will correctly turn ones into zeros in flash, but not zeros into ones. If there is no bootloader all bits in flash are ones from the factory.
reconnecting to it, going to the firmware section of the VESC tool, then the bootloader tab... I get a pretty serious warning about NOT updating bootloader if one is already present:
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?
So, i am fine updating if i can confirm these are missing bootloader - any way to confirm bootloader is missing first?
And do this update (once bootloader missing confirmed), over USB, or via STLink?
I'll give it a shot. Worst case it seems like i can connect the STLink and get it sorted?
You can do the update over usb if the bootloader is confirmed missing, and as far as I can tell that seems to be the case. The worst thing that can happen is that you have to use the stlink and download the bootloader file from github. The reason for the warning is that most people don't have an stlink and messing up the bootloader over usb means they have to get an stlink and figure out how to connect and use it.
I think we are working now!
Just to be clear - this is NOT a maytech VESC - i have no idea how old these are... hw 4.7, and not the ones i got from you Ben (i remember those 4 were green PCB's).
Regardless - it seemed a bit fiddly, but after i forced it to update the bootloader - restarted the VESC Tool, and re-connected it saw the 3.26 firmware for 4.7 hw!
Ran a quick detection and both motors are spinning and talking with the VESC Tool! I will now reconnect to full voltage (moved down to 3s while testing), and run detection and configure.
Super excited to get my brother ROLLING!
Thank you Sir!
Nice! Let me know how it goes. It is nice to see when old hardware gets a new life from a software update.
aha, i have probably one of the first hw 4.6 from the good old days.
There were some wrinkles, but we got it sorted out! We did the "maiden" ride last night/this morning at 230AM! So excited we did a quick 2 or so miles around his neighborhood.
Speaking of new life - we electrified an old Bustin Maestro... (which was my x-mas gift to him 2010/2011'ish!). Top mounted as it's a drop through, but the wedged nose/tail makes it a bit squirrely at speed, but *SUPER NIMBLE* at lower speed. He's going to dial in some stiffer bushings and be careful (he's good about wearing gear and has ridden that board A TON over the years so super comfy on it).
Dual non-sensored R-Specs (6355 190kv), 97 clones, Pink badwolf v2 GT2b! 8s (4s x 2) 10Ah 10C Multistars (yes i know - i got them and didn't use, so he is until they puff).
Moving up from his koowheel (surprisingly nice even w/ me on it - just not up any real hill w/ my weight) - he was giggling like a school kid accelerating up hills! It helps he's almost 100lb lighter than me... but still great.
SO SO AWESOME!
Thank you Ben for helping get him rolling on this new old setup!!!
How do we put an image in this forum? I tried [img] /img], and![]()
/img> (skipping [ &
That is normally the case,
but not in STM32. STM32 allows programming from 0xff to <anyvalue> and from <anyvalue> to 0. So you can't use a bit as 8 bitflags, 0xff -> 0x7f -> 0x3f -> 0x1f -> 0xf ->0x7 -> 0x3 -> 0x1 -> 0x0. This won't work on STM32. The only option is 0xff -> 0xaa -> 0x00.ok scratch that. I was talking about STM32 F0. On F4 the normal standard flash behaviour is implemented.
EDIT: I used strikeout to mark the text that is not true. This renders fine in the editor, but when posted it is totally invisible.
Thanks Frank - i wanted to run 12s (still not thinking FOC is reliable enough on old hw) - at least unlikely w/ 190kv motors.
Just to be clear on Ted's setup - what kv motor? I'm guessing one of your low kv (136/118)?
I am trying to first time program, it appears I need updated firmware but when I update I get an arrow message that the operation has been aborted because of a thread exit or application request. Any help would be great thanks