Part Number: AM6442
Hello TI Team,
We are using an AM6442 HS-FS custom board with Processor SDK Linux 9.x (RT-Linux).
We understand that SDK 9.x uses the Binman-based signing flow, and the older k3-image-gen and core-secdev-k3 signing flow is no longer used.
We would like guidance on the following:
1. What is the recommended procedure to generate customer signing keys (custMpk.pem) for SDK 9.x?
2. After generating our customer keys, where should they be integrated within the SDK/U-Boot source tree?
3. When replacing the default custMpk.pem, are tiboot3.bin, tispl.bin, and u-boot.img automatically signed during the U-Boot build process, or are additional signing steps required?
4. For an HS-FS device, can the generated customer-signed images be boot-tested directly before moving to an HS-SE device?
5. Since we are using a custom AM6442 board, are there any specific hardware requirements, eFuse/OTP settings, boot mode settings, or board-level considerations required for secure boot validation?
6. The complete customer-key signing flow for:
* tiboot3.bin
* tispl.bin
* u-boot.img
Our goal is to validate the complete secure boot flow on an AM6442 HS-FS custom board using customer-generated keys before moving toward HS-SE production deployment.
Thank you.
Ganesh D
