Date: Thu, 28 Dec 2023 12:38:58 -0800 From: Mark Millard <marklmi@yahoo.com> To: bob prohaska <fbsd@www.zefox.net> Cc: John F Carr <jfc@mit.edu>, "ticso@cicely.de" <ticso@cicely.de>, Marcin Cieslak <saper@saper.info>, "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org> Subject: Re: USB-serial adapter suggestions needed Message-ID: <B371E1D9-410D-40DC-A0D5-AFEC24B15C3D@yahoo.com> In-Reply-To: <ZY3LWKmCPvmLZvzU@www.zefox.net> References: <ZYhjzPLUBT74EVau@cicely7.cicely.de> <ZYiI7KuPwabExucl@www.zefox.net> <55q37289-ss30-nq9o-7r31-086n999p394s@fncre.vasb> <ZYonM2b2X008mpaw@cicely7.cicely.de> <ZYuHW34T1rxwqdz6@www.zefox.net> <C8C30A69-05D5-45FE-B95D-A31BD13B841F@yahoo.com> <23100FB9-BB4A-48FF-A715-84EF7F6F59A6@mit.edu> <6DD2FDE4-77DB-499A-AED8-F179A9DAA0EF@yahoo.com> <ZYxzNqNENpowIOrg@www.zefox.net> <6A38A60B-3281-468D-907C-26AB2F8D07A6@yahoo.com> <ZY3LWKmCPvmLZvzU@www.zefox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Dec 28, 2023, at 11:24, bob prohaska <fbsd@www.zefox.net> wrote: > On Wed, Dec 27, 2023 at 12:27:33PM -0800, Mark Millard wrote: >>=20 >> Overall I've not been able to understand what the >> (various?) hypothesized stage-by-stage byte flow >> paths are in these notes. >>=20 >=20 > Maybe this will help. The path is >=20 > workstation> Ethernet > terminal server:usb-serial > serial wires> = GPIO 8/10 >=20 > I hesitated to use the words "terminal server" because that has = implications > (distinct IP address, multiple serial interfaces) that don't exist = here.=20 >=20 > The workstation is a RasPiOS Pi4, the Pi3 host called pelorus is the = terminal > server and the GPIO pins are on the Pi3 host named www.zefox.net . Your prior messages reported text referencing .org, such as: FreeBSD/arm64 (www.zefox.org) (ttyu1) and: No, the garbled login prompt originates from www.zefox.org's serial console. and: Understood, it's been hard to articulate 8-( Maybe Workstation > ethernet > pelorus > usb port > gpio 8,10 > console = www.zefox.org is a little clearer So: "www.zefox.net <http://www.zefox.net/>" above is a change of report, = if I understand right. > The Ethernet connection works well enough for all the other hosts = that I think=20 > we can disregard whether it's wired or WiFi and LAN or WAN or all = four. You have also reported that: The Pi3 which reported the garbled login prompt=20 uses in config.txt: b@www:/boot/msdos % more config.txt init_uart_clock=3D3000000 enable_uart=3D1 kernel=3Du-boot.bin kernel7=3Du-boot.bin dtoverlay=3Dmmc force_mac_address=3Db8:27:eb:71:46:4f This is using the mini-uart for the serial console and the full-function UART for bluetooth. It also is not using arm_64bit=3D1 . (So armv7 support instead of aarch64 support?) https://elinux.org/RPi_Serial_Connection claims: QUOTE . . . the less capable mini-UART with no break detection, no framing = errors detection, no parity bit, no receive timeout interrupt and no DCD, DSR, DTR or RI signals END QUOTE This contrasts with: The Pi3 hosting the usb-serial adapter has in config.txt bob@pelorus:~ % more /boot/efi/config.txt [all] arm_64bit=3D1 dtparam=3Daudio=3Don,i2c_arm=3Don,spi=3Don dtoverlay=3Dmmc dtoverlay=3Ddisable-bt device_tree_address=3D0x4000 kernel=3Du-boot.bin which has the full-function UART for its serial console and is using arm_64bit=3D1 . Why the variation? =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?B371E1D9-410D-40DC-A0D5-AFEC24B15C3D>