Unable to fetch all memories

[AdamGoertz]

Apologies if this is the wrong place for this issue. I was uncertain whether to open it here or in crazyflie-firmware. Please let me know if it belongs elsewhere.

I am using the latest release of Crazyswarm2 (1.0.5) with the cpp backend, which uses the latest commit of this repository (72996dc) as a submodule, and have tested this using the two latest releases of crazyflie-firmware (2025.12 and 2026.04).

On startup, Crazyflie::requestMemoryToC is called. I have added a log statement at crazyflie_cpp/src/Crazyflie.cpp:890 to print each memory index when it is requested.

[crazyflie_server-4] [INFO] [1786732393.018601675] [crazyflie_server]: [cf02] Requesting memories...
[crazyflie_server-4] [INFO] [1786732393.023075253] [crazyflie_server]: [cf02] Memories: 8
[crazyflie_server-4] [INFO] [1786732393.023112547] [crazyflie_server]: [cf02] Memory: 0
[crazyflie_server-4] [INFO] [1786732393.026580286] [crazyflie_server]: [cf02] Memory: 1
[crazyflie_server-4] [INFO] [1786732393.029990173] [crazyflie_server]: [cf02] Memory: 2
[crazyflie_server-4] [INFO] [1786732393.033546938] [crazyflie_server]: [cf02] Memory: 3
[crazyflie_server-4] [INFO] [1786732393.043523585] [crazyflie_server]: [cf02] Memory: 4

After this point, the server hangs and never receives memories 4-7.

[AdamGoertz]

Looks like commit 92a1660e252d91ccf0f1f9f6c987c0b0ac30413e on crazyflie-firmware changes the memory size to be between 8-12 bytes, rather than always 8. This breaks the size check in crtpMemoryGetInfoResponse::valid.

[whoenig]

Thanks! Could you also specify if you use Crazyradio2 vs Crazyradio PA? We have seen general server hangs when a message we send is acknowledged, but never responded to on the firmware side. This is a firmware issue, likely related to the missing syslink flow control between NRF51 and STM32, that seems to be less likely to be triggered with a Crazyradio2.

[AdamGoertz]

I was testing using the Crazyradio PA