From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15973] New: imx8m bootloader image generation broken since update to imx-mkimage 6.1.36_2.1.0
Date: Wed, 06 Mar 2024 15:47:17 +0000 [thread overview]
Message-ID: <bug-15973-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=15973
Bug ID: 15973
Summary: imx8m bootloader image generation broken since update
to imx-mkimage 6.1.36_2.1.0
Product: buildroot
Version: 2024.02
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: buildroot@martin-whitaker.me.uk
CC: buildroot@uclibc.org
Target Milestone: ---
imx-mkimage 6.1.36_2.1.0 includes this commit
https://github.com/nxp-imx/imx-mkimage/commit/5a0faefc223e51e088433663b6e7d6fbce89bf59
which inserts an additional data structure in the generated image. The external
data position passed to (the uboot) mkimage in
board/freescale/common/imx/imx8-bootloader-prepare.sh needs to be adjusted
accordingly, so '-p 0x5000' instead of '-p 0x3000'. You can see that same
adjustment being made in the soc.mak file in the commit reference.
I have only tested this on an i.MX8M Nano DDR4 EVK board, but expect it applies
to all i.MX8M boards that use imx-mkimage to generate their bootloader image.
This bug first appeared in the 2023.11 release.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2024-03-06 15:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 15:47 bugzilla [this message]
2024-03-27 17:44 ` [Buildroot] [Bug 15973] imx8m bootloader image generation broken since update to imx-mkimage 6.1.36_2.1.0 bugzilla
2024-03-27 21:08 ` bugzilla
2024-03-28 10:44 ` bugzilla
2024-04-23 17:07 ` bugzilla
2024-06-04 13:55 ` bugzilla
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=bug-15973-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.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