Bitcraze Forums

Just received my crazyflie2.0 - assembled and tested OK. I.e start sequence is OK.
So tried to install the s/w stack.

With crazyflie USB attached I ran latest cfc client. "cfclient 2017.06"
Using libUSB at first (installed via zadig-2.3)
Tried procedure for updating the bootloader. used the cf2_nrf-2017.05.bin to program it. Seemed to work (verify was never selectable).
When it was done I ended up with M2 flashing.
Tried again with with LibusbK and did not work.

After some reading occurred to me the zip file with internal manifest might be the proper file instead of the bin.
but programming failed - so tried using the cf2-2017.06.bin file
Now I've got M2 blue and I can't get it back into bootloader mode with a 3second start button press

What am I doing wrong ?
How can I recover ?

by disconnecting the battery was able to get back to an M2 I could get back into bootloader mode.
So now I can try the bootloader again.
What file should i be uploading - the zip, or a bin ?

It says its a crazyflie2 but it could be an old one ? is there a previous release I could be using ?

Hi,
You should flash the .zip file using the Crazyflie client.

I succeeded in recovering and using the zip worked on another attempt.
Thanks.

In summary:
- you may need to disconnect the battery to get from a solid Blue M2LED back to being able to use the on/off button.
- The zip file contains a manifest in json and one or more bin files. Don;t program bin files directly (which you may be used to from other devices)
- instead select the zip file.