]> git.dujemihanovic.xyz Git - u-boot.git/commit
projects / u-boot.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 6c66ccf) | patch
binman: ti-secure: Add support for TI signing
authorNeha Malcom Francis <n-francis@ti.com>
Fri, 21 Jul 2023 18:44:25 +0000 (00:14 +0530)
committerTom Rini <trini@konsulko.com>
Fri, 21 Jul 2023 23:36:58 +0000 (19:36 -0400)
commit78144826bb8209df0a703a4a0dd88f7b57ad12cb
tree06ffa14eb4423215f11b4e59b2bd426379be98a8tree | snapshot
parent6c66ccf26ccca70bfcd94b43fbe6523f7564d214commit | diff
binman: ti-secure: Add support for TI signing

The ti-secure entry contains certificate for binaries that will be
loaded or booted by system firmware whereas the ti-secure-rom entry
contains certificate for binaries that will be booted by ROM. Support
for both these types of certificates is necessary for booting of K3
devices.

Reviewed-by: Simon Glass <sjg@chromium.org>
[vigneshr@ti.com: fixed inconsist cert generation by multiple packing]
Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
Signed-off-by: Neha Malcom Francis <n-francis@ti.com>
13 files changed:
board/ti/keys/custMpk.pem [new file with mode: 0644] blob
board/ti/keys/ti-degenerate-key.pem [new file with mode: 0644] blob
tools/binman/btool/openssl.py diff | blob | history
tools/binman/entries.rst diff | blob | history
tools/binman/etype/ti_secure.py [new file with mode: 0644] blob
tools/binman/etype/ti_secure_rom.py [new file with mode: 0644] blob
tools/binman/etype/x509_cert.py diff | blob | history
tools/binman/ftest.py diff | blob | history
tools/binman/test/279_ti_secure.dts [new file with mode: 0644] blob
tools/binman/test/280_ti_secure_rom.dts [new file with mode: 0644] blob
tools/binman/test/281_ti_secure_rom_combined.dts [new file with mode: 0644] blob
tools/binman/test/288_ti_secure_rom_a.dts [new file with mode: 0644] blob
tools/binman/test/289_ti_secure_rom_b.dts [new file with mode: 0644] blob
My U-Boot fork