From: Johan Jonker <jbx6244@gmail.com>
To: u-boot@0leil.net
Cc: kever.yang@rock-chips.com, sjg@chromium.org, trini@konsulko.com,
u-boot@lists.u-boot-project.org, eddie.cai.linux@gmail.com
Subject: [PATCH v4 2/9] rockchip: doc: add mask ROM mode text
Date: Mon, 3 Aug 2026 21:11:53 +0200 [thread overview]
Message-ID: <8e3babdf-dc50-44b2-a184-7d9f2a9938ff@gmail.com> (raw)
In-Reply-To: <d15555b5-e57b-4567-ab70-56d48fd4b878@gmail.com>
Add text that explains how to get into mask ROM mode.
Signed-off-by: Johan Jonker <jbx6244@gmail.com>
---
doc/board/rockchip/rockchip.rst | 26 ++++++++++++++++++++++++--
1 file changed, 24 insertions(+), 2 deletions(-)
diff --git a/doc/board/rockchip/rockchip.rst b/doc/board/rockchip/rockchip.rst
index de2df3046e28..d31b6d182c5e 100644
--- a/doc/board/rockchip/rockchip.rst
+++ b/doc/board/rockchip/rockchip.rst
@@ -325,6 +325,28 @@ To build rk3588 boards:
make evb-rk3588_defconfig
make CROSS_COMPILE=aarch64-linux-gnu-
+Mask ROM mode
+-------------
+
+The mode that the boot ROM falls back into that listens to
+0x471/0x472 USB commands.
+
+Options to get your board into Mask ROM mode:
+
+* Holding the recovery button, depending on firmware support or wiring,
+ when booting the board.
+* Remove any SD cards, removable eMMC or removable UFS modules.
+* Erase any storage media containing boot firmware.
+
+Methods of last resort (USE AT YOUR OWN RISK):
+
+Pins that should be connected/sorted for a
+short period when the board is connected to power, so that boot ROM
+cannot locate any boot firmware and falls back into Mask ROM mode.
+
+* NAND: connect pin 8 and 9 of the NAND flash with a needle.
+* eMMC: connect the clock line to ground.
+
Flashing
--------
@@ -485,9 +507,9 @@ To write a U-Boot image to the SD card (assumed to be /dev/sda):
NAND
""""
-Bring device in BootROM mode:
+Bring device in Mask ROM mode:
-If bricked and no BootROM mode shows up then connect pin 8 and 9 of the NAND flash
+If bricked and no Mask ROM mode shows up then connect pin 8 and 9 of the NAND flash
with a needle while reconnecting to the USB OTG port to a PC.
Show connected devices with:
--
2.39.5
next prev parent reply other threads:[~2026-08-03 19:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d15555b5-e57b-4567-ab70-56d48fd4b878@gmail.com>
2026-08-03 19:11 ` [PATCH v4 1/9] rockchip: scripts: remove rkmux.py Johan Jonker
2026-08-03 19:11 ` Johan Jonker [this message]
2026-08-05 21:25 ` [PATCH v4 2/9] rockchip: doc: add mask ROM mode text Simon Glass
2026-08-03 19:12 ` [PATCH v4 3/9] rockchip: doc: remove TODO Johan Jonker
2026-08-03 19:12 ` [PATCH v4 4/9] rockchip: doc: add more building instructions Johan Jonker
2026-08-03 19:12 ` [PATCH v4 5/9] rockchip: tools: rksd: remove reference to README.rockchip Johan Jonker
2026-08-05 21:25 ` Simon Glass
2026-08-03 19:12 ` [PATCH v4 6/9] rockchip: tools: rkspi: " Johan Jonker
2026-08-05 21:25 ` Simon Glass
2026-08-03 19:13 ` [PATCH v4 7/9] rockchip: tools: add comment section to rkimage.c Johan Jonker
2026-08-05 21:25 ` Simon Glass
2026-08-03 19:13 ` [PATCH v4 8/9] rockchip: doc: rockusb: remove reference to README.rockchip Johan Jonker
2026-08-05 21:25 ` Simon Glass
2026-08-03 19:13 ` [PATCH v4 9/9] rockchip: doc: remove README.rockchip Johan Jonker
2026-08-05 21:25 ` Simon Glass
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=8e3babdf-dc50-44b2-a184-7d9f2a9938ff@gmail.com \
--to=jbx6244@gmail.com \
--cc=eddie.cai.linux@gmail.com \
--cc=kever.yang@rock-chips.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@0leil.net \
--cc=u-boot@lists.u-boot-project.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