Lighthouse keeps getting disconnected

[soujanya957]

Hi. Trying to get my crazyflie code to work with lighthouse. It works, but it sometimes just doesn't connect with the lighthouse. I notice that even after flashing with latest firmware, the console bootup shows lighthouse firmware disabled. I reflashed and cold-rebooted and it showed LH ready and it detected the lighthouse base stations. It ran like one flight, but restarting the drone and/or using a different workstation to deploy the code (move radios, etc) anything causes the firmware to boot with lighthouse disabled in the console print in cfclient. Any help would be great!

[ArisMorgens]

Hello @soujanya957!

The "lighthouse firmware disabled" error can be caused by a version mismatch between the deck and the Crazyflie.
In the console tab, it looks like this:

LHFL: Lighthouse bootloader version: 2
LHFL: Bitstream CRC32: 25A6B8FD [FAIL]
LHFL: The deck bitstream does not match the required bitstream.
LHFL: We require lighthouse bitstream of size 104092 and CRC32 563A0D3E.
LHFL: Leaving the deck in bootloader mode ...
LH: FPGA not booted. Lighthouse disabled!

In the latest release (2026.08) we bumped the lighthouse fpga firmware to V7. This means that when you flash the .zip file via cfclient, the deck gets updated. If you later flash your Crazyflie with firmware before this commit, you get this version mismatch.

If that's the case, the best solution would be to rebase your firmware to the latest release or latest master of crazyflie-firmware.

Otherwise, you could flash the Crazyflie with the lighthouse deck attached with a previous release e.g. 2026.04 via cfclient, and continue working on an older version of crazyflie firmware.

Let us know if you managed to solve the issue, or if you have any questions.