STM32H5 - X-CUBE-SEC-M-H5_V2.0.0 - CubeMX

[andyi]

Hi Everybody,

I posted a comment here https://community.st.com/t5/stm32-online-courses/stm32h5-secure-manager-course/bc-p/824487/highlight/true#M27 yesterday because I am trying following the online course and what is written in the wiki to start developing an application on the STM32H573VI using the secure manager.

At the moment I am starting the development by using the nucleo board for H573 however, by following the wiki, the only project that could be used for deploying the solution is an handswritten example that does not use the CubeMx.

If I try to follow the old documentation on the youtube videos, as explained in the link provided, I am unable to set the boot path correctly.

At the moment I am a bit lost, should I build my project without the use of CubeMx in case of secure manager? Will it be added in the future? I am missing something straightforward?

thank you in advance

Andrea

[Frantz LEFRERE]

Hello Andre,

STiROT can only be activated if TrustZone is activated.
So you need to generate a application "full secure" or Secure/non secure application.
Other solution OEMiROT code example is with TrustZone, so you also a need a secure application at least.
Best regards,

Frantz 

[andyi]

Dear Frantz,

Thank you for your reply. But sadly, my doubts still remains.

In X-CUBE-SEC-M-H5_V2.0.0 there are 2 projects that could be used as examples:

• STM32H573I-DK/Templates/ROT/SMAK_Appli
• STM32H573I-DK/Applications/ROT/SMAK_Appli

The first one is a simple application that toggles the LEDS of the DK, the second uses the UART for checking different functionalities of the Secure Manager.

However, those two application do not use the CubeMx as a base. Clocks, peripherals etc could not be updated by using the CubeMx but only by hand.

I would like to understand which steps I should follow on CubeMx in order to have an application that could be run over the Secure Manager.

I followed those wiki pages:

• https://wiki.st.com/stm32mcu/wiki/Security:How_to_start_with_Secure_Manager_default_configuration_on_STM32H5
• https://wiki.st.com/stm32mcu/wiki/Security:How_to_start_with_Secure_Manager_customized_config_on_STM32H5

Both of those does not take into consideration the CubeMx. CubeMx solution was provided for version 1 of Secure Manager as visible on the Youtube videos that was published for version 1.1. https://www.youtube.com/watch?v=BLSlME3iq3A video at minute 2:50 shows that the project is automatically generated.

thank you in advance

Andrea

[Frantz LEFRERE]

Hello Andrea,

Sorry I have not realize your question was in the context of secure manager, the boot path generation has been remove from CubeMX for the secure manager.
This is for complexity and maintenance reason.
So boot path is still working for OEMiROT or STiROT but not for secure manager.
The best way is to use the application example and to port your code in it.
Some wiki page are under construction about this topic
I hope this clarifies.

Br,

Frantz

[andyi]

Dear Frantz,

thank you for the reply.

I partially understand your response. I am trying to follow the wiki for guidance on it but it seems to me that some steps are not clear. A bit of guidance on this subject would be really appreciated.

Will it be possible to implement anything about it?

Thank you

Andrea