How to properly run the TF-M integration samples on the LPC55S69?

[Mariposa-Marina]

Hi,

I am encountering challenges in executing the Trusted Firmware-M (TFM) on the LPC55S69. I have successfully compiled and flashed the blinky code with TFM onto the development board, in strict accordance with the instructions provided in the tutorial located at https://docs.zephyrproject.org/latest/boards/nxp/lpcxpresso55s69/doc/index.html. The compilation command used was:
west build -b lpcxpresso55s69/lpc55s69/cpu0/ns samples/basic/blinky -p

However, it appears that the board is not executing the code on the REE (Rich Execution Environment) side. Normally, the REE is expected to periodically blink an LED, but this behavior is not observed. Furthermore, there is no output being logged to the serial console. In comparison, other development boards, such as the nRF5340 DK and the STM32L562E-DK, are operating correctly. Could you please provide guidance on the steps required to resolve this issue and how to access the TEE (Trusted Execution Environment) logs?

If anybody could help me make better decisions it would be highly appreciated.

Regards

Mariposa Marina

[github-actions[bot]]

Hi @Mariposa-Marina! We appreciate you submitting your first issue for our open-source project. 🌟

Even though I'm a bot, I can assure you that the whole community is genuinely grateful for your time and effort. 🤖💙

[Mariposa-Marina]

It has been observed that when Zephyr is downgraded to version zephyr-3.4.0, the aforementioned issue does not occur, and the TEE initialization check can be successfully passed. Additionally, by appending the following content to the board.cmake file for the LPCXpresso55S69 board, the final tfm_merge.hex file is automatically generated and can be programmed onto the board using the west flash command.

## zephyr/boards/arm/lpcxpresso55s69/board.cmake
## ...
board_runner_args(pyocd "--target=lpc55s69")
## insert below code
if (CONFIG_BUILD_WITH_TFM)
  set_property(TARGET runners_yaml_props_target PROPERTY hex_file tfm_merged.hex)
endif()
## ...

Furthermore, since this version of Zephyr employs the J-Link programming method, it is necessary to utilize LPCScrypt to switch the LPCXpresso55S69 development board’s serial port to J-Link mode for the flashing process.

However, with this version, the STM32L562E-DK experiences the following issue during the programming process, which is not present in the latest version.

-- west flash: rebuilding
[0/19] Performing build step for 'tfm'
ninja: no work to do.
[2/3] Performing install step for 'tfm'
-- Install configuration: "MinSizeRel"
[3/3] Completed 'tfm'
-- west flash: using runner pyocd
-- runners.pyocd: Flashing file: /backup/ZEPHYR/tmp/nxp_zephyr/build/zephyr/tfm_merged.hex
0001111 C Target type stm32l562qeixq not recognized. Use 'pyocd list --targets' to see currently available target types. See https://pyocd.io/docs/target_support.html for how to install additional target support. [main]
FATAL ERROR: command exited with status 1: pyocd flash -e sector -a 0x8055000 -t stm32l562qeixq /backup/ZEPHYR/tmp/nxp_zephyr/build/zephyr/tfm_merged.hex

In the case of Zephyr versions 4.0.0 and 3.7.0, whereas other versions have not been tested, the LPCXpresso55S69 board exhibits the following error message when executing the tfm_secure_partition.

Booting TF-M v2.1.0
[WRN] This device was provisioned with dummy keys. This device is NOT SECURE
[Sec Thread] Secure image initializing!
[INF][PS] Encryption alg: 0x5500200
[INF][Crypto] Provision entropy seed...
Partition initialization FAILED in 0x10008795