[SOLVED] CrazieFlie 2.0 Failed IOS flash - stuck on Blue Light

[mnflyer]

Today I received my CF2.0 and took it for a couple flights using my iPhone. Then I saw the 'Upgrade Available' and tried to upgrade. It said it would take 10 minutes...unfortunately my phone is set to lock at 2 minutes and I did not know that would interrupt the upgrade. Now my CrazyFlie is not working. When I turn it on (battery or USB) it just has a solid blue light. My iphone can't see it anymore. The on/off switch will not turn it off either.

Here's what I tried so far:
1. If I hold power button while connecting battery or USB it goes to a 'slow blue blink' which progresses to fast blink.
2. When it is in fast blue blink...Windows (10) detects the device as STM32 BOOTLOADER DEVICE.
3. CFclient still can't see my CrazyFlie over USB. I tried a couple driver variations in Zadig with no success and went back to WINUSB Driver.
4. I downloaded dfu-util for windows and was able to successfully (well it said 'file downloaded successfully) both cf2loader-1.0.bin (8000000) and cf2-2015.08.1.bin (8004000). This was just using WINUSB driver according to Zadig.
5. I'm still stuck with a solid blue light whether I go to battery power or USB. I can still connect to the device using dfu-util, but I don't know what else to do.

Can you help?

[mnflyer]

There is one more state I can get it to go into-if I hold power button and connect power until I get the 'slow blink' mode and let go. It goes into a 'alternate 2 blue light blink' mode. I still can't see it from my iphone though.

[chad]

I *think* the Bluetooth updater won't overwrite the bootloader so you ought to be able to just flash at 0x08004000 with cf2-2015.08.1.bin. But you say that didn't work? Maybe a second try? I'm guessing you used the dfu instructions on the wiki?

[mnflyer]

Indeed I used the instructions here. I attached a screenprint of the output when I run dfu-util --list and the upgrade sequence. It appears to run successfully...but the device is stuck in blue light mode. Any ideas?

[mnflyer]

I had also tried redoing the bootloader like this:
http://blog.crazyflie.net/archives/34-R ... oader.html

No luck yet. I haven't given up since it does let me run these commands, but I'm stuck.

[chad]

Ah! I think the problem is that you can't use the .bin file for the STM32 flash over dfu. I believe you have to use the .dfu file! Since I don't see a dfu file on the Github releases page, I built one from the 2015.08.1 tag. Un-gz/tar it before you try to flash it. Let me know if that helps. I think the bootloader on your CF2 should be ok still.

cf2-2015.08.1.dfu.tgz

(49.46 KiB) Downloaded 553 times

[mnflyer]

Thank you, I tried the DFU using the command at:
https://wiki.bitcraze.io/projects:crazy ... opment:dfu
Which was:
dfu-util.exe -d 0483:df11 -a 0 -D cf2-2015.08.1.dfu

It looked OK ("Download done"), but still in solid blue light state after disconnecting power and reconnecting battery.

[mnflyer]

I just installed VirtualBox and the Bitcraze VM .6 so I can try working through the Linux environment instead of Windows. My VM can see STM32 Bootloader when the device is plugged in via lsusb but if I try to run dfu-util it says 'Cannot Open Device'. Nothing new here, just trying anything I can to wake the flie up. I'm wondering why it cannot be seen in the PC Client when that is supposed to support USB.

Bus 001 Device 004: ID 0483:df11 STMicroelectronics STM Device in DFU Mode
Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

dfu-util 0.5

(C) 2005-2008 by Weston Schmidt, Harald Welte and OpenMoko Inc.
(C) 2010-2011 Tormod Volden (DfuSe support)
This program is Free Software and has ABSOLUTELY NO WARRANTY

dfu-util does currently only support DFU version 1.0

Filter on vendor = 0x0483 product = 0xdf11
Cannot open device
Opening DFU USB device... bitcraze@bitcraze-vm:~/Downloads$

[chad]

I just installed VirtualBox and the Bitcraze VM .6 so I can try working through the Linux environment instead of Windows. My VM can see STM32 Bootloader when the device is plugged in via lsusb but if I try to run dfu-util it says 'Cannot Open Device'. Nothing new here, just trying anything I can to wake the flie up. I'm wondering why it cannot be seen in the PC Client when that is supposed to support USB.

Bus 001 Device 004: ID 0483:df11 STMicroelectronics STM Device in DFU Mode
Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

dfu-util 0.5

(C) 2005-2008 by Weston Schmidt, Harald Welte and OpenMoko Inc.
(C) 2010-2011 Tormod Volden (DfuSe support)
This program is Free Software and has ABSOLUTELY NO WARRANTY

dfu-util does currently only support DFU version 1.0

Filter on vendor = 0x0483 product = 0xdf11
Cannot open device
Opening DFU USB device... bitcraze@bitcraze-vm:~/Downloads$

Try running the dfu-util command as sudo. Does that help?

Oh, and my last post about the dfu file rather than the bin file was dumb. I forgot you were using an explicit start address which should work fine with the bin file. The dfu file with no address, bin file with address are synonymous. meh! I'm getting stumped here, grabbing at straws...

[chad]

Actually, is the STM32 even showing up in the usb devices? Maybe you can try:

Code: Select all

lsusb

-or-

Code: Select all

dfu-util -l

to see if it shows up.