Crazyflie Deck Flashing

Console messages, before and after flashing

Output in Console tab, BEFORE flashing

LHFL: Lighthouse bootloader version: 2
STAB: Starting stabilizer loop
ESTKALMAN: State out of bounds, resetting
SUP: Can not fly
SUP: Ready to fly
LHFL: Bitstream CRC32: 952E7A01 [FAIL]
LHFL: The deck bitstream does not match the required bitstream.
LHFL: We require lighthouse bitstream of size 104093 and CRC32 112BC794.
LHFL: Leaving the deck in bootloader mode ...
LH: FPGA not booted. Lighthouse disabled!

Output in Console tab, AFTER flashing

LHFL: Lighthouse bootloader version: 2
STAB: Starting stabilizer loop
ESTKALMAN: State out of bounds, resetting
LHFL: Bitstream CRC32: 112BC794 [PASS]
LHFL: Firmware version 6 verified, booting deck!
SUP: Can not fly
SUP: Ready to fly

Installing the CFClient GUI

https://www.bitcraze.io/documentation/repository/crazyflie-clients-python/master/installation/install/

Or install from source:

https://github.com/bitcraze/crazyflie-clients-python/blob/master/docs/installation/install.md

Video: how to flash

This flashes both firmware to the crazyflie drone and the deck:

Extra Notes

1. The flashing from Cold boot (recovery) part is optional. It’s only needed if the crazyflie’s firmware is unknown and outdated.

2. During the flashing, the “Status” label might show “Identifying deck to be updated” and might be stuck there for a long time.

   1. If it’s stuck for more than 1 minute, it might be because the drone is calibrating the IMU. Try holding it up and help it move in all directions and orientations. The drone should blink and emit a sound when that’s done. After that, the deck flashing should continue.

   2. It’s also fine to unplug/power-off the drone and repeat the whole flashing process, if the step is stuck for more than 3 minutes. The cfclient GUI might need to be re-started, too.