From: "Marko Mäkelä" <marko.makela@iki.fi>
To: Robert Nelson <robertcnelson@gmail.com>
Cc: Randolph Sapp <rs@ti.com>,
Erik Welsh <Erik.Welsh@octavosystems.com>,
Anshul Dalal <anshuld@ti.com>,
bb@ti.com, nm@ti.com, trini@konsulko.com, afd@ti.com,
u-boot@lists.denx.de
Subject: Re: [PATCH 2/3] k3-am62-pocketbeagle2: add initial board support
Date: Mon, 20 Apr 2026 21:20:30 +0300 [thread overview]
Message-ID: <aeZubllYVLLpznWr@kehys.lan> (raw)
In-Reply-To: <CAOCHtYin=6r86ThsagZrdFu5+_b2ACGmMZs3yK3tPd45PXJw4w@mail.gmail.com>
Sun, Apr 19, 2026 at 10:08:56AM -0500, Robert Nelson wrote:
>On Sun, Apr 19, 2026 at 8:54 AM Marko Mäkelä <marko.makela@iki.fi> wrote:
>>
>> Hi Robert,
>>
>> Sat, Apr 18, 2026 at 12:53:59PM -0500, Robert Nelson wrote:
>> >Please don't upgrade to the 12.x.y.z0 branch of ti-linux-firmware
>> >
>> >After this commit you can't even upgrade to `v11.02.09` without other changes!
>> >
>> >https://github.com/u-boot/u-boot/commit/7403d26bea36315f2008ed3ef80125b094c0bafb
>>
>> I downgraded to firmware 11.2.5 "Fancy Rat", but that didn't allow me to
>> see any further messages.
>>
>> >I'm pretty sure OpTee 4.10.0 is safe, but otherwise this is my current
>> >stable branch:
>> >
>> >https://github.com/beagleboard/u-boot-pocketbeagle2/blob/main/version.sh
>>
>> I tried to choose the same versions: OPTEE 4.9.0, TI-firmware 11.02.11
>> (strangely, also this one identifies as 11.2.5; I should always build
>> everything from the scratch), and TrustedFirmware-A v2.14.0 a.k.a.
>> lts-v2.14.0, because I did not find any tag for v2.14.1. The U-boot fork
>> that I'm trying to build is already the same one. The boot process would
>> seem to always hang at the same spot: before switching to the 64-bit
>> u-boot.
>
>it's showing up in this repo
>
>https://github.com/TrustedFirmware-A/trusted-firmware-a/tags
Thank you. Somehow I was missing the tag:
Fetching origin
From https://git.trustedfirmware.org/TF-A/trusted-firmware-a
* [new tag] lts-v2.14.1 -> lts-v2.14.1
Replacing the TF-A didn't make a difference either. I guess I will
switch to another (non-trusted-firmware) development platform until a
revised update is available.
Marko
next prev parent reply other threads:[~2026-04-20 18:20 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 22:37 [PATCH 0/3] k3-am62-pocketbeagle2: add board and variant support rs
2026-03-17 22:37 ` [PATCH 1/3] arm: mach-k3: am62: add &main_uart6 to clock and pwr tree rs
2026-03-17 22:37 ` [PATCH 2/3] k3-am62-pocketbeagle2: add initial board support rs
2026-03-20 9:29 ` Anshul Dalal
2026-03-20 15:32 ` Robert Nelson
2026-03-23 19:37 ` Randolph Sapp
2026-03-23 19:46 ` Robert Nelson
2026-03-26 0:34 ` Randolph Sapp
2026-03-26 23:23 ` Randolph Sapp
2026-03-27 14:25 ` Marko Mäkelä
2026-03-27 14:53 ` Robert Nelson
2026-03-27 19:15 ` Marko Mäkelä
2026-03-28 8:18 ` Marko Mäkelä
2026-03-28 16:39 ` Robert Nelson
2026-03-29 17:13 ` Marko Mäkelä
2026-03-30 14:41 ` Robert Nelson
2026-04-18 15:02 ` Marko Mäkelä
2026-04-18 17:53 ` Robert Nelson
2026-04-19 13:54 ` Marko Mäkelä
2026-04-19 15:08 ` Robert Nelson
2026-04-20 18:20 ` Marko Mäkelä [this message]
2026-03-30 23:57 ` Randolph Sapp
2026-03-31 16:13 ` Robert Nelson
2026-03-31 22:54 ` Randolph Sapp
2026-03-17 22:38 ` [PATCH 3/3] k3-am62-pocketbeagle2: add support for 1GB variant rs
2026-03-20 10:10 ` Anshul Dalal
2026-03-20 15:26 ` Robert Nelson
2026-03-23 18:38 ` Randolph Sapp
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=aeZubllYVLLpznWr@kehys.lan \
--to=marko.makela@iki.fi \
--cc=Erik.Welsh@octavosystems.com \
--cc=afd@ti.com \
--cc=anshuld@ti.com \
--cc=bb@ti.com \
--cc=nm@ti.com \
--cc=robertcnelson@gmail.com \
--cc=rs@ti.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.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