You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When developing a custom code for the F4 side of the Crazyflie 2.1 (support for Paparazzi UAV system), I struggled a bit with the communication at 1M baud between the NRF and the F4. I later realized that uart hardware flow control is enabled on the NRF side, but on the F4 side, this flow control should be done by hand (no hardware flow control for uart6).
Also, not doing it properly leads to several transmission errors making the communication with the Crazyradio not reliable.
Unless I missed this part of the documentation, I suggest to add this important information to the developer wiki/doc so that people don't face the sameo) issue in the future.
The text was updated successfully, but these errors were encountered:
No, only when using my own firmware on F4 without the (software) flow control.
Funny thing was that it was almost working with debugging options but not with optimized code. It turns out that with debug flags, the code is slower and produce less errors (but only by chance). Using properly the RTS line makes it work without problems anymore.
When developing a custom code for the F4 side of the Crazyflie 2.1 (support for Paparazzi UAV system), I struggled a bit with the communication at 1M baud between the NRF and the F4. I later realized that uart hardware flow control is enabled on the NRF side, but on the F4 side, this flow control should be done by hand (no hardware flow control for uart6).
Also, not doing it properly leads to several transmission errors making the communication with the Crazyradio not reliable.
Unless I missed this part of the documentation, I suggest to add this important information to the developer wiki/doc so that people don't face the sameo) issue in the future.
The text was updated successfully, but these errors were encountered: