From: Lukas Schmid <lukas.schmid@netcube.li>
To: Parthiban <parthiban@linumiz.com>
Cc: parthiban@linumiz.com, linux-sunxi@lists.linux.dev
Subject: Re: T113-S3: Secure Boot
Date: Sat, 08 Nov 2025 17:56:40 +0100 [thread overview]
Message-ID: <2286928.tdWV9SEqCh@lukas-hpz440workstation> (raw)
In-Reply-To: <5290a949-1eed-47e9-a258-024447009c7b@linumiz.com>
[-- Attachment #1: Type: text/plain, Size: 986 bytes --]
On Freitag, 7. November 2025 18:13:13 Mitteleuropäische Normalzeit Parthiban
wrote:
> Hi Lukas,
Hi Parthiban
>
> On 8/1/25 10:33 PM, Lukas Schmid wrote:
> > 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.
>
> Could you please share how this is done or may be with a document patch to
> u-boot? To add, am also in the initial analysis of adding secure boot for
> A133.
I actually do have a document on how I fused and flashed my prototype board
here: https://nagami.readthedocs.io/en/latest/software/enable-secureboot-on-soc/
The required changes to U-Boot are already in a Patch, but I haven't heard
anything back yet.
>
> Thanks,
> Parthiban
Best regards,
Lukas
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-11-08 17:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-01 20:33 T113-S3: Secure Boot Lukas Schmid
2025-08-02 0:09 ` Andre Przywara
2025-08-02 8:37 ` Lukas Schmid
2025-11-07 17:13 ` Parthiban
2025-11-08 16:56 ` Lukas Schmid [this message]
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=2286928.tdWV9SEqCh@lukas-hpz440workstation \
--to=lukas.schmid@netcube.li \
--cc=linux-sunxi@lists.linux.dev \
--cc=parthiban@linumiz.com \
/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