Hi William,
Am 17.01.19 um 03:02 schrieb William Jacobs:
I am looking for help getting serial communication to work via the
UART on either a Raspberry PI 3 B or a 3 B + that is running Fedora 29. The kernel
recognizes the UART as /dev/ttyS1 on these systems. Data flows, but it is corrupted at
random intervals. This happens at any baud rate. With these same two computers,
everything works fine if I run Debian, which I really don't like. So it is not a
hardware issue. I am thinking it is more of a device tree problem.
i assume the root cause is the experimental cpu frequency driver. So
either you blacklist this driver or use /dev/ttyAMA0 which doesn't
depend on VPU clock.
Best regards
Stefan
I also have UART to USB adapters that the kernel recognizes ad /dev/ttyUSB0. When using
these under Fedora there is no corrupted data.
I would mention that I also have Fedora running nicely on a Quad Core i.MX6 based
Hummingboard2. On that UART, there is no corrupted data issue.
For my project, I really would like to use Fedora and have good communication via the
Raspberry PI UART. Is anyone here successfully using the UART on the Raspberry PI 3 B or
3 B +?
One final thing to mention, I do not have the console enabled on /dev/ttyS1. If I do
enable it, I get the corrupted data when trying to log in or look at console output via a
serial connection.
Any help would be greatly appreciated even if it just to tell me what to go read.
Thanks,
Will