Date: Thu, 28 Dec 2023 19:40:30 -0800 From: Mark Millard <marklmi@yahoo.com> To: bob prohaska <fbsd@www.zefox.net> Cc: John F Carr <jfc@mit.edu>, ticso@cicely.de, Marcin Cieslak <saper@saper.info>, freebsd-arm@freebsd.org Subject: Re: USB-serial adapter suggestions needed Message-ID: <B7E5DF67-4B43-401A-89DC-6F9422C95FA9@yahoo.com> In-Reply-To: <ZY4y2NvvL0N8Db69@www.zefox.net> References: <ZY4y2NvvL0N8Db69@www.zefox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail-4C62B640-776D-4FDB-BCD2-23CC7784A5FD Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable > On Dec 28, 2023, at 18:46, bob prohaska <fbsd@www.zefox.net> wrote: >=20 > =EF=BB=BFOn Thu, Dec 28, 2023 at 12:38:58PM -0800, Mark Millard wrote: >> On Dec 28, 2023, at 11:24, bob prohaska <fbsd@www.zefox.net> wrote: >>=20 >>> 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 implicat= ions >>> (distinct IP address, multiple serial interfaces) that don't exist here.= >>>=20 >>> The workstation is a RasPiOS Pi4, the Pi3 host called pelorus is the ter= minal >>> server and the GPIO pins are on the Pi3 host named www.zefox.net . >>=20 >> Your prior messages reported text referencing .org, such as: >>=20 >> FreeBSD/arm64 (www.zefox.org) (ttyu1) >>=20 >> and: >>=20 >> No, the garbled login prompt originates from www.zefox.org's >> serial console. >>=20 >> and: >>=20 >> Understood, it's been hard to articulate 8-( Maybe >> Workstation > ethernet > pelorus > usb port > gpio 8,10 > console www.zef= ox.org >> is a little clearer >>=20 >> So: "www.zefox.net <http://www.zefox.net/>" above is a change of report, i= f I understand >> right. >>=20 >=20 > It's my typo 8-( > The host generating console output is the Pi3 named www.zefox.org . > The host named www.zefox.net isn't involved at all, though it is > present and I typed its name in error. >=20 >>> The Ethernet connection works well enough for all the other hosts that I= think >>> we can disregard whether it's wired or WiFi and LAN or WAN or all four. >>=20 >> You have also reported that: >>=20 >> The Pi3 which reported the garbled login prompt >> 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 >>=20 >> 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?) >>=20 >=20 > You are correct, it's using the mini-uart (which I didn't realize) > per sysctl. The machine is running aarch64, the reference to kernel7 > in config.txt is a mistake. Bluetooth and WiFi aren't used on www.zefox.o= rg. For RPi3B*=E2=80=99s, booting as aarch64 should have arm_64bit=3D1 in config= .txt , as I understand. Use of the mini-uart is probably not a good idea for the serial console: dto= verlay=3Ddisable-bt should also be listed, like for the other RPi3B* . In fact, other than the force_mac_address, the general content should be lik= e the one with arm_64bit=3D1 as far as I can tell. Do you have specific reas= ons for needing any of the differences? >> https://elinux.org/RPi_Serial_Connection claims: >>=20 >> QUOTE >> . . . the less capable mini-UART with no break detection, no framing erro= rs >> detection, no parity bit, no receive timeout interrupt and no DCD, DSR, >> DTR or RI signals >> END QUOTE >>=20 >> This contrasts with: >>=20 >> 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 >>=20 >> which has the full-function UART for its serial console >> and is using arm_64bit=3D1 . >>=20 >> Why the variation? >>=20 >=20 > That machine is the terminal server, pelorus, on the LAN. Its > internal uart does not participate in the data transmission chain. > "Hosting the usb-serial converter" was my euphemism for terminal server. >=20 > Please accept my apologies for not proofreading more carefully! > If there is a better choice of terminology please tell me. >=20 > Thanks for your patience! >=20 > bob prohaska Note: edited on an iPad. For now, the computers I normally use are not avail= able. My ability to lookup some types of information is greatly limited. I w= ill soon be without internet access for some number of days.= --Apple-Mail-4C62B640-776D-4FDB-BCD2-23CC7784A5FD Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D= utf-8"></head><body dir=3D"auto"><font face=3D"Courier New"></font><br><bloc= kquote type=3D"cite"><div dir=3D"ltr"><font face=3D"Courier New">On Dec 28, 2= 023, at 18:46, bob prohaska <fbsd@www.zefox.net> wrote:<br><br></font>= </div><div dir=3D"ltr"><font face=3D"Courier New">=EF=BB=BF<span>On Thu, Dec= 28, 2023 at 12:38:58PM -0800, Mark Millard wrote:</span><br></font><blockqu= ote type=3D"cite"><font face=3D"Courier New"><span>On Dec 28, 2023, at 11:24= , bob prohaska <fbsd@www.zefox.net> wrote:</span><br></font></blockquo= te><blockquote type=3D"cite"><font face=3D"Courier New"><span></span><br></f= ont></blockquote><blockquote type=3D"cite"><blockquote type=3D"cite"><font f= ace=3D"Courier New"><span>On Wed, Dec 27, 2023 at 12:27:33PM -0800, Mark Mil= lard wrote:</span><br></font></blockquote></blockquote><blockquote type=3D"c= ite"><blockquote type=3D"cite"><blockquote type=3D"cite"><font face=3D"Couri= er New"><span></span><br></font></blockquote></blockquote></blockquote><bloc= kquote type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite"><fo= nt face=3D"Courier New"><span>Overall I've not been able to understand what t= he</span><br></font></blockquote></blockquote></blockquote><blockquote type=3D= "cite"><blockquote type=3D"cite"><blockquote type=3D"cite"><font face=3D"Cou= rier New"><span>(various?) hypothesized stage-by-stage byte flow</span><br><= /font></blockquote></blockquote></blockquote><blockquote type=3D"cite"><bloc= kquote type=3D"cite"><blockquote type=3D"cite"><font face=3D"Courier New"><s= pan>paths are in these notes.</span><br></font></blockquote></blockquote></b= lockquote><blockquote type=3D"cite"><blockquote type=3D"cite"><blockquote ty= pe=3D"cite"><font face=3D"Courier New"><span></span><br></font></blockquote>= </blockquote></blockquote><blockquote type=3D"cite"><blockquote type=3D"cite= "><font face=3D"Courier New"><span></span><br></font></blockquote></blockquo= te><blockquote type=3D"cite"><blockquote type=3D"cite"><font face=3D"Courier= New"><span>Maybe this will help. The path is</span><br></font></blockquote>= </blockquote><blockquote type=3D"cite"><blockquote type=3D"cite"><font face=3D= "Courier New"><span></span><br></font></blockquote></blockquote><blockquote t= ype=3D"cite"><blockquote type=3D"cite"><font face=3D"Courier New"><span>work= station> Ethernet > terminal server:usb-serial > serial wires> G= PIO 8/10</span><br></font></blockquote></blockquote><blockquote type=3D"cite= "><blockquote type=3D"cite"><font face=3D"Courier New"><span></span><br></fo= nt></blockquote></blockquote><blockquote type=3D"cite"><blockquote type=3D"c= ite"><font face=3D"Courier New"><span>I hesitated to use the words "terminal= server" because that has implications</span><br></font></blockquote></block= quote><blockquote type=3D"cite"><blockquote type=3D"cite"><font face=3D"Cour= ier New"><span>(distinct IP address, multiple serial interfaces) that don't e= xist here. </span><br></font></blockquote></blockquote><blockquote type=3D"c= ite"><blockquote type=3D"cite"><font face=3D"Courier New"><span></span><br><= /font></blockquote></blockquote><blockquote type=3D"cite"><blockquote type=3D= "cite"><font face=3D"Courier New"><span>The workstation is a RasPiOS Pi4, th= e Pi3 host called pelorus is the terminal</span><br></font></blockquote></bl= ockquote><blockquote type=3D"cite"><blockquote type=3D"cite"><font face=3D"C= ourier New"><span>server and the GPIO pins are on the Pi3 host named www.zef= ox.net .</span><br></font></blockquote></blockquote><blockquote type=3D"cite= "><font face=3D"Courier New"><span></span><br></font></blockquote><blockquot= e type=3D"cite"><font face=3D"Courier New"><span>Your prior messages reporte= d text referencing .org, such as:</span><br></font></blockquote><blockquote t= ype=3D"cite"><font face=3D"Courier New"><span></span><br></font></blockquote= ><blockquote type=3D"cite"><font face=3D"Courier New"><span>FreeBSD/arm64 (w= ww.zefox.org) (ttyu1)</span><br></font></blockquote><blockquote type=3D"cite= "><font face=3D"Courier New"><span></span><br></font></blockquote><blockquot= e type=3D"cite"><font face=3D"Courier New"><span>and:</span><br></font></blo= ckquote><blockquote type=3D"cite"><font face=3D"Courier New"><span></span><b= r></font></blockquote><blockquote type=3D"cite"><font face=3D"Courier New"><= span>No, the garbled login prompt originates from www.zefox.org's</span><br>= </font></blockquote><blockquote type=3D"cite"><font face=3D"Courier New"><sp= an>serial console.</span><br></font></blockquote><blockquote type=3D"cite"><= font face=3D"Courier New"><span></span><br></font></blockquote><blockquote t= ype=3D"cite"><font face=3D"Courier New"><span>and:</span><br></font></blockq= uote><blockquote type=3D"cite"><font face=3D"Courier New"><span></span><br><= /font></blockquote><blockquote type=3D"cite"><font face=3D"Courier New"><spa= n>Understood, it's been hard to articulate 8-( Maybe</span><br></font></bloc= kquote><blockquote type=3D"cite"><font face=3D"Courier New"><span>Workstatio= n > ethernet > pelorus > usb port > gpio 8,10 > console www.z= efox.org</span><br></font></blockquote><blockquote type=3D"cite"><font face=3D= "Courier New"><span>is a little clearer</span><br></font></blockquote><block= quote type=3D"cite"><font face=3D"Courier New"><span></span><br></font></blo= ckquote><blockquote type=3D"cite"><font face=3D"Courier New"><span>So: "www.= zefox.net <http://www.zefox.net/>" above is a change of report, if I u= nderstand</span><br></font></blockquote><blockquote type=3D"cite"><font face= =3D"Courier New"><span>right.</span><br></font></blockquote><blockquote type= =3D"cite"><font face=3D"Courier New"><span></span><br></font></blockquote><f= ont face=3D"Courier New"><span></span><br><span>It's my typo 8-( </span><br>= <span>The host generating console output is the Pi3 named www.zefox.org .</s= pan><br><span>The host named www.zefox.net isn't involved at all, though it i= s</span><br><span>present and I typed its name in error.</span><br><span></s= pan><br></font><blockquote type=3D"cite"><blockquote type=3D"cite"><font fac= e=3D"Courier New"><span>The Ethernet connection works well enough for all th= e other hosts that I think </span><br></font></blockquote></blockquote= ><blockquote type=3D"cite"><blockquote type=3D"cite"><font face=3D"Courier N= ew"><span>we can disregard whether it's wired or WiFi and LAN or WAN or all f= our.</span><br></font></blockquote></blockquote><blockquote type=3D"cite"><f= ont face=3D"Courier New"><span></span><br></font></blockquote><blockquote ty= pe=3D"cite"><font face=3D"Courier New"><span>You have also reported that:</s= pan><br></font></blockquote><blockquote type=3D"cite"><font face=3D"Courier N= ew"><span></span><br></font></blockquote><blockquote type=3D"cite"><font fac= e=3D"Courier New"><span>The Pi3 which reported the garbled login prompt </sp= an><br></font></blockquote><blockquote type=3D"cite"><font face=3D"Courier N= ew"><span>uses in config.txt:</span><br></font></blockquote><blockquote type= =3D"cite"><font face=3D"Courier New"><span>b@www:/boot/msdos % more config.t= xt</span><br></font></blockquote><blockquote type=3D"cite"><font face=3D"Cou= rier New"><span>init_uart_clock=3D3000000</span><br></font></blockquote><blo= ckquote type=3D"cite"><font face=3D"Courier New"><span>enable_uart=3D1</span= ><br></font></blockquote><blockquote type=3D"cite"><font face=3D"Courier New= "><span>kernel=3Du-boot.bin</span><br></font></blockquote><blockquote type=3D= "cite"><font face=3D"Courier New"><span>kernel7=3Du-boot.bin</span><br></fon= t></blockquote><blockquote type=3D"cite"><font face=3D"Courier New"><span>dt= overlay=3Dmmc</span><br></font></blockquote><blockquote type=3D"cite"><font f= ace=3D"Courier New"><span>force_mac_address=3Db8:27:eb:71:46:4f</span><br></= font></blockquote><blockquote type=3D"cite"><font face=3D"Courier New"><span= ></span><br></font></blockquote><blockquote type=3D"cite"><font face=3D"Cour= ier New"><span>This is using the mini-uart for the serial console and the</s= pan><br></font></blockquote><blockquote type=3D"cite"><font face=3D"Courier N= ew"><span>full-function UART for bluetooth. It also is not using</span><br><= /font></blockquote><blockquote type=3D"cite"><font face=3D"Courier New"><spa= n>arm_64bit=3D1 . (So armv7 support instead of aarch64 support?)</span><br><= /font></blockquote><blockquote type=3D"cite"><font face=3D"Courier New"><spa= n></span><br></font></blockquote><font face=3D"Courier New"><span></span><br= ><span>You are correct, it's using the mini-uart (which I didn't realize)</s= pan><br><span>per sysctl. The machine is running aarch64, the referenc= e to kernel7 </span><br><span>in config.txt is a mistake. Bluetooth an= d WiFi aren't used on www.zefox.org.</span><br></font></div></blockquote><di= v><br></div><div>For RPi3B*=E2=80=99s, booting as aarch64 should have arm_64= bit=3D1 in config.txt , as I understand.</div><div><br></div><div>Use of the= mini-uart is probably not a good idea for the serial console: dtoverlay=3Dd= isable-bt should also be listed, like for the other RPi3B* .</div><div><br><= /div><div>In fact, other than the force_mac_address, the general content sho= uld be like the one with arm_64bit=3D1 as far as I can tell. Do you have spe= cific reasons for needing any of the differences?</div><br><blockquote type=3D= "cite"><div dir=3D"ltr"><blockquote type=3D"cite"><font face=3D"Courier New"= ><span>https://elinux.org/RPi_Serial_Connection claims:</span><br></font></b= lockquote><blockquote type=3D"cite"><font face=3D"Courier New"><span></span>= <br></font></blockquote><blockquote type=3D"cite"><font face=3D"Courier New"= ><span>QUOTE</span><br></font></blockquote><blockquote type=3D"cite"><font f= ace=3D"Courier New"><span>. . . the less capable mini-UART with no break det= ection, no framing errors</span><br></font></blockquote><blockquote type=3D"= cite"><font face=3D"Courier New"><span>detection, no parity bit, no receive t= imeout interrupt and no DCD, DSR,</span><br></font></blockquote><blockquote t= ype=3D"cite"><font face=3D"Courier New"><span>DTR or RI signals</span><br></= font></blockquote><blockquote type=3D"cite"><font face=3D"Courier New"><span= >END QUOTE</span><br></font></blockquote><blockquote type=3D"cite"><font fac= e=3D"Courier New"><span></span><br></font></blockquote><blockquote type=3D"c= ite"><font face=3D"Courier New"><span>This contrasts with:</span><br></font>= </blockquote><blockquote type=3D"cite"><font face=3D"Courier New"><span></sp= an><br></font></blockquote><blockquote type=3D"cite"><font face=3D"Courier N= ew"><span>The Pi3 hosting the usb-serial adapter has in config.txt</span><br= ></font></blockquote><blockquote type=3D"cite"><font face=3D"Courier New"><s= pan>bob@pelorus:~ % more /boot/efi/config.txt</span><br></font></blockquote>= <blockquote type=3D"cite"><font face=3D"Courier New"><span>[all]</span><br><= /font></blockquote><blockquote type=3D"cite"><font face=3D"Courier New"><spa= n>arm_64bit=3D1</span><br></font></blockquote><blockquote type=3D"cite"><fon= t face=3D"Courier New"><span>dtparam=3Daudio=3Don,i2c_arm=3Don,spi=3Don</spa= n><br></font></blockquote><blockquote type=3D"cite"><font face=3D"Courier Ne= w"><span>dtoverlay=3Dmmc</span><br></font></blockquote><blockquote type=3D"c= ite"><font face=3D"Courier New"><span>dtoverlay=3Ddisable-bt</span><br></fon= t></blockquote><blockquote type=3D"cite"><font face=3D"Courier New"><span>de= vice_tree_address=3D0x4000</span><br></font></blockquote><blockquote type=3D= "cite"><font face=3D"Courier New"><span>kernel=3Du-boot.bin</span><br></font= ></blockquote><blockquote type=3D"cite"><font face=3D"Courier New"><span></s= pan><br></font></blockquote><blockquote type=3D"cite"><font face=3D"Courier N= ew"><span>which has the full-function UART for its serial console</span><br>= </font></blockquote><blockquote type=3D"cite"><font face=3D"Courier New"><sp= an>and is using arm_64bit=3D1 .</span><br></font></blockquote><blockquote ty= pe=3D"cite"><font face=3D"Courier New"><span></span><br></font></blockquote>= <blockquote type=3D"cite"><font face=3D"Courier New"><span>Why the variation= ?</span><br></font></blockquote><blockquote type=3D"cite"><font face=3D"Cour= ier New"><span></span><br></font></blockquote><font face=3D"Courier New"><sp= an></span><br><span>That machine is the terminal server, pelorus, on the LAN= . Its </span><br><span>internal uart does not participate in the data transm= ission chain. </span><br><span>"Hosting the usb-serial converter" was my eup= hemism for terminal server.</span><br><span></span><br><span>Please accept m= y apologies for not proofreading more carefully!</span><br><span>If there is= a better choice of terminology please tell me. </span><br><span></span><br>= <span>Thanks for your patience!</span><br><span></span><br><span>bob prohask= a</span></font><br></div></blockquote><br><div>Note: edited on an iPad. For n= ow, the computers I normally use are not available. My ability to lookup som= e types of information is greatly limited. I will soon be without internet a= ccess for some number of days.</div></body></html>= --Apple-Mail-4C62B640-776D-4FDB-BCD2-23CC7784A5FD--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B7E5DF67-4B43-401A-89DC-6F9422C95FA9>