From: <rs@ti.com>
To: Anshul Dalal <anshuld@ti.com>, <robertcnelson@gmail.com>,
<ayush@beagleboard.org>, <Erik.Welsh@octavosystems.com>,
<trini@konsulko.com>, <afd@ti.com>, <xypron.glpk@gmx.de>,
<ilias.apalodimas@linaro.org>, <sjg@chromium.org>
Cc: <u-boot@lists.u-boot-project.org>
Subject: [PATCHv5 0/3] k3-am62-pocketbeagle2: add board and variant support
Date: Thu, 30 Jul 2026 16:53:17 -0500 [thread overview]
Message-ID: <20260730215319.965327-2-rs@ti.com> (raw)
From: Randolph Sapp <rs@ti.com>
Resubmitting with a synced rm-cfg.yaml and tuned diff parameters. We desperately
need to add documentation about how the rm-cfg.yaml is generated here. And the
beagleplay needs to get it's rm-cfg resynced with am62x at some point.
Since it's been decided internally to follow along with what Zephyr is doing and
make a completely separate device tree for the 1GB + eMMC Industrial board, I'm
resubmitting v3 with the variant support patch dropped. We will circle back to
enable the Industrial part once the dt has been accepted kernel side.
See the following link for more information regarding that decision:
https://lore.kernel.org/u-boot/DJLTHZL0ERIG.JV1UL67GFIVJ@ti.com/
Add initial board support for the PocketBeagle 2 from BeagleBoard.org. This is
based on the current official series from Robert Nelson [1] and work from Bryan
Brattlof [2].
Now that the various memory issues have been resolved we can clearly see at
runtime that there's an issue with the current device. One of our reservations
overlaps with the u-boot stack. To get around this we'll need to change the
relocation address to something we know will not collide.
[1] https://github.com/beagleboard/u-boot/tree/v2026.01-am62-pocketbeagle2
[2] https://github.com/bryanbrattlof/beagleboot/tree/b4/pb2i
Bryan Brattlof (1):
arm: mach-k3: am62: add &main_uart6 to clock and pwr tree
Randolph Sapp (2):
k3-am62-pocketbeagle2: add initial board support
k3-am62-pocketbeagle2: add support for efi capsules
arch/arm/dts/Makefile | 1 +
...> k3-am62-pocketbeagle2-ddr4-1600MTs.dtsi} | 92 ++---
.../arm/dts/k3-am62-pocketbeagle2-u-boot.dtsi | 336 ++++++++++++++++++
arch/arm/dts/k3-am62-r5-pocketbeagle2.dts | 35 ++
arch/arm/mach-k3/am62x/Kconfig | 1 +
arch/arm/mach-k3/r5/am62x/clk-data.c | 19 +-
arch/arm/mach-k3/r5/am62x/dev-data.c | 5 +-
board/beagle/pocketbeagle2/Kconfig | 60 ++++
board/beagle/pocketbeagle2/MAINTAINERS | 10 +
board/beagle/pocketbeagle2/Makefile | 9 +
.../board-cfg.yaml | 0
.../{beagleplay => pocketbeagle2}/pm-cfg.yaml | 0
board/beagle/pocketbeagle2/pocketbeagle2.c | 84 +++++
board/beagle/pocketbeagle2/pocketbeagle2.env | 26 ++
.../pocketbeagle2}/rm-cfg.yaml | 0
.../sec-cfg.yaml | 0
...onfig => am62_pocketbeagle2_a53_defconfig} | 25 +-
...config => am62_pocketbeagle2_r5_defconfig} | 11 +-
doc/board/beagle/am62_pocketbeagle2.rst | 279 +++++++++++++++
doc/board/beagle/index.rst | 1 +
include/configs/pocketbeagle2.h | 39 ++
21 files changed, 966 insertions(+), 67 deletions(-)
copy arch/arm/dts/{k3-am62x-sk-ddr4-1600MTs.dtsi => k3-am62-pocketbeagle2-ddr4-1600MTs.dtsi} (97%)
create mode 100644 arch/arm/dts/k3-am62-pocketbeagle2-u-boot.dtsi
create mode 100644 arch/arm/dts/k3-am62-r5-pocketbeagle2.dts
create mode 100644 board/beagle/pocketbeagle2/Kconfig
create mode 100644 board/beagle/pocketbeagle2/MAINTAINERS
create mode 100644 board/beagle/pocketbeagle2/Makefile
copy board/beagle/{beagleplay => pocketbeagle2}/board-cfg.yaml (100%)
copy board/beagle/{beagleplay => pocketbeagle2}/pm-cfg.yaml (100%)
create mode 100644 board/beagle/pocketbeagle2/pocketbeagle2.c
create mode 100644 board/beagle/pocketbeagle2/pocketbeagle2.env
copy board/{ti/am62x => beagle/pocketbeagle2}/rm-cfg.yaml (100%)
copy board/beagle/{beagleplay => pocketbeagle2}/sec-cfg.yaml (100%)
copy configs/{am62x_beagleplay_a53_defconfig => am62_pocketbeagle2_a53_defconfig} (88%)
copy configs/{am62x_beagleplay_r5_defconfig => am62_pocketbeagle2_r5_defconfig} (89%)
create mode 100644 doc/board/beagle/am62_pocketbeagle2.rst
create mode 100644 include/configs/pocketbeagle2.h
--
2.55.0
next reply other threads:[~2026-07-30 21:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 21:53 rs [this message]
2026-07-30 21:53 ` [PATCHv5 1/3] arm: mach-k3: am62: add &main_uart6 to clock and pwr tree rs
2026-07-30 21:53 ` [PATCHv5 2/3] k3-am62-pocketbeagle2: add initial board support rs
2026-07-30 22:07 ` Andrew Davis
2026-07-30 21:53 ` [PATCHv5 3/3] k3-am62-pocketbeagle2: add support for efi capsules rs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260730215319.965327-2-rs@ti.com \
--to=rs@ti.com \
--cc=Erik.Welsh@octavosystems.com \
--cc=afd@ti.com \
--cc=anshuld@ti.com \
--cc=ayush@beagleboard.org \
--cc=ilias.apalodimas@linaro.org \
--cc=robertcnelson@gmail.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.u-boot-project.org \
--cc=xypron.glpk@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.