From nobody Tue Jan 24 17:11:20 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 4P1YR95t31z316KL for ; Tue, 24 Jan 2023 17:11:33 +0000 (UTC) (envelope-from jjrushford@gmail.com) Received: from mail-il1-x136.google.com (mail-il1-x136.google.com [IPv6:2607:f8b0:4864:20::136]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P1YR946llz3Prk for ; Tue, 24 Jan 2023 17:11:33 +0000 (UTC) (envelope-from jjrushford@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-il1-x136.google.com with SMTP id i1so7699929ilu.8 for ; Tue, 24 Jan 2023 09:11:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=k89bQXy6x5hVui7a9UwmTMMbqybWZkgD9FWA69N/GF4=; b=i9gBA0mRSc4s44BNygHyf7DstKiuUNnZodT/WLImlZ+2ciAOVS7dpiFFP5Gp8G4Sj2 P99cnIpifTmDD9XMQBMgi6KXOZAu8ciUZKbBLuSfhAgtzwwxBLXxZ72BYcox9YhqSEjB 8rOIpk1IqNvObs+NqW3cp4f14Wu6pfLgwd9apYb8sgDSry4/2P/3DeR53fd2xXz/KSm2 Biu1dW6HCMWL7GQuqQ7Aczje98Degyv2eah6vcvPVNvvBeqxIsI+Nk5vlc3a3yVr2cqi uU+gDRVFZuedlr+lJSt61cQXUPyrbYfi8tSZsyAb8zcH0vvxCOv01YT9/C6BA4c7gXWg cxeQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=k89bQXy6x5hVui7a9UwmTMMbqybWZkgD9FWA69N/GF4=; b=xqkjS62IEV15qn+a3KNk/llu2EQ1WUJiNsbOyEmmU2dlqtnZp0IN5WQbxUxLohDuXT oMJcYciGgImxDA7/EP/vQMvAL/qfmldsYaSFlCCqqkMZBVTil5tcf9wZKF+f8HF9kcNq FUTGcWC7g18wQPKik4yrNbwI5GwDcxxPYgAt1qhRqxa9aZd8yg4/7DrseK0beIx2HcoR k4ZAcnyi9X8hK+MS+19eV0FC3zpGKnvr+OU0F97jqTJJGzDByu16fOzUWuwvotMp1Vxe tSFH+DNQAQZtk1kyFlWACMGDp8PbL+zhB3PsLIi4p4DureRdPQY7yHEpY0spaXrdJ//d 9qCA== X-Gm-Message-State: AFqh2koOWEE53UXtpPr4/WTln7NsItZhVsv0Ye4nd9bsnpAZ72qX3hAp 4cyymknE4p/+3OuuU566OQXorXV1x/a3Sg== X-Google-Smtp-Source: AMrXdXsrCyDIvNGQ1BhkJZq0z30ZkKrltsVHudQXJNVYKYepfjbgZ9tV3SJKfoW6jSqucMxQOVz03A== X-Received: by 2002:a05:6e02:1a6c:b0:30f:40fc:7a2b with SMTP id w12-20020a056e021a6c00b0030f40fc7a2bmr19755848ilv.32.1674580292493; Tue, 24 Jan 2023 09:11:32 -0800 (PST) Received: from smtpclient.apple ([2601:280:587f:1450:84e6:9743:8888:b2e8]) by smtp.gmail.com with ESMTPSA id g8-20020a0566380bc800b003a60e059970sm856590jad.84.2023.01.24.09.11.31 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 24 Jan 2023 09:11:31 -0800 (PST) Content-Type: text/plain; charset=utf-8 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 (Mac OS X Mail 16.0 \(3731.300.101.1.3\)) Subject: Re: Enabling Raspberry Pi 4B Uarts, specifically uart3 From: John Rushford In-Reply-To: <2bd8e680-df6a-cfe1-fbd2-ade1ac2d0497@thegalacticzoo.com> Date: Tue, 24 Jan 2023 10:11:20 -0700 Cc: freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <2bd8e680-df6a-cfe1-fbd2-ade1ac2d0497@thegalacticzoo.com> To: Fred Finster X-Mailer: Apple Mail (2.3731.300.101.1.3) X-Rspamd-Queue-Id: 4P1YR946llz3Prk X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N Fred, This is my /boot/loader.conf. After rebooting, no change and no data on = uart3. BTW, FreeBSD does=20 not create a /dev/ttyU1. =46rom the config.txt with dtoverlay=3Duart3, = FreeBSD creates a /dev/ttyu1 ucom_load=3D"YES" umodem_load=3D"YES" usb_template_load=3D"YES" hw.usb.template=3D3 umodem_load=3D"YES" umodem_load=3D"YES" # Multiple console (serial+efi gop) enabled. boot_multicons=3D"YES" boot_serial=3D"YES" # Disable the beastie menu and color beastie_disable=3D"YES" loader_color=3D"NO" kern.vty=3Dvt gpiopps_load=3D"YES"This is my /boot/loader.conf: /boot/msdos/config.txt: cat msdos/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 dtoverlay=3Dpps-gpio,gpiopin=3D18 dtoverlay=3Duart3 enable_uart=3D1 [pi4] # hdmi_safe=3D1 armstub=3Darmstub8-gic.bin # dmesg|grep uart uart0: mem 0x7e201000-0x7e2011ff irq 16 on = simplebus0 uart0: console (115200,n,8,1) uart1: mem 0x7e201600-0x7e2017ff irq 43 on = simplebus0 The memory address 0x7e201600 corresponds to that assigned to uart3 in: = src/freebsd-src/sys/contrib/device-tree/src/arm/bcm2711.dtsi=20 Still no data seen thanks John Rushford > On Jan 24, 2023, at 6:09 AM, Fred Finster = wrote: >=20 > */ > /* >=20 > */From:/* > */Date:/*Sun, 22 Jan 2023 21:36:36 UTC >=20 > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D269104 >=20 > Bug ID: 269104 > Summary: The uarts2 - uarts5 do not function on raspberry pi = 4B > Product: Base System > Version: 13.1-RELEASE > Hardware: arm64 > OS: Any > Status: New > Severity: Affects Only Me > Priority: --- > Component: arm > Assignee: freebsd-arm@FreeBSD.org > Reporter: jjrushford@gmail.com >=20 > I=E2=80=99ve tried using the additional serial ports that are = available with a > raspberry pi 4B by enabling them in config.txt and when I try to read = data on > them, I see nothing. >=20 > Specifically, I=E2=80=99ve wired an Adafruit ultimate GPS to uart3, = gpio pins 4 and 5. > I=E2=80=99ve built the RPI-firmware port and copied the uart0-5 = dtb=E2=80=99s to > /boot/msdos/overlays. I then enable uart3 in /boot/msdos/config.txt = with > dtoverlay=3Duart3 and reboot. After boot, I see that FreeBSD has = created > /dev/ttyu1 and /dev/cuau1 in the dev tree for uart3. When I try = reading from > ttyu1 or cuau1, I do not see any data whatsoever. I=E2=80=99ve set = the baud rate to > 9600 and disabled flow control but still no data is seen. If I change = the > wiring to use ttyu0, gpio pins 14 and 15, I do see data there. >=20 > Just to verify the hardware, I installed a different SD card with = raspberry pi > OS, Debian, and enabled uart3 in config.txt. When I read the = /dev/ttyAMA1 I do > see the NMEA time stamps coming in uart3 at 9600 baud with no issue. = Next I > reboot back to FreeBSD 13.1, I cannot see any data from The GPS card = on ttyu1 > or cuau1. >=20 > --=20 > You are receiving this mail because: > You are the assignee for the bug. >=20 > In the aarch64 arm64 Raspberry Pi FreeBSD, maybe you need to enable = some kernel modules > kldstat > kldload ucom umodem usb_template > sysctl hw.usb.template=3D3 >=20 > add in file /boot/loader.conf >=20 > ucom_load=3D"YES" > umodem_load=3D"YES" > usb_template_load=3D"YES" > hw.usb.template=3D3 >=20 >=20 > *cu -s 9600 -l /dev/ttyU1 What do you see? or rather cu? :>) Do = report back success or failure or changes necessary to make work, = please. = *https://forums.raspberrypi.com/viewtopic.php?t=3D244827&sid=3Df4a784a3c40= ed0940e6fbb9f81af5015&start=3D25#p1590882 = >=20 >=20 > Re: Pi-4 Activating additional UART ports > = >=20 > Mon Jan 06, 2020 10:36 am = >=20 > On all Pis, UART0 is a PL011 that appear to Linux as ttyAMA, and = UART1 is an 8250 clone that appears as ttyS0. On a Pi4, UART2-5 are = additional PL011s that also appear as ttyAMA. The number starts at 0 = for the first enabled PL011 and counts up through all the enabled = interfaces. The numbering is stable for any given combination of UARTs, = but enabling or disabling one can change the number assignments of = others. >=20 > /PL011 appear to FreeBSD/*as /dev/ttyUx So I wonder if one has to = enable ucom and umodem and usb_template to view serial data comming back = over what looks like a USB to serial interface? Your thoughts? = https://ghostbsd-arm64.blogspot.com/2023/01/hookup-gdb-to-black-magic-prob= e-v23.html * >=20 > My setup trying to connect to USB serial port under X86_64 FreeBSD 13 = to a Black Magic Probe >=20 >=20 > --=20 > Fred Finster > fred@thegalacticzoo.com > +1 971-718-9144 > https://GhostBSD-ARM64.blogspot.com > https://ghostbsd.org >=20