From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH 1/2] Documentation: troubleshooting: mention bootrom command
Date: Thu, 24 Sep 2026 16:53:28 +0200 [thread overview]
Message-ID: <20260924145332.2712276-1-a.fatoum@pengutronix.de> (raw)
The bootrom command is easily overlooked, but it's useful when debugging
BootROM refusing to boot on i.MX8M, so mention it.
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
Documentation/devel/troubleshooting.rst | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/Documentation/devel/troubleshooting.rst b/Documentation/devel/troubleshooting.rst
index f96b4d2b15ff..796f5eef4f13 100644
--- a/Documentation/devel/troubleshooting.rst
+++ b/Documentation/devel/troubleshooting.rst
@@ -142,6 +142,17 @@ System-on-Chip.
functions that can be used to toggle a GPIO. These can be used for
debugging early hangs by toggling an LED for example.
+- Inspect via fallback boot method
+
+ On some systems, a failure to boot from one boot medium causes the
+ BootROM to try a fallback. If the fallback can actually boot barebox,
+ you may be able to get more information once the shell is reached.
+ For example, if the BootROM refuses eMMC boot, is eMMC at least usable
+ from within barebox?
+ barebox can also decode BootROM logs on some SoCs via
+ :ref:`command_bootrom`, which can answer questions as whether the
+ BootROM even attempted access to the desired boot medium.
+
- Trace BootROM activity
If you have no indication that the barebox prebootloader is being started,
--
2.47.3
next reply other threads:[~2026-09-24 14:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 14:53 Ahmad Fatoum [this message]
2026-09-24 14:53 ` [PATCH 2/2] Documentation: troubleshooting: add debugging via built-in init scripts Ahmad Fatoum
2026-09-24 15:06 ` [PATCH] fixup! " Ahmad Fatoum
2026-09-25 9:07 ` (subset) " Sascha Hauer
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=20260924145332.2712276-1-a.fatoum@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
/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