"... may need to wait for some input from an rpi engineer"
I thought maybe you were one. [Compliment]
MANY THANKS.
It seems like this is a bug. That is, if one says you have UART1 then no cruft should be on the TX line at any time.
The other hint is that when my service starts, it fails because /dev/ttyAMA0 can't be opened.
But if I start the service by hand later, it works fine. Except for the risk the other side (PIC) gets confused.
So something in the system is using UART1.
I think I've done what I'm supposed to to prevent that.
But either I need to do more (what?) or it's a bug.
I thought maybe you were one. [Compliment]
MANY THANKS.
It seems like this is a bug. That is, if one says you have UART1 then no cruft should be on the TX line at any time.
The other hint is that when my service starts, it fails because /dev/ttyAMA0 can't be opened.
But if I start the service by hand later, it works fine. Except for the risk the other side (PIC) gets confused.
So something in the system is using UART1.
I think I've done what I'm supposed to to prevent that.
But either I need to do more (what?) or it's a bug.
Statistics: Posted by MIT70 — Sat Feb 22, 2025 1:44 am