From nobody Fri Dec 29 03:40:30 2023 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T1WPC24Qwz55M3g for ; Fri, 29 Dec 2023 03:40:47 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic312-25.consmr.mail.gq1.yahoo.com (sonic312-25.consmr.mail.gq1.yahoo.com [98.137.69.206]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4T1WPB6HBcz4H0V for ; Fri, 29 Dec 2023 03:40:46 +0000 (UTC) (envelope-from marklmi@yahoo.com) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1703821244; bh=u7l9k+Iv5QinV75Cz5FhiQ8RqxySD3hrezKdi/vV4xQ=; h=From:Subject:Date:References:Cc:In-Reply-To:To:From:Subject:Reply-To; b=Uy+N0unA3DPO5WjXTKF9S2sZhBFwJuDyx8Qf4dWWVSYt8kcEZNfGPP2E5I9iPuxCMbJcmD16IkDaS/jkGoFQLXf9c8Oq6mEjVQ+/yD9BMjE07QMF8IYyIuv4+5tl4fW0UDcHmIYdSm1huLgJLPTqsLvqNIA2LoUV/gFH41wu84hwsdkf/9mC+opSf57vqvL4t/UvjRmeSmIjdP65kN1syBA/+BwEpBWptjpg1SAUcKjK6NQgPHAnlwwdHn/8ELEfrEdow+D+X7kqyYzGaWmRUIrCks15TZ/nn3VwaVxtGrakKhE7Q87aty7M9ldGh60f3JUqgX5G34CdjlmOaEDn+A== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1703821244; bh=8mJwPwHzQSeJXwzOe1tAfR10qeMV54kL0R5Pfgim2E+=; h=X-Sonic-MF:From:Subject:Date:To:From:Subject; b=JaVlH49MbiwPy0XL0DGKGlfQKiH+l0qm1wzXhIbsE+LwsP7kPLrSKKrxlppC6cO3B+lyn5k0DyM/N7N2GqGqTL55SCq5PCqnrZVcEeB7gM4fqk7Czoz8yacLJMP1WG1om9tXd0k1N2dVltEzcrmTlqKckQncV/lTc6IxrF5f+CTantWpMP3t3XIdtp4GccG+40Fw8UTGmC443QiBaDYTzdoY4AE9X5NJHD73G2Pn9iKZXQ4d1E25V/fxfJPWrJjJ4UlnzKSXQqOMuoOxJEgM5GV1AR7gPdm3IGbaHdhso9EtHSpiJr5f0l1apF5O83xwMt242AkNVgRdln2lnju2dw== X-YMail-OSG: BRuiYMgVM1kaMeS5iY6W0Dc_6fQxXbis.A4pY.5RQi96wZXqFB3KYbaedG8.In5 Ab19B3sL5Ro27EqeAs8uA0ljj9kN2a6qerqddLTQFnMRaMpUdfr9S2k4q8AweoGRnc5v15qB8v_U FsqA5Pl6w.f7pfXKyUNsg1sJk7b_1hiB2F5GDz3JaAMAiinT0l4hSprL9WY.oa54K.5ShOnvgf9k uSkytmZBzAnkHyQGrbPEq.9JYV.5Cu3go047M7W92eepGRjNl.uHk_G8EQj2wmsrQQydvRaLMCl2 gkNrPn9xwIAntnxqVsvPEvB94AI723n49SbyXkHhvYgIUJH_QWYhzK10JGZrWG.zBe8nckX80rjl ZlpuO1v6egigxP6omAFJAuEsvi_MhU0zi_xA6sz7aPjTQ46enoRit6iU1phFGXmd75_IMA9s8oYN 5a0cn8Mnd.u6dYVPYHXTsUjswtdFRTWrdPuKTQtqtN1g0y7Jbw9fvlBQOUU9d8Y0GznkYgvTQKBv JcUB1.UCCvTzv13gGJb8A9OwXJONd3wCFRhTrGvtDUuAwxgOtYs1Xvi6QQoX9KYryT1DxVz3KQOb Jk45jDF2wdjE1ztIN4lTNGv5f.O9C45vSbnbpSy6i.rmJcKNn.kOjvtQIH_A3T_p.XFBDaxyhMEJ C4SZSdjnoLS8noIcjhSXEvpRL3fVVUA73K7RC71qUDhg5ZnoBzxTE1bHTZqnbb_GFkTK70HPCZFK RriGdkv.ID0SgKGMt3vHp2eD_pcvzOq.2Ymqa36jt534FHvw49Lbhjy83NLTvA7dZWGKuYZWAOiY j7q5FbgdnkLcbRGsu0W11ip4mql4ZvZzAZWJBHdHGPA0ZofXlxBlgMGNYnCT3TARWW3Tsf71ofQM BCx.XMHgbTycF0RzsMdaPBduPi9S8v1zsi21n5LK4T4LkKfT3hHN_ZsqE0r7D1WrN8q4vZsI_lu7 I9RL7STLvtoj_uD_3mtz9DijI3QYZIxCd45wu3QpVUh34c8W0fQCikM5S3MTe4dl.4tkcNdASc19 5WVD32ropArdB5IknmK8_gCRU5InhN4ktSTN6nbnsatSjR8Geh2uGhNieQipMNC65J_5pj5iSE3B xrbsC4JWQsYmgsjzkzPh5Y48NbRxq_d3OETVojkx6KNNrJT85OBSm_lw12iJ3O.y465fK0uL.5tr 5jnrqkIK1amzfWwAXhNj7grNAF6fuCKA7S8hGujn4Mqk4Q5GJaHUMHwWZ_BfPwQ_vUHoaMQJnY6a AOwi9eOLEsOpW9sDksH3k3PsJxgC.P_q_m6gAqkh7tmYFjGUM4DG6jr90sUV1bvw5HSiCvRiG6Mj cT1rHlNzi.9GtK05Hxl_0oY61zcb4PTRMd99LufPVIiRqDPI5d3240GJ_gksBfoPLGecp4vbqjyp ShwJ24.GuYnXeDGzDJKFT0TYbXkFuGUekHVC5mUAzyGMPImrG4Yoq_e08GvkoCnmepNLJ0bwE.rf xCeUp04.XHaFpTONResYt0QIWSUqK7gGU8hXfdlspTWFACK0.S6TcCjzjJGTpayXxM79gCN6AhC3 8CmXedEu2DwoZTmOjhYaOh2H3i10NC7eXKJPVVBmzFo6f6ec2TNxbv6BvBxHt.Qhgbl6lu2d_lB. 7V5coWcJmiyj9jdyIBx.bGhcF2yHJGE2wtxf8qw4UxQTUNtA7xqqaSpZnfMXkLJzWR1IN.w3WqgL _JXMryvahgz2RADbTZzDnaAOWIPFL0eUUTyMTMirSOKTt5CCT2I3aGaV5ulqU5PIodT6T3b2nulh ZTRP2og1W56oNT1..f6WL00In55L5HmqczLV4tU9549u.dHAmz8dV2wTr0SaRqha.fs_ojUNOtmM 6K9xSjqNlWJ5Sr4DSMWVmZuUhgqDt5aIVs2YbiXW4qI.WaXlKDMMoAydI7zM.zjrRycKMlpkBRWv 4Iuepx_eSgTn6xqW_ptyioRO837uN2AUUo8Dmt85RFYQ64QUdLRuVepfoQU2ScjHji06DWaihjqv siXItN7CHpUz9q2MT0UqZgNJdQEAH0tOHxXOVMMpLuk5BJINcRaW0g4OrYdir3GrD7MtKAN363YW VNTojVBLs_yktqKsmaDJKGwXWzV6xf3l__R0kWbPm5jLoV9haGZLyEdYvGbCrZT5Q7u_.Wx72pDA 64q1uNU1UI1.hw6bOXKfRLW65MPhMViexcFP6u0cy3z0rATf3gUS5wSy1CKlZPSlnjnVweBYkUJD e..I9P0uMN2z_TY4vIn9rDeQRTNZQYwxHbapcX90kylbhszxQD8LEWIF6NAhxReV9naF1Kj4tfN6 B X-Sonic-MF: X-Sonic-ID: b77f194d-b402-4e88-8963-4ae3db122c34 Received: from sonic.gate.mail.ne1.yahoo.com by sonic312.consmr.mail.gq1.yahoo.com with HTTP; Fri, 29 Dec 2023 03:40:44 +0000 Received: by hermes--production-gq1-6949d6d8f9-gwrdd (Yahoo Inc. Hermes SMTP Server) with ESMTPA ID d4727a9b73cc6e6f5a5c8ed07ffcb494; Fri, 29 Dec 2023 03:40:41 +0000 (UTC) Content-Type: multipart/alternative; boundary=Apple-Mail-4C62B640-776D-4FDB-BCD2-23CC7784A5FD Content-Transfer-Encoding: 7bit From: Mark Millard List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org Mime-Version: 1.0 (1.0) Subject: Re: USB-serial adapter suggestions needed Date: Thu, 28 Dec 2023 19:40:30 -0800 Message-Id: References: Cc: John F Carr , ticso@cicely.de, Marcin Cieslak , freebsd-arm@freebsd.org In-Reply-To: To: bob prohaska X-Mailer: iPad Mail (21C62) X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/20, country:US] X-Spamd-Bar: ---- X-Rspamd-Queue-Id: 4T1WPB6HBcz4H0V --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 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 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 " 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
On Dec 28, 2= 023, at 18:46, bob prohaska <fbsd@www.zefox.net> wrote:

=
=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:

On Wed, Dec 27, 2023 at 12:27:33PM -0800, Mark Mil= lard wrote:

Overall I've not been able to understand what t= he
(various?) hypothesized stage-by-stage byte flow
<= /font>
paths are in these notes.

=

Maybe this will help. The path is
=

work= station> Ethernet > terminal server:usb-serial > serial wires> G= PIO 8/10

I hesitated to use the words "terminal= server" because that has implications
(distinct IP address, multiple serial interfaces) that don't e= xist here.

<= /font>
The workstation is a RasPiOS Pi4, th= e Pi3 host called pelorus is the terminal
server and the GPIO pins are on the Pi3 host named www.zef= ox.net .

Your prior messages reporte= d text referencing .org, such as:

FreeBSD/arm64 (w= ww.zefox.org) (ttyu1)

and:
<= span>No, the garbled login prompt originates from www.zefox.org's
=
serial console.
<= font face=3D"Courier New">
and:

<= /font>
Understood, it's been hard to articulate 8-( Maybe
Workstatio= n > ethernet > pelorus > usb port > gpio 8,10 > console www.z= efox.org
is a little clearer

So: "www.= zefox.net <http://www.zefox.net/>" above is a change of report, if I u= nderstand
right.


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 i= s
present and I typed its name in error.

The Ethernet connection works well enough for all th= e other hosts  that I think
we can disregard whether it's wired or WiFi and LAN or WAN or all f= our.

You have also reported that:

The Pi3 which reported the garbled login prompt
uses in config.txt:
b@www:/boot/msdos % more config.t= xt
init_uart_clock=3D3000000
enable_uart=3D1
kernel7=3Du-boot.bin
dt= overlay=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
<= /font>
arm_64bit=3D1 . (So armv7 support instead of aarch64 support?)
<= /font>

You are correct, it's using the mini-uart (which I didn't realize)
per sysctl.  The machine is running aarch64, the referenc= e to kernel7
in config.txt is a mistake.  Bluetooth an= d WiFi aren't used on www.zefox.org.

For RPi3B*=E2=80=99s, booting as aarch64 should have arm_64= bit=3D1 in config.txt , as I understand.

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>
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?

https://elinux.org/RPi_Serial_Connection claims:
=
QUOTE
. . . the less capable mini-UART with no break det= ection, no framing errors
detection, no parity bit, no receive t= imeout 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]
<= /font>
arm_64bit=3D1
dtparam=3Daudio=3Don,i2c_arm=3Don,spi=3Don
dtoverlay=3Dmmc
dtoverlay=3Ddisable-bt
de= vice_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= ?


That machine is the terminal server, pelorus, on the LAN= . Its
internal uart does not participate in the data transm= ission chain.
"Hosting the usb-serial converter" was my eup= hemism for terminal server.

Please accept m= y apologies for not proofreading more carefully!
If there is= a better choice of terminology please tell me.

= Thanks for your patience!

bob prohask= a

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.
= --Apple-Mail-4C62B640-776D-4FDB-BCD2-23CC7784A5FD--