[SOLVED] Firmware Update Failed (IOS): Timeout while fetching STM32 Info

[domahony]

After attempting to update the firmware using the IOS app, the update failed. As my symptoms appeared to be the same, I followed the information in the thread CrazieFlie 2.0 Failed IOS flash - stuck on Blue Light (viewtopic.php?f=5&t=1801). However, after going into bootloader mode (holding power button for ~3s), and selecting the Update button in the IOS app, the dialog box "Error Updating Timeout whle fecthing STM32 Info" is displayed.

On the Crazyflie, the M1 LED is repeating 5 quick flashes, the M2 is flashing, (around 1hz), the M3 is steady blue, and M4 is not lit.

When I select Update on my IOS tablet, the M4 flashes green briefly.

Before I attempted the update I was able to fly around a bit for around 5 minutes or so, but now it doesn't work at all.

Any help is greatly appreciated!

[chad]

Does your light behavior look like the video shown here?

If so, that's a system self-test failure.

[domahony]

Yes the M1 led is flashing exactly like that.

A couple of things to note though:

1.) When I initially assembled the copter, the self test passed successfully.
2.) Now, (after the upgrade failure), when I initially power-on the copter, nothing happens, except the M2 led is on (steady, not blinking).
3.) The M1 led flashes in the failed self test pattern only when I go into bootloader mode.

As I mentioned, the self test initially passed, is there a way I can totally reset everything?

If not what else can I do?

[tobias]

It's hard to say what has gone wrong but it should not be possible to overwrite the bootloaders (one in nRF51 and one in STM32) without flashing a firmware which deliberately does so. I think that incomplete because the update failed there is now an incomplete firmware. What puzzles me is why it now fails with "Error Updating Timeout while fetching STM32 Info".

The STM32 can be upgraded using USB and can be recovered this way however the nRF51 can only be flashed using either bluetooth (app) or the Crazyradio. You can however try flashing the STM32 with DFU.

[domahony]

I reflashed the bootloader using DFU several times. I currently have the cf2-2015.08.1.bin flashed on.

I have a Crazyradio, and can I connect using the cfclient (only from bootloader mode). Sometimes I can connect with the radio, sometimes only via USB (I can't figure out a pattern yet).

Also, occasionally, I've seen the message "Error Updating; Timeout while fecthing nR51 info" instead of the "Timeout while fetching STM32 info" box, however, I can't figure out what circumstances cause the nRF51 message to appear.

I've attached a screenshot of parameters output (note the red in the firmware section).

I can provide any other debugging information, and welcome any troubleshooting suggestions.

[domahony]

Here this screenshot I mentioned in my last post:

[tobias]

What happens if you try flashing it from the cfclient with the crazyradio? My guess is that the STM32 bootloader is the problem. Did you flash this one or did you build it your self and flash it? Did you use this command?

Code: Select all

sudo dfu-util -d 0483:df11 -a 0 -s 0x08000000 -D cf2loader-1.0.bin

[domahony]

Thank you so much!!

I used the this url as you suggested.

However, I used the command

Code: Select all

sudo dfu-util -d 0483:df11 -a 0 -s 0x08004000 -D ./cf2loader-1.0.bin 

Note that I used the 0x08004000 address versus the 0x08000000 address.

After that I could successfully flash the bootloader using the cfclient. I used this firmware file.

Thank you so much again.