Date: Wed, 27 Dec 2023 00:30:26 -0800 From: Mark Millard <marklmi@yahoo.com> To: bob prohaska <fbsd@www.zefox.net> Cc: ticso@cicely.de, Marcin Cieslak <saper@saper.info>, freebsd-arm@freebsd.org Subject: Re: USB-serial adapter suggestions needed Message-ID: <C8C30A69-05D5-45FE-B95D-A31BD13B841F@yahoo.com> In-Reply-To: <ZYuHW34T1rxwqdz6@www.zefox.net> References: <ZYd%2Bmid70Sc1xg//@www.zefox.net> <snq8819p-3q19-o239-7op5-sss807q66082@fncre.vasb> <ZYeDi2H754ZKyJG3@www.zefox.net> <16864054-4os0-pq3p-7qp0-7299666908os@fncre.vasb> <ZYhSYNxHcmR2I/YP@www.zefox.net> <ZYhjzPLUBT74EVau@cicely7.cicely.de> <ZYiI7KuPwabExucl@www.zefox.net> <55q37289-ss30-nq9o-7r31-086n999p394s@fncre.vasb> <ZYonM2b2X008mpaw@cicely7.cicely.de> <ZYuHW34T1rxwqdz6@www.zefox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Dec 26, 2023, at 18:09, bob prohaska <fbsd@www.zefox.net> wrote: > On Tue, Dec 26, 2023 at 02:06:59AM +0100, Bernd Walter wrote: >> On Tue, Dec 26, 2023 at 12:02:50AM +0000, Marcin Cieslak wrote: >>> On Sun, 24 Dec 2023, bob prohaska wrote: >>>=20 >>>> I do see what looks like noise on the serial lines, but only after = a spontaneous >>>> disconnect and only with FTDI adapters. When the serial connections = are working >>>> nothing resembling noise is seen. >>>=20 >>> How does that noise look like? >>=20 > It appears to be non-ascii. I can't get it to copy and paste in a way > that's recognizable to me, but here's a sample anyway, taken from > bob@pelorus:~ % uname -a > FreeBSD pelorus 14.0-RELEASE-p4 FreeBSD 14.0-RELEASE-p4 #0 = releng/14.0-n265400-4edf3b80733e: Wed Dec 27 20:21:26 PST 2023 = bob@pelorus:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC arm64: > ....... > # tip ucom > connected >=20 > FreeBSD/arm64 (www.zefox.org) (ttyu1) >=20 > login: =EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF= =BF=BD > Password: > Login incorrect > .......... >=20 > The backslash letter pairs are clearly different, but they're = displayed on a > RasPiOS lxterminal window as a white oval with a dark question mark in = the middle. It shows that way in some programs but not others in my context. But what matters is the byte sequence, not the potentially false interpretations of them. In a program that shows hexadecimal byte values and the printable text (with "." for control characters and for 8-bit characters on the right below): 0000: 6C 6F 67 69 6E 3A 20 C3 AF C2 BF C2 BD C3 AF C2 login: ......... 0010: BF C2 BD C3 AF C2 BF C2 BD C3 AF C2 BF C2 BD C3 ................ 0020: AF C2 BF C2 BD C3 AF C2 BF C2 BD C3 AF C2 BF C2 ................ 0030: BD C3 AF C2 BF C2 BD 0A 50 61 73 73 77 6F 72 64 ........Password 0040: 3A : The byte pairs that start with C3 's and C2's look far from random to me --also they do not look like glitches. (Of course, I'm not looking at original files.) > Sometimes printable characters show up, but it doesn't look like my = memory > of a baudrate mismatch on a serial modem. Maybe that's just an = artifact of > modern character sets. =3D=3D=3D Mark Millard marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C8C30A69-05D5-45FE-B95D-A31BD13B841F>