From: Leo Denieul <leo.denieul.yoshino@gmail.com>
To: buildroot@buildroot.org
Cc: Dick Olsson <hi@senzilla.io>, Sergey Matyukevich <geomatsi@gmail.com>
Subject: [Buildroot] [PATCH 0/2] NXP Layerscape secure boot support for TF-A
Date: Thu, 12 Nov 2026 10:38:54 +0100 [thread overview]
Message-ID: <cover.1794475724.git.leo.denieul.yoshino@gmail.com> (raw)
Subject: [PATCH 0/2] NXP Layerscape secure boot support for TF-A
This series adds the support to build signed boot images for NXP
Layerscape SoCs with the NXP Code Signing Tool, and enables it for the
LX2160ARDB (lx2160a-rdb_defconfig).
Tested on a LX2160ARDB with SRKH fused (ITS not blown): with the right
keys the BootROM authenticates the PBI and BL2 (SNVS Secure, no error
in SCRATCHRW3), with wrong SRK keys, BL31/BL33 certificates are
rejected by BL2.
This series depends on:
- configs/lx2160a-rdb: new defconfig (v8)
- package/qoriq-cst: new package (v6)
A TF-A bump with SRK key generation at build time will follow
Leo Denieul (2):
boot/arm-trusted-firmware: add NXP Layerscape secure boot support
board/freescale/lx2160a-rdb: add secure boot support
.../arm-trusted-firmware.hash | 2 +
board/freescale/lx2160a-rdb/post-build.sh | 6 ++
board/freescale/lx2160a-rdb/readme.txt | 34 +++++++++
boot/arm-trusted-firmware/Config.in | 75 +++++++++++++++++++
.../arm-trusted-firmware.mk | 63 ++++++++++++++++
5 files changed, 180 insertions(+)
--
2.53.0
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2026-11-12 9:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 9:38 Leo Denieul [this message]
2026-11-12 9:39 ` [Buildroot] [PATCH 1/2] boot/arm-trusted-firmware: add NXP Layerscape secure boot support Leo Denieul
2026-11-12 9:39 ` [Buildroot] [PATCH 2/2] board/freescale/lx2160a-rdb: add " Leo Denieul
2026-11-12 10:22 ` [Buildroot] [PATCH 0/2] NXP Layerscape secure boot support for TF-A Leo Denieul
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=cover.1794475724.git.leo.denieul.yoshino@gmail.com \
--to=leo.denieul.yoshino@gmail.com \
--cc=buildroot@buildroot.org \
--cc=geomatsi@gmail.com \
--cc=hi@senzilla.io \
/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