Skip to main content
Associate II
February 27, 2025
Solved

TrustZone TFM Example Problems

  • February 27, 2025
  • 2 replies
  • 742 views

We have a project where we're using a U5A5 MCU with trustzone enabled and we're currently trying to figure out how to flash without having to use the SAM card. I downloaded the example from ST and am trying to run through the  B-U585I-IOT02A TFM example application on my NUCLEO-U5A5ZJ-Q development board. Running unmodified, I am able to build all three projects (appli, loader, boot) and the regression.sh run without errors, the TFM_Update.sh script runs without errors, but when I connect to the terminal, I get the following repeating pattern.

 

JamesB_0-1740680927984.png

I've already tried pressing the reset button as well as removing and putting back the IDD jumper. Any help would be appreciated!

Best answer by Jocelyn RICARD

Hello @JamesB ,

I would suggest disabling TAMPER feature in the configuration file (boot_hal_cfg.h).

#define TFM_TAMPER_ENABLE NO_TAMPER

or

#define TFM_TAMPER_ENABLE INTERNAL_TAMPER_ONLY

Best regards

Jocelyn

2 replies

Jocelyn RICARD
Jocelyn RICARDBest answer
ST Employee
February 28, 2025

Hello @JamesB ,

I would suggest disabling TAMPER feature in the configuration file (boot_hal_cfg.h).

#define TFM_TAMPER_ENABLE NO_TAMPER

or

#define TFM_TAMPER_ENABLE INTERNAL_TAMPER_ONLY

Best regards

Jocelyn

JamesBAuthor
Associate II
February 28, 2025

With that change I now get this. It repeats continually over and over (boot loop?)

 

JamesB_0-1740765024384.png

 

JamesBAuthor
Associate II
February 28, 2025

When I pressed the "User" button on the development board, it stopped looping and continued as expected, although does not seem to start at the main entry point but rather a sub-menu.

JamesB_0-1740766909067.png

 

Jocelyn RICARD
ST Employee
March 3, 2025

Hello @JamesB,

when pressing blue button upon reset, you go into the standalone loader.

What happens here is that when launching TFM or non secure application, a reset occurs.

It is probably related to deference of memory sized between original chip and target chip.

A porting has to be done to adapt the GTZC configurations.

Best regards

Jocelyn