From: Sascha Hauer <s.hauer@pengutronix.de>
To: Barebox List <barebox@lists.infradead.org>
Subject: [PATCH] Documentation: boards: k3: adjust to reality
Date: Thu, 5 Jun 2025 12:11:58 +0200 [thread overview]
Message-ID: <20250605101158.461655-1-s.hauer@pengutronix.de> (raw)
Using separate files for firmware binaries was removed in commit
1bc97b7995 ("ARM: k3: r5: drop loading of separate binaries"). Adjust
the documentation accordingly.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
---
Documentation/boards/ti-k3.rst | 28 +++++-----------------------
1 file changed, 5 insertions(+), 23 deletions(-)
diff --git a/Documentation/boards/ti-k3.rst b/Documentation/boards/ti-k3.rst
index 18061a9836..6cb9eb8eda 100644
--- a/Documentation/boards/ti-k3.rst
+++ b/Documentation/boards/ti-k3.rst
@@ -72,25 +72,16 @@ OP-TEE is built from https://github.com/OP-TEE/optee_os.git::
OP-TEE is optional. barebox will continue without ``optee.bin`` when the file
does not exist.
-Copying ti-dm.bin
------------------
-
-The ``ti-dm.bin`` binary is part of ti-linux-firmware.git, this needs to be
-copied to the eMMC/SD as well::
-
- cp firmware/ti-linux-firmware/ti-dm/am62xx/ipc_echo_testb_mcu1_0_release_strip.xer5f $TI_BOOT/ti-dm.bin
-
Combining binaries into a FIP image
-----------------------------------
-Alternatively to putting the different binaries (``barebox.bin``, ``bl31.bin``, ``optee.bin``
-and ``ti-dm.bin``) into the FAT image the files can be combined into a FIP image named
-``k3.fip``.::
+The files have to be combined into a FIP image named ``k3.fip``.::
fiptool create --soc-fw bl31.bin \
--tos-fw optee.bin \
--nt-fw barebox-beagleplay.img \
- --blob uuid=9e8c2017-8b94-4e2b-a7b3-a0f88eabb8ae,file=ti-dm.bin k3.fip
+ --blob uuid=9e8c2017-8b94-4e2b-a7b3-a0f88eabb8ae,file=\
+ firmware/ti-linux-firmware/ti-dm/am62xx/ipc_echo_testb_mcu1_0_release_strip.xer5f k3.fip
USB DFU boot
------------
@@ -99,20 +90,11 @@ using ``dfu-util``::
dfu-util -D barebox-beagleplay-r5.img -a bootloader
-This will start the initial stage which then expects the following stages which can
-be uploaded with ``dfu-util`` as well, either as FIP image::
+This will start the initial stage which then expects the following stage which can
+be uploaded with ``dfu-util`` as well::
dfu-util -D k3.fip -a fip
-or as separate files::
-
- dfu-util -D blb31.bin -a tfa
- dfu-util -D optee.bin -a optee
- dfu-util -D ti-dm.bin -a ti-dm
- dfu-util -D barebox-beagleplay.img -a barebox
-
-Uploading optee.bin can be skipped in case it's not needed.
-
eMMC boot
---------
K3 boards can boot from eMMC boot partitions. In this mode the ROM reads the tiboot3.bin
--
2.39.5
next reply other threads:[~2025-06-05 10:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-05 10:11 Sascha Hauer [this message]
2025-06-05 11:54 ` 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=20250605101158.461655-1-s.hauer@pengutronix.de \
--to=s.hauer@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