So these are some differences (see above rasppi doc)
/boot/config.txt is now in /boot/firmware/config.txt
dtoverlay=miniuart-bt now needs to bedtparam=krnbt=off
This will make serial communication work for simple examples (like this experimental bolt app uart example here with python script), but with the crtp over uart example I get this:
Exception: Couldn't load link driver for /ttyAMA0
This is because the python package pyserial can use the serial port, but if you list it with python3 -m serial.tools.list_ports -v, then only ttyACM10 is shown. This is the port that is not on the standard GPIO 14 and 15 pins, but on a separate debug port on the other side of the board which requires a special plug.
So we have instructions of how to connect a crazyflie through uart with a raspberry pi: https://www.bitcraze.io/documentation/repository/crazyflie-lib-python/master/development/uart_communication/
These instructions don't work for Raspberry pi 5 anymore as they handle their uarts differently: https://www.raspberrypi.com/documentation/computers/configuration.html#configuring-uarts
So these are some differences (see above rasppi doc)
/boot/config.txt
is now in/boot/firmware/config.txt
dtoverlay=miniuart-bt
now needs to bedtparam=krnbt=off
This will make serial communication work for simple examples (like this experimental bolt app uart example here with python script), but with the crtp over uart example I get this:
Exception: Couldn't load link driver for /ttyAMA0
This is because the python package pyserial can use the serial port, but if you list it with
python3 -m serial.tools.list_ports -v
, then only ttyACM10 is shown. This is the port that is not on the standard GPIO 14 and 15 pins, but on a separate debug port on the other side of the board which requires a special plug.