Date: Tue, 24 Jan 2023 11:43:56 -0700 From: John Rushford <jjrushford@gmail.com> To: Fred Finster <fred@thegalacticzoo.com> Cc: freebsd-arm@freebsd.org Subject: Re: Enabling Raspberry Pi 4B Uarts, specifically uart3 Message-ID: <A57674AD-7198-4909-9B10-5B826D98B626@gmail.com> In-Reply-To: <CF334DAE-8890-4591-B8FF-4ABEBFE87E3A@gmail.com> References: <2bd8e680-df6a-cfe1-fbd2-ade1ac2d0497@thegalacticzoo.com> <CF334DAE-8890-4591-B8FF-4ABEBFE87E3A@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Fred,
Looking at the pstat -t output, I see no data available on ttyu1. I =
know that there is data coming from the GPS card as
I can see it when I switch OS to Debian. This confirms the problem =
though with the additional uarts.
pstat -t
LINE INQ CAN LIN LOW OUTQ USE LOW COL SESS PGID STATE
ttyu0 23040 0 0 2304 23064 0 2307 7 1167 1167 ICOil
ttyu1 0 0 0 0 0 0 0 4 0 0 IC
ttyv0 1920 0 0 192 1984 0 199 7 1159 1159 Oil
ttyv1 1920 0 0 192 1984 0 199 7 1160 1160 Oil
ttyv2 1920 0 0 192 1984 0 199 7 1161 1161 Oil
ttyv3 1920 0 0 192 1984 0 199 7 1162 1162 Oil
ttyv4 1920 0 0 192 1984 0 199 7 1163 1163 Oil
ttyv5 1920 0 0 192 1984 0 199 7 1164 1164 Oil
ttyv6 1920 0 0 192 1984 0 199 7 1165 1165 Oil
ttyv7 1920 0 0 192 1984 0 199 7 1166 1166 Oil
ttyv8 0 0 0 0 0 0 0 0 0 0 -
ttyv9 0 0 0 0 0 0 0 0 0 0 -
ttyva 0 0 0 0 0 0 0 0 0 0 -
ttyvb 0 0 0 0 0 0 0 0 0 0 -
pts/0 7680 0 0 768 7688 0 769 0 1336 1420 Oi
pts/1 7680 0 0 768 7688 0 769 36 1380 1380 Oi
On Jan 24, 2023, at 10:11 AM, John Rushford <jjrushford@gmail.com> =
wrote:
>=20
> Fred,
>=20
> 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
>=20
> 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:
>=20
> /boot/msdos/config.txt:
>=20
> cat msdos/config.txt:
>=20
> [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
>=20
> [pi4]
> # hdmi_safe=3D1
> armstub=3Darmstub8-gic.bin
>=20
> # dmesg|grep uart
> uart0: <PrimeCell UART (PL011)> mem 0x7e201000-0x7e2011ff irq 16 on =
simplebus0
> uart0: console (115200,n,8,1)
> uart1: <PrimeCell UART (PL011)> mem 0x7e201600-0x7e2017ff irq 43 on =
simplebus0
>=20
> The memory address 0x7e201600 corresponds to that assigned to uart3 =
in: src/freebsd-src/sys/contrib/device-tree/src/arm/bcm2711.dtsi=20
>=20
> Still no data seen
>=20
> thanks
> John Rushford
>=20
>=20
>> On Jan 24, 2023, at 6:09 AM, Fred Finster <fred@thegalacticzoo.com> =
wrote:
>>=20
>> */
>> /*
>>=20
>> */From:/*<bugzilla-noreply_at_freebsd.org>
>> */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 =
<https://forums.raspberrypi.com/viewtopic.php?t=3D244827&sid=3Df4a784a3c40=
ed0940e6fbb9f81af5015&start=3D25#p1590882>
>>=20
>>=20
>> Re: Pi-4 Activating additional UART ports
>> =
<https://forums.raspberrypi.com/viewtopic.php?t=3D244827&sid=3Df4a784a3c40=
ed0940e6fbb9f81af5015&start=3D25#p1590882>
>>=20
>> Mon Jan 06, 2020 10:36 am =
<https://forums.raspberrypi.com/viewtopic.php?p=3D1590882&sid=3D3091c9b0b9=
8ce61a2a9be011e1ef5386#p1590882>
>>=20
>> On all Pis, UART0 is a PL011 that appear to Linux as ttyAMA<n>, and =
UART1 is an 8250 clone that appears as ttyS0. On a Pi4, UART2-5 are =
additional PL011s that also appear as ttyAMA<n>. 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
>=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A57674AD-7198-4909-9B10-5B826D98B626>