From: Lukas Schmid <lukas.schmid@netcube.li>
To: linux-sunxi@lists.linux.dev
Subject: T113-S3: Secure Boot
Date: Fri, 01 Aug 2025 22:33:19 +0200 [thread overview]
Message-ID: <4693897.cEBGB3zze1@lukas-hpz440workstation> (raw)
[-- Attachment #1: Type: text/plain, Size: 1124 bytes --]
Hi all,
I’m working on enabling secure boot on the Allwinner T113-S3 (as part of
preparing my SoM design for EU CRA compliance).
I’ve successfully fused the SoC with secure boot enabled and burned the
ROTPK_HASH. The SoC correctly boots a TOC0-signed image from SD card, and U-
Boot starts up and behaves as expected.
However, when I try to load and boot the kernel from U-Boot, the board hangs
right after U-Boot hands over control, no further progress. The same kernel
image worked fine before enabling secure boot, so I suspect it might be related
to the secure boot configuration or runtime expectations.
I’ve already tried debugging U-Boot and confirmed that the kernel is loaded and
`bootm` is called; the system hangs at that point.
Here are the versions I’m using:
- **Kernel:** Linux 6.15.4 (mainline)
- **U-Boot:** 2025.07-rc5 (with custom devicetree and I2C3 modifications)
Is there anything specific I might be missing when running the kernel under
secure boot on the T113-S3? Any guidance, common pitfalls, or pointers would
be appreciated.
Best regards,
Lukas
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2025-08-01 20:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-01 20:33 Lukas Schmid [this message]
2025-08-02 0:09 ` T113-S3: Secure Boot Andre Przywara
2025-08-02 8:37 ` Lukas Schmid
2025-11-07 17:13 ` Parthiban
2025-11-08 16:56 ` Lukas Schmid
2025-11-08 17:01 ` Parthiban
2025-11-08 17:55 ` Lukas Schmid
2026-01-08 4:34 ` Parthiban
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=4693897.cEBGB3zze1@lukas-hpz440workstation \
--to=lukas.schmid@netcube.li \
--cc=linux-sunxi@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).