cancel
Showing results for 
Search instead for 
Did you mean: 

Assigning pins to the secure context of TFM application

SedCore
Associate III

Hello,

Unless I'm wrong, the architecture of the TFM application as described in UM2851 seems not to allow the assignment of a peripheral (e.g. a LED pin) to the Secure context of TrustZone as it is the case with simple TrustZone applications. 

The UM2851 states that the user can "Replace the nonsecure TFM application example delivered in the STM32CubeU5 MCU Package by its own product nonsecure application", without raising this possibility for the secure application too.

Moreover, I couldn't find on the Internet such example of customization of the Secure context of the TFM application to assign peripherals to the Secure part of the application.

Is there a way to do so? If yes, how?

Thanks a lot.

@STea @Jocelyn RICARD @Benjamin BARATTE 

1 ACCEPTED SOLUTION

Accepted Solutions
STea
ST Employee

Hello @SedCore ,

The previous reply was deleted because it was detected as AI generated spam.

know regarding your request, there is no restriction in changing the TFM Appli secure project in which you could assign change I/O attributions to the secure or non-secure world (check the target_cfg.c in secure Appli project).
I think by default it is configured for the non-secure world for SRAM3, so you need to modify the SAU and GTZC to be assigned to secure.
Regards

In order to give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

View solution in original post

2 REPLIES 2
SedCore
Associate III

@gpguy :thinking_face: it seems you had some ideas? Why your reply has been deleted?

STea
ST Employee

Hello @SedCore ,

The previous reply was deleted because it was detected as AI generated spam.

know regarding your request, there is no restriction in changing the TFM Appli secure project in which you could assign change I/O attributions to the secure or non-secure world (check the target_cfg.c in secure Appli project).
I think by default it is configured for the non-secure world for SRAM3, so you need to modify the SAU and GTZC to be assigned to secure.
Regards

In order to give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.