Replies: 1 comment
|
Thanks a lot for the well described message! I am pretty sure this is a bug so I made an issue in the nRF firmware repos: bitcraze/crazyflie2-nrf-firmware#101. Lets fix the bug there. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
When reading CRTP packets from the Crazyflie 2.1+ using BLE shortly after booting the drone, I experience two issues:
The second split packets have their first byte cut off, and an extra junk byte appended to the end. This would seem to point to an off-by-one error in the nRF firmware, but it appears correct to me.
Additionally, it looks like the packet splitting procedure is not implemented in accordance with the documentation. Namely, it only sets the
startandlengthbits in the first packet's control byte (it does not set thepidbits), and it does not clear thestartorlengthbits in the second packet's control byte. It seems like the previous version of the firmware set the control byte correctly though.Here is a partial dump of the packets I receive after boot:
If I reboot the STM only (but not the nRF) by sending the
SYSOFFandSYSONbootloader commands, I get the expected packets after boot, but they are still malformed:Is anyone else experiencing this issue?
All reactions