crazyflie unresponsive after JTAG flash

[cfusting]

This morning I tried using my Bus Blaster v3 to flash the flie's firmware. I had some trouble getting the software setup on OS X but Macports solved most of my problems. However I believe I may have damaged or incorrectly flash the firmware. Previously when connecting the Blaster to the flie lots of LED's lit up, but having flashed the firmware only the blue PWR LED lights up. I am unable to connect to the bootloader via the radio as well. Here is my flashing command and program output:

Code: Select all

make flash OPENOCD_INTERFACE=interface/busblaster.cfg
openocd -d0 -f interface/busblaster.cfg -f target/stm32f1x.cfg -c init -c targets -c "reset halt" \
                 -c "flash write_image erase cflie.elf" -c "verify_image cflie.elf" -c "reset run" -c shutdown
Open On-Chip Debugger 0.6.1 (2013-03-04-10:36)
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.sourceforge.net/doc/doxygen/bugs.html
debug_level: 0
adapter speed: 1000 kHz
adapter_nsrst_delay: 100
jtag_ntrst_delay: 100
cortex_m3 reset_config sysresetreq
Error: stm32f1x.cpu -- clearing lockup after double fault
Polling target failed, GDB will be halted. Polling again in 100ms
Polling succeeded again
    TargetName         Type       Endian TapName            State       
--  ------------------ ---------- ------ ------------------ ------------
 0* stm32f1x.cpu       cortex_m3  little stm32f1x.cpu       halted
target state: halted
target halted due to debug-request, current mode: Thread 
xPSR: 0x01000000 pc: 0x00010100 msp: 0x464c457c
auto erase enabled
wrote 59392 bytes from file cflie.elf in 3.658806s (15.852 KiB/s)
verified 58960 bytes in 1.152030s (49.980 KiB/s)
Error: stm32f1x.cpu -- clearing lockup after double fault
target state: halted
target halted due to debug-request, current mode: Handler HardFault
xPSR: 0x00000003 pc: 00000000 msp: 0x464c455c
Polling target failed, GDB will be halted. Polling again in 100ms
shutdown command invoked
Polling succeeded again

Any ideas?

UPDATE: This was resolved by flashing the bootloader.

Cheers,

_Chris