I use a ESP32-devboard that sends some sensor data to a Pi over serial, using the dev board built in ch341-uart converter. This has been working fine on Pi4's since a long time, but now I'm seeing issues on Pi 5 with data being lost.
I wrote a small app that just reads out all data and prints the amount of bytes received every second that I use to try to narrow down this issue.
If I enable the uart0 on the Pi 5, and wire the UART there as well I can see that I receive all the data on that UART but not on the ttyUSB0 that uses the ch341-chip. Since no flow control is used I can run them both at the same time and compare the amount of data received using my simple test program.
Since I saw that the Pi 5 UART works well, while the USB-serial did not, I added a third option in the mix by connecting a cp2102n via USB to the Pi 5 and wiring up the RX pin to the ESP32 UART as well. And here I once again see that I can receive all data using this USB-serial converter.
But I cannot think of a good reason why the ch341-driver would suddenly start misbehaving on the Pi 5, when the exact same kernel version works on the Pi 4. Has anyone experienced anything similar?
The UART is using a baudrate of 921600, and the ESP32 dev board is this one: https://www.olimex.com/Products/IoT/ESP ... e-hardware.
UPDATE: I might have been chasing ghosts, seems like I have the same issues on other systems that the Pi 5. So ignore this post![:)]( "Smile")
I wrote a small app that just reads out all data and prints the amount of bytes received every second that I use to try to narrow down this issue.
If I enable the uart0 on the Pi 5, and wire the UART there as well I can see that I receive all the data on that UART but not on the ttyUSB0 that uses the ch341-chip. Since no flow control is used I can run them both at the same time and compare the amount of data received using my simple test program.
Since I saw that the Pi 5 UART works well, while the USB-serial did not, I added a third option in the mix by connecting a cp2102n via USB to the Pi 5 and wiring up the RX pin to the ESP32 UART as well. And here I once again see that I can receive all data using this USB-serial converter.
But I cannot think of a good reason why the ch341-driver would suddenly start misbehaving on the Pi 5, when the exact same kernel version works on the Pi 4. Has anyone experienced anything similar?
The UART is using a baudrate of 921600, and the ESP32 dev board is this one: https://www.olimex.com/Products/IoT/ESP ... e-hardware.
UPDATE: I might have been chasing ghosts, seems like I have the same issues on other systems that the Pi 5. So ignore this post
Statistics: Posted by erikb — Wed Apr 17, 2024 12:52 pm