Reflashing an ODrive after losing its firmware

Want to get your ODrive working again?
This only takes a few minutes and is well worth knowing just in case you come across this common dilemma.
Why does this happen? Occasionally when prototyping with an ST Microcontroller based board the firmware can go amiss, although it's hard to know what caused it.
These devices are very stable and once permanently in a project have no trouble with firmware.
Well I wanted to put together this video to help others in the same situation, so here's my experience getting the device up and running again.
Lightning Bolt on Thumbnail: -
Nature vector created by macrovector - www.freepik.com
www.freepik.com/vectors/nature
#WelcomeToMyGarage
#dev255
#ODrive

[@Simcadepro]

i love the term sounds like water thru a pipe to describe the motors are engaged

[@astral2040]

I was looking for a Video on Flux capacitor optimisation guide, but this came in handy. Nice Video helped alot.

[@Dev255]

Great Scott, I'm glad it helped someone 😉👍

[@bandasaikrishna1835]

Thank you for this video. This saved my 2 odrive controllers.

[@padstar2007]

Thanks for sharing this video,

[@Dev255]

No dramas, thanks for lending me your now famous ODrive for the video 😉

[@Dangineering]

Thank you so much for this video, but I am still having trouble. I have followed all the steps as you said, but when I go to use the Dfu tool it doesn't autofill in the information of the Odrive that was forced into DFU mode. Instead if remains greyed out and I can't proceed any further. I have done everything to force it into DFU mode, including the dipswitch and grounding GPIO pin 6. The computer does recognize something is being plugged in because in the device manager it lists it under other devices as "STM32 BOOTLOADER", but then when I click on it it says The drivers for this device are not installed, (code 28) thee are no compatible drivers for this device. I am at a complete loss

[@tired9048]

You should change "STM32 BOOTLOADER" device driver to one located in C:\Program Files (x86)\STMicroelectronics\Software\DfuSe v3.0.6\Bin\Driver\Win10

[@Dev255]

Hi Daniel, have you managed to get this sorted via @tired response? The best option I've found as things have moved on from this video is to create a query on the ODrive Forum. I haven't played with one for a while but left this video up as it helps some with older versions get theirs up and running. If you are still stuck, please feel free to ask again and I'll try and dig deeper.

[@axelvincent1174]

@@Dev255 hello, i ve the same problem but when i change the driver nothing if you have an answer =)

[@HamSanwich420]

Hi Neil, my 56v o drive board seems to short out my usb hubs every time i connect a usb cable. have you seen anything like that yet?

[@Dev255]

Hi, I've not come across this before, is it when power is applied to the board? As the USB does not connect unless the ODrive is powered. You could try temporarily switching to DFU mode just to see if the USB works with the ODrive powered. There is a possibility that the USB hub doesn't like the board. Also, have you got a decent earth on the ODrive? Although it shouldn't affect it in this way. Failing this, you could ask on the ODrive website forum, just start a new support feed. Hope that helps

[@SAMETELMACI]

hi ı have a odesc 3.6 odrive from sequre, and when ı connect 2 sequre to my computer same time, odrive 1 is broken, ı flash on stm32cubeide but dont fix, when ı connect odrivedfu is tell me odrive found but dont serial number, but when ı check ı see serial code

[@Dev255]

Hi, I don't know what this could be, as I haven't played with anything other than the ODrive systems. Their community page is very comprehensive for the ODrive, and it may help you, although ODrive don't support other manufacturers' systems as there are many differences

[@hussamhaij6238]

Mine it doesn't appear even when i put it in dfu mode , how can i fix this ? thank you in andvance

[@Dev255]

Hi, if it doesn't appear even in DFU, you may have a faulty unit, although the one in this video was sent to me as they had the same issue. You may wish to try a different PC, USB port, or even the USB cable, there is a possibility that the USB cable you are using only supplies power and does not have the data lines to connect to the system. If using on a PC take a look in the Device Manager for this unit and unplug and re-plug back in to see if anything appears. I hope that helps.

[@hussamhaij6238]

@@Dev255 Thank you for replying , it worked before and connected it, but suddenly it disappeared and started to get "connect to your odrive " when ever I execute the odrivetool command, I tried diff usb ports, pc's and cables, but still same issue.

[@Dev255]

@@hussamhaij6238 Ah ok, that may still be recoverable, although you may need to get the ST-Link V2 USB device that I mention in the video, this should allow you to re-flash the Firmware should its own boot loader not work. Before spending money on that though, it may be worth you contacting the manufacturer as they may be able to help or even replace your unit. The ST-Link is fairly cheap and is a good backup option. Hopefully, your board is recoverable. You may also benefit from searching on the ODrive community forum here: discourse.odriverobotics.com/

[@simonlaker5742]

there isnt many tutorials for odrive . trying to run a linear motor on one . thanks

[@Dev255]

No worries, the ODrive community has a good Discord channel if you need further assistance

[@simonlaker2139]

@@Dev255 thanks I've been on there. Mines a home brew. Linear tubular ironless bldc. Asked many questions. I have had some help lately, but still not sure if it will run on odrive.

[@simonlaker2139]

@@Dev255 also planning on cnc and 3d printer. Drop in replacement. 3d printed

[@Dev255]

@@simonlaker2139 Ah ok, its all about pole pairs and encoder type for the ODrive, if linear, have you considered the AMT 102 rotary encoder with a shaft that is rotated by a kevlar taught thread (by sprung idler pulley) that links to the linear device. Kevlar has less than 1% stretch, so is very accurate for cheap linear measurements. The only problem then is keeping it clean in a dirty environment.

[@simonlaker2139]

@@Dev255 I built a linear incremental magnetic encoder from component level. Resolution of 0.001mm

[@nico9893]

does not work on my makerbase "odrive".. after many attempts.. be careful useing not the original odrive. Especially since (mine) does only work with the MKS firmware and not the latest Odrive..

[@Dev255]

Hi, yes I wouldn't recommend anything other than ODrive carry out this re-flash unless you are sure this will work. This type of ODrive is being discontinued but I will leave this video up for reference of older devices. I still use my ODrives on this version of firmware.

[@kleindavid9416]

did you get it working... fighting with mine again and its annoying...