All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rasmus Villemoes <ravi@prevas.dk>
To: <u-boot@lists.denx.de>
Cc: Tom Rini <trini@konsulko.com>
Subject: Re: [PATCH] am335x: add support for loading u-boot from multiple offsets
Date: Thu, 22 Jan 2026 14:49:44 +0100	[thread overview]
Message-ID: <87ecnhrc3r.fsf@prevas.dk> (raw)
In-Reply-To: <20260122131728.1551365-1-ravi@prevas.dk> (Rasmus Villemoes's message of "Thu, 22 Jan 2026 14:17:28 +0100")

On Thu, Jan 22 2026, Rasmus Villemoes <ravi@prevas.dk> wrote:

> The am335x knows nothing about eMMC boot partitions, so in order to
> implement an update procedure of the bootloader which is robust
> against power failure or other interruptions, one must make use of the
> fact that ROM code on the am335x looks for a valid first stage
> bootloader at several different offsets.

Additional info I had written under the --- separator, but for some
reason didn't make it into the mail:

I finally got around to follow up on https://lore.kernel.org/u-boot/871prgzuui.fsf@prevas.dk/ .

I'm not at all sure about the naming of the config option(s), they can of course be changed.

The order the trial bits gets set is somewhat odd, but is clearly what
happens, and somebody else trying to reverse engineer the ROM code has
observed the same thing: See the TracingVectors.ods in
https://github.com/sjgallagher2/am335xbootrom .

Rasmus

  reply	other threads:[~2026-01-22 13:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-22 13:17 [PATCH] am335x: add support for loading u-boot from multiple offsets Rasmus Villemoes
2026-01-22 13:49 ` Rasmus Villemoes [this message]
2026-01-22 16:21 ` Tom Rini

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=87ecnhrc3r.fsf@prevas.dk \
    --to=ravi@prevas.dk \
    --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 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.