El mar, 15 oct 2024 a las 21:57, RVP (<r...@sdf.org>) escribió:
>
> On Tue, 15 Oct 2024, Martin Neitzel wrote:
>
> >> Not sure why it fails with the dtyU0 device.
> >
> > Maybe because the tests where done using "cat /dev/dtyU0"
> > throughout this thread. cat(1) itself buffers, defeating
> > any "stty raw" games to unbuffer the the device. You need
> > to use "cat -u" when testing with cat(1).
> >
>
> I don't think `-u' matters when cat is writing to a terminal.
>
> > (I also suggest "-v" in order to not mess up the terminal with
> > control codes.)
> >
>
> Yes; or hexdump (but, we aren't seeing anything at all--unless the
> device is sending only non-printable chars.--like NULs--which it
> isn't. I also converted Ramiro's hexdump output back into binary
> yesterday and blasted it to a terminal and _stuff did show up_).
>
> -RVP
Thanks Martin and RVP, cat -u did not work.
netbsd-raspa4$ { sleep 1; stty -f /dev/ttyU0 9600 raw clocal cread
-crtscts; } & cat -u -v /dev/ttyU0
stty: /dev/ttyU0: Resource temporarily unavailable
^C
Regards.
