From: Sascha Hauer <s.hauer@pengutronix.de>
To: BAREBOX <barebox@lists.infradead.org>
Subject: [PATCH 2/3] ARM: k3: am62x: make more space for r5 barebox binary
Date: Mon, 18 May 2026 11:26:39 +0200 [thread overview]
Message-ID: <20260518-k3-am62x-image-size-fixes-v1-2-ab723d79922d@pengutronix.de> (raw)
In-Reply-To: <20260518-k3-am62x-image-size-fixes-v1-0-ab723d79922d@pengutronix.de>
On the AM62x we have 0x3e000 bytes available for the initial r5 barebox
binary and the dmdata. The dmdata is currently hardcoded at offset
0x3a800 in the SRAM leaving only the space below that for the barebox
binary. The dmdata only has a size of 1362 bytes. Let's be generous and
give it 4096 bytes of maximum space, so move it up to 0x3d000 leaving
mode space for the barebox binary.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
---
images/Makefile.k3 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/images/Makefile.k3 b/images/Makefile.k3
index 789f77722a..12538541b0 100644
--- a/images/Makefile.k3
+++ b/images/Makefile.k3
@@ -92,7 +92,7 @@ quiet_cmd_k3_am62x_image = K3_am62x_IMG $@
$(SYSFW_$(@F)):2:0:0:00040000 \
$(SYSFWDATA_am625):18:0:0:00067000 \
$$inner \
- $(DMDATA_am625):17:16:0:43c3a800 \
+ $(DMDATA_am625):17:16:0:43c3d000 \
--key "$(KEY_$(@F))" --out $@
ifdef CONFIG_FIRMWARE_K3_AM62L_OPTEE
--
2.47.3
next prev parent reply other threads:[~2026-05-18 9:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 9:26 [PATCH 0/3] k3: am62x: image size fixes Sascha Hauer
2026-05-18 9:26 ` [PATCH 1/3] ARM: k3: am62x: move stack to end of SRAM Sascha Hauer
2026-05-18 9:26 ` Sascha Hauer [this message]
2026-05-18 9:41 ` [PATCH 2/3] ARM: k3: am62x: make more space for r5 barebox binary Ahmad Fatoum
2026-05-18 9:26 ` [PATCH 3/3] ARM: k3: k3-r5_defconfig: limit image size to maximum available space Sascha Hauer
2026-05-18 9:37 ` Ahmad Fatoum
2026-05-18 10:38 ` Sascha Hauer
2026-05-18 13:33 ` [PATCH 0/3] k3: am62x: image size fixes 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=20260518-k3-am62x-image-size-fixes-v1-2-ab723d79922d@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