On Mon, 19 Oct 2026 16:09:35 +0530, Beleswar Padhi wrote:
> Some TI K3 SoCs like J721S2, J784S4, and J722S have a HSM (High Security
> Module) M4F core in the Wakeup Voltage Domain which could be used to
> run secure services like Authentication. Boot flow for HSM M4 core is
> different than the general purpose M4F cores, and is as below:
>
> 1. Request control of HSM M4F remote processor.
> 2. Assert Reset on the HSM M4F remote processor.
> 3. Request Secure Entity to Authenticate and Load HSM firmware into
> core's internal SRAM memory region. For GP device, load the firmware
> manually into core's SRAM region.
> 4. Deassert Reset on the HSM M4F remote processor.
> 5. Release control of HSM M4F remote processor.
>
> [...]
Applied to u-boot/main, thanks!
[1/7] arm: mach-k3: Add config options for packaging HSM firmware
commit: 147321b92c741adb9e2f6a767daff5867b104fe3
[2/7] arm: dts: k3-{j721s2/j722s/j784s4}-binman: Add template for packing HSM
firmware
commit: 5ccd6c38cc1549fc3be28e197a1859520b65c384
[3/7] binman: openssl: Add boot and load extensions to x509 cert
commit: 8e4d2004d1e2701218946853f4949a62e0e427c5
[4/7] arm: dts: k3-{j721s2/j722s/j784s4}-r5.dtsi: Enable HSM core
commit: 427a0983e889aa2f6f9bfa751d9d0507efdae8fb
[5/7] remoteproc: k3-hsm: Introduce a remoteproc driver for K3 HSM core
commit: 6e67b32765e18d02b86e87c3c0f36d3b8ceef427
[6/7] arm: mach-k3: r5: common: Invoke boot of HSM M4 core
commit: 6bd72149941217edf467f44f3c86db9b3657ebf2
[7/7] doc: board: ti: k3: Add section for HSM M4F core loading
commit: bc63a70e4561f89d978e67b586ba09e29381ed48
--
Tom
