I’m encountering some strange behavior on my previously working odrive 3.5-48V:
I flashed the board previously using
openocd and an ST-link I had, and it worked successfully. I was able to control both of my hoverboard motors.
Today I started up
odrivetool (on widows) and it connected normally. One of my motors may have had a bad connection do to some soldering, so I checked the connections and reran
odrivetool. Since that first connection this morning, I have been unsuccessful at connecting to my odrive. I figured reflashing the firmware might yield positive results, so I switched from windows to ubuntu 16.04 and ran an identical
openocd command to the one that previously successfully flashed my board. (In the correct directory).
openocd -f interface/stlink-v2.cfg -f target/stm32f4x.cfg -c init -c reset\ halt -c flash\ write_image\ erase\ ODriveFirmware_v3.4-24V.elf -c reset\ run -c exit
However, there seems to be an issue there as well, as openocd gives me the output of:
Open On-Chip Debugger 0.9.0 (2018-01-24-01:05) Licensed under GNU GPL v2 For bug reports, read http://openocd.org/doc/doxygen/bugs.html Info : auto-selecting first available session transport "hla_swd". To override use 'transport select <transport>'. Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD adapter speed: 2000 kHz adapter_nsrst_delay: 100 none separate Info : Unable to match requested speed 2000 kHz, using 1800 kHz Info : Unable to match requested speed 2000 kHz, using 1800 kHz Info : clock speed 1800 kHz Info : STLINK v2 JTAG v17 API v2 SWIM v4 VID 0x0483 PID 0x3748 Info : using stlink api v2 Info : Target voltage: 3.224753 Error: init mode failed (unable to connect to the target) in procedure 'init' in procedure 'ocd_bouncer'
My stlink v2 has its indicator light on and shows up in an
lsusb, and I’ve checked the connections. My odrive has its green led on, but I can’t seem to get anything out of it to indicate it isn’t fried or something. Nothing happened between when it was working and not working, so I’m wondering if anyone has any good debug ideas to poke around at these issues?
Edit: I can’t seem to get anything for the odrive on an