STM32MP135f - Secure Boot strange problems
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2024-06-10 6:38 AM - last edited on 2024-06-10 6:42 AM by Peter BENSCH
Hi!
According to the instructions on page https://wiki.st.com/stm32mpu/wiki/How_to_perform_Secure_Boot_from_Distribution_package#Creating_signature_key_for_STM32MP15x_lines
1.) Problem at 5.1
2.) Another problem with 7.2
STM32MP_SigningTool_CLI -pubk ~/yocto/secure-boot/publicKey00.pem -prvk ~/yocto/secure-boot/privateKey00.pem -pwd xxxxxxxxxxx -t fsbl -of 0x00000001 -bin ~/yocto/build/tmp-glibc/deploy/images/stm32mp13-ugea/arm-trusted-firmware/tf-a-stm32mp135f-ugea-microdev-mx-emmc.stm32 -o ~/yocto/build/tmp-glibc/deploy/images/stm32mp13-ugea/arm-trusted-firmware/tf-a-stm32mp135f-ugea-microdev-mx-emmc_Signed.stm32
Error below can be solver if removing -of 0x00000001 <---- Why??
-------------------------------------------------------------------
STM32MP Signing Tool v2.15.0
-------------------------------------------------------------------
Binary already contains header
STM32MP_SigningTool_CLI -pubk ~/yocto/secure-boot/publicKey00.pem -prvk ~/yocto/secure-boot/privateKey00.pem -pwd xxxxxxxxxxx --enc-key ~/yocto/secure-boot/stm32mp13_encryption_key.bin -t fsbl --enc-dc 0x0E5F2025 --image-version 0 -of 0x80000003 -bin ~/yocto/build/tmp-glibc/deploy/images/stm32mp13-ugea/arm-trusted-firmware/tf-a-stm32mp135f-ugea-microdev-mx-emmc.stm32 -o ~/yocto/build/tmp-glibc/deploy/images/stm32mp13-ugea/arm-trusted-firmware/tf-a-stm32mp135f-ugea-microdev-mx-emmc_Encrypted.stm32
Error below can be solved if removing -of 0x80000003 <---- Why??
-------------------------------------------------------------------
STM32MP Signing Tool v2.15.0
-------------------------------------------------------------------
Binary already contains header
Current local.conf from Yocto:
System info:
