From: "Marko Mäkelä" <marko.makela@iki.fi>
To: rs@ti.com
Cc: robertcnelson@gmail.com, ayush@beagleboard.org,
Erik.Welsh@octavosystems.com, anshuld@ti.com, bb@ti.com,
trini@konsulko.com, afd@ti.com, xypron.glpk@gmx.de,
ilias.apalodimas@linaro.org, sjg@chromium.org,
u-boot@lists.denx.de
Subject: Re: [PATCHv3 0/4] k3-am62-pocketbeagle2: add board and variant support
Date: Fri, 26 Jun 2026 20:59:26 +0300 [thread overview]
Message-ID: <aj69_uiqzmGuXql-@kehys.lan> (raw)
In-Reply-To: <20260624211949.327905-1-rs@ti.com>
Hi Randolph, all,
I tested this together with the ECDSA patch series v8, on top of the
current u-boot master.
I built a signed FIT image with Linux v7.1, target load address
0x84000000 and device tree address 0x83000000. This did not clash with
the $loadaddr of 0x82000000; the kernel address 0x81000000 would cause
u-boot to crash and reboot.
The kernel booted fine, but the
https://www.beagleboard.org/distros/pocketbeagle-2-debian-13-5-2026-05-19-minimal-v6-12-x-ti
user space would fail to start up ZRAM. I guess it's simply because I
did not make any kernel modules available yet. I was able to get into
the login screen and shut down the system nevertheless.
My ultimate goal is to set up trusted boot on top of TF-A. The
PocketBeagle 2 is a convenient development platform.
With best regards,
Marko
prev parent reply other threads:[~2026-06-26 17:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-24 21:19 [PATCHv3 0/4] k3-am62-pocketbeagle2: add board and variant support rs
2026-06-24 21:19 ` [PATCHv3 1/4] arm: mach-k3: am62: add &main_uart6 to clock and pwr tree rs
2026-06-24 21:19 ` [PATCHv3 2/4] k3-am62-pocketbeagle2: add initial board support rs
2026-06-24 21:19 ` [PATCHv3 3/4] k3-am62-pocketbeagle2: add support for 1GB variant rs
2026-06-24 23:29 ` Randolph Sapp
2026-06-25 8:21 ` Anshul Dalal
2026-06-29 20:32 ` Randolph Sapp
2026-06-30 15:17 ` Bryan Brattlof
2026-06-24 21:19 ` [PATCHv3 4/4] k3-am62-pocketbeagle2: add support for efi capsules rs
2026-06-26 17:59 ` Marko Mäkelä [this message]
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=aj69_uiqzmGuXql-@kehys.lan \
--to=marko.makela@iki.fi \
--cc=Erik.Welsh@octavosystems.com \
--cc=afd@ti.com \
--cc=anshuld@ti.com \
--cc=ayush@beagleboard.org \
--cc=bb@ti.com \
--cc=ilias.apalodimas@linaro.org \
--cc=robertcnelson@gmail.com \
--cc=rs@ti.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox