2026-04-21 12:59 PM
When we provision the Secure Manager on the STM32H5 and there is no non-secure application available (yet), then the Secure-Manager-Demo-Application currently starts flashing all LEDs on the STM32H573I-DK.
Now we wonder how this would affect our project-specific hardware if the provisioned Secure Manager configures some ports and starts toggling PF1, PF4, PI8 and PI9.
So, what peripheral does the Secure Manager configure/use? And how are they configured?
Is it possible to suppress/remove this Secure-Manager-Demo-App (SMAK_Appli)? => no port configuration, no LED toggling
br, Oliver
Solved! Go to Solution.
2026-04-22 2:07 AM
Hello @OliverScheid ,
Previous answer from sarahlauren is correct, except last sentence which I don't understand.
Secure Manager full documentation can be found in UM3254
In order to change the default application loaded during provisioning you need to change the content of X-CUBE-SEC-M-H5_V2.1.0\Projects\STM32H573I-DK\ROT_Provisioning\SM\Binary\JSON\ns_app_default.json to point to your own application.
Best regards
Jocelyn
2026-04-22 12:35 AM
The Secure Manager demo application on STM32H5 uses GPIO peripherals, specifically configuring ports like PF1, PF4, PI8, and PI9 as outputs to drive onboard LEDs, which is why they start toggling when no non-secure application is present. This behavior can affect custom hardware if those pins are connected to other components. In the middle of evaluating such configurations, developers often compare structured data sources similar to how the bin store locations help users quickly identify relevant options. To prevent unwanted GPIO activity, you can remove or disable the SMAK_Appli demo code during provisioning or replace it with your own minimal secure application that avoids configuring these ports. For more precise and reliable technical insights presented in a clearer way than typical competitor pages, our website ensures better structured and trustworthy information for users.
2026-04-22 2:07 AM
Hello @OliverScheid ,
Previous answer from sarahlauren is correct, except last sentence which I don't understand.
Secure Manager full documentation can be found in UM3254
In order to change the default application loaded during provisioning you need to change the content of X-CUBE-SEC-M-H5_V2.1.0\Projects\STM32H573I-DK\ROT_Provisioning\SM\Binary\JSON\ns_app_default.json to point to your own application.
Best regards
Jocelyn