2025-01-13 08:47 AM
Hi,
I'm currently exploring the solutions to develop a bootloader on a STM32U535. I'm looking into the MCUBoot based examples provided by ST : SBSFU projects.
After some investigations, I noticed that the SBSFU_Boot memory footprint was ~80ko and the SBSFU_Loader one was 24ko. For MCUs with limited flash size like STM32U535xB, this leaves almost no space for the application.
Is there a way to reduce MCUboot size ? For instance, by disabling non essential modules ?
Or maybe am I doing something wrong and memory footprint should be lower ?
Pierre
2025-01-13 09:51 AM
Hi,
the STM32U535 has built in bootloader , also on USB .
So 128K for your program, see AN2606 ...
or why you want make the bootloader yourself ?
2025-01-14 02:05 AM
The built in bootloader is too simple, I need the security features of SBSFU : image encryption / decryption, reset recovery, downgrade prevention.
My question was poorly asked, I'm not trying to develop a bootloader from scratch. I'll use MCUBoot because I need these security features and I'm trying to understand its flexibility.
And I was wondering if, for limited size MCUs, there were ways to optimize MCUBoot memory footprint, in order to leave more space for the application.
2025-01-14 02:25 AM
Ah, ok...so its a problem about money, because the 512KB version is about 40 ct more expensive.
Thats dramatic then...
2025-01-14 03:30 AM
What an inappropriate answer.
Thanks buddy, very helpful !