Uploading "lighthouse-fpga" using UI doesn't work

[h4writer]

I've been struggling to get a new version / adjusted version of the lighthouse-fpga firmware on the drone (bolt).

We have been trying the following instruction to update the lighthouse deck:
https://www.bitcraze.io/documentation/repository/crazyflie-clients-python/master/userguides/userguide_client/#firmware-upgrade

I have tried:

1. An official release

• I took the 2025.02 release from "https://github.com/bitcraze/crazyflie-release/releases/tag/2025.02"
• I extracted the lighthouse.bin
• I edited the file with a hex editor and changed 2nd byte (version) from 6 to 7
• I uploaded it

After restart the console in cfclient still shows:
LHFL: Firmware version 6 verified, booting deck!

2. Building my own build

Updating the Makefile in the fpga build to 7:
https://github.com/bitcraze/lighthouse-fpga/blob/master/Makefile

I did confirm that the second byte is indeed 7 after this change.
I uploaded this again, by adding this generated lighthouse.bin version in the 2025.02 and uploaded it.

After restart the console in cfclient still shows:
LHFL: Firmware version 6 verified, booting deck!

Is this a bug, or am I doing something wrong?

[ataffanel]

Did you also update the file manifest.json with version 7? It is likely your new firmware was not flashed if it was still seen as v6 in the manifest.

[h4writer]

I did adjust the value in the manifest.json, but sadly that didn't help either.

"lighthouse.bin": {"platform": "deck", "target": "bcLighthouse4", "type": "fw", "release": "V7", "repository": "lighthouse-fpga"}

[ataffanel]

I think the problem is that your new lighthouse firmware is not flashed since it does not have the right hash in the firmware, this is the commit that updated the firmware to accept version 6 of the lighthouse firmware: bitcraze/crazyflie-firmware@ebf0a1c

You need to edit these values in order for the bootloader to actually flash the new firmware.

[h4writer]

Ah I see. I will try that and let you know if that helped. Thanks!

[h4writer]

This solves it indeed. I was able to upload a custom firmware. Might be good to add this to the documentation somewhere?
Thanks!