Date: Tue, 26 Dec 2023 18:09:31 -0800 From: bob prohaska <fbsd@www.zefox.net> To: ticso@cicely.de Cc: Marcin Cieslak <saper@saper.info>, freebsd-arm@freebsd.org Subject: Re: USB-serial adapter suggestions needed Message-ID: <ZYuHW34T1rxwqdz6@www.zefox.net> In-Reply-To: <ZYonM2b2X008mpaw@cicely7.cicely.de> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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: > > > > > 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. > > > > How does that noise look like? > 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 FreeBSD/arm64 (www.zefox.org) (ttyu1) login: �������� Password: Login incorrect ........... 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. 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. > If the tip process was stopped by the ssh disconnect then the uart will fall > back to its default bps rate. > Some USB uarts still buffer received data in the chip itself, with the wrong > bps rate. > > > Did you try to run respective sshd daemons in the debug mode to log disconnects > > and possible their reason? I did, and didn't see anything recognizable as an error. It seemed the session just stopped. No errors, nothing. Whether it's ssh that stopped or tip that stopped seems to be the primary mystery. What I see is ssh stopping, but that may be more symptom than cause. Ssh sessions not involving tip/cu don't stop, at least not as often. Thanks for writing, bob prohaska > > > > -- > B.Walter <bernd@bwct.de> https://www.bwct.de > Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ZYuHW34T1rxwqdz6>