From nobody Tue Jan 10 18:19:19 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 4Nrzc43hV2z2sMbF for ; Tue, 10 Jan 2023 18:19:32 +0000 (UTC) (envelope-from jjrushford@gmail.com) Received: from mail-il1-x129.google.com (mail-il1-x129.google.com [IPv6:2607:f8b0:4864:20::129]) (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 4Nrzc40Nnbz49Br for ; Tue, 10 Jan 2023 18:19:32 +0000 (UTC) (envelope-from jjrushford@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-il1-x129.google.com with SMTP id a3so873513ilp.6 for ; Tue, 10 Jan 2023 10:19:32 -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=XKtyIJ0TKEc0Ptib76sBxMeSCsGqZxTrOEGHz5Fj+gA=; b=QOKTI/d3RNXZtf28VlgOR3KObmqpzKyMeqnYdYUoxIe+0bxlguYwxzn90Cj2pyQfhD cDIAxoAmbAoO+QHSaOqRjc8XhSaT5OJrxRTFa5zCw2ejTIedefKu64//F+oqbUSXCA6s +LmhcpYQMOAy0jZHwMBYRnEfRqY7+d1wTqf3kSxa49laxuLpxw6D1XUOu5OzRcW6vWWW qZ+NSXgKLsJV9z1WQxYBHuYmF/AgDw2vPm5iVJQUa6CJ+/+0+5l2opBKUozSOsE6fIl/ w9xzc/APkG01nGVrC/MGBC5oTYwT6YcPE5+tMj9RC3cAkLZAuXkDdDoQxvUnUOdWai+0 URFw== 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=XKtyIJ0TKEc0Ptib76sBxMeSCsGqZxTrOEGHz5Fj+gA=; b=ow2DBlZYGKzsOW5nK/fCcY+QCaxEMCYys/irn9EwI0ROjpAIhyuO8EEA+H2QD9IPJZ QwYNs17OxsZmMW7FVtLMj+Ecj+MvTTzBWUpWjuX/7yJy3kynZYoeKP+WD9zhPvyfYys6 3RE0dP6+u5cjP2/gRpfHfPm3H3m628jer1UPQAsL26HSzuZBBth19LVqlLTCVQ9CFthS Xx0s5/RHJKsffn1UBjNCPaJZfVK81b1NPmDVlUdTI3pzQZNZNcJ4hfLvW3c+43mI3p1+ C/sha17TxcdMhbBdL+gJ0V9RM/UvCHtKWEDF7nVcLZIoYnZYYH6aORYl3r7pwH+qlVDu bJnA== X-Gm-Message-State: AFqh2kqSihG/C3wJDy57F6hAB450d966D0dNRQQHbfrMioFpYGv951wz 7Xw8uupngAkgBJHTWBNkvFXtLUScNOg= X-Google-Smtp-Source: AMrXdXu1Xn4Cm3pK/Zc8wD+jOY7I1dpq1Xfp/6sHjE7FPrJR/6aspRBbi3DY0o/Gqdwr88TmoXR1+A== X-Received: by 2002:a92:d1c1:0:b0:30d:899f:aed4 with SMTP id u1-20020a92d1c1000000b0030d899faed4mr12919858ilg.21.1673374771034; Tue, 10 Jan 2023 10:19:31 -0800 (PST) Received: from smtpclient.apple ([2601:280:587f:87d0:fd8d:7a9e:180e:7182]) by smtp.gmail.com with ESMTPSA id h1-20020a92d081000000b00302a9c9b4bfsm3722918ilh.44.2023.01.10.10.19.30 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 10 Jan 2023 10:19:30 -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.200.110.1.12\)) Subject: Re: Pi 4 serial ports From: John Rushford In-Reply-To: <20230110083520.4b284ec89da2c7cd8a1c8fa7@bidouilliste.com> Date: Tue, 10 Jan 2023 11:19:19 -0700 Cc: "freebsd-arm@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: References: <20230110083520.4b284ec89da2c7cd8a1c8fa7@bidouilliste.com> To: Emmanuel Vadot X-Mailer: Apple Mail (2.3731.200.110.1.12) X-Rspamd-Queue-Id: 4Nrzc40Nnbz49Br 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 Emmanuel, Thank you very much! I=E2=80=99m new to FreeBSD on pi and I guess I was = making this way to difficult. I built the rpi-firmware port and copied/enabled the uart dtb=E2=80=99s = for the uart I wish to use. =20 I rebooted and I now see the port in the kernel messages and the ttyu in = the dev tree. =20 Next I=E2=80=99ll break out my soldering iron and wire up the GPS = breakout and get it working hopefully. Cheers John > On Jan 10, 2023, at 12:35 AM, Emmanuel Vadot = wrote: >=20 >=20 > Hi John, >=20 > On Mon, 9 Jan 2023 13:43:37 -0700 > John Rushford wrote: >=20 >> Greetings, >>=20 >> I?m running FreeBSD 13.1-RELEASE on a raspberry pi 4b rev 1.4. The = pi 4 has 4 UART ports available but as far as I can tell, FreeBSD 13.1 = only supports 1 of them. >> I would like to use one of the other UART ports to wire an adafruit = GPS breakout too. I tried using the UART0 port but when I wire the GPS = breakout to it,=20 >> I run into boot issues with u-boot and console logging. I know that = in other OS?s such as raspian or ubuntu, you are able to enable the = additional UARTS in config.txt. >> Thinking that FreeBSD might support this I tried adding = ?dtoverlay=3Duartx? where x is 0 to 3 but I?m not seeing in any kernel = logging that these ports were enabled and >> I don?t see any additional ttyu?s in the dev tree. >>=20 >> So my question, does FreeBSD support these additional UARTS and if = so, how do I enable them so that I may use one for the GPS breakout? >>=20 >> Thanks >> John >=20 > In the rpi-firmware package there is some uartXX.dtbo > By looking at them those overlays are there for enabling the other > uart port. > Just put the ones you want to use on the FAT partition of your sdcard > in the /overlays/ directory and add in config.txt "dtoverlay=3DuartXXX" >=20 > Cheers, >=20 > --=20 > Emmanuel Vadot