2025-09-24 3:30 AM - edited 2025-09-24 3:34 AM
Hi Team,
Firmware file are just signed not encrypted through STM32 SigningTool - stm32mcu (STM32_SigningTool_CLI.exe) after generating public and private keys through STM32_KeyGen_CLI.exe.
Public key in raw 64 bytes is provided to bootloader_main.c as constant and hash is calculated from firmware data file after placing it at known location.
Able to verify magic number as after signing a firmware file a header of 256 bytes is placed at top but failing to verify ECDSA signature. Using API ECDSAverify from legacy_v3 cryptographic library to verify signature.
Please anyone help me with example as a reference to know where it is getting wrong.
2025-12-04 2:00 AM
Hello @Ajay_Bhatt ,
You have a full secure boot example available in X-CUBE-SBSFU package.
It is using the cryptolib V3.
Best regards
Jocelyn