stm32: nucleo-wba65ri 'ns' variant fails to boot #107675

Describe the bug

The 'ns' variant of nucleo_wba65ri board fails to boot since commit 5503261 due to TF-M firmware not allowing non-secure application to read SoC OTPs.

When target boots, is loops on booting TF-M, due to a system error during Zephyr late init hook that triggers a reset.

The root cause needs to be addressed from TF-M, for example configuring SAU to allow non-secure to read from the SoC OTPs address range.

Regression

• This is a regression.

Steps to reproduce

west build -b nucleo_wba65ri//ns samples/hello_world
./build/tfm/api_ns/regression.sh
west flash

Relevant log output

Booting TF-M v2.2.2+7e8bf2314
[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] Init HW accelerator...
[INF][Crypto] Init HW accelerator... complete.
Booting TF-M v2.2.2+7e8bf2314
[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] Init HW accelerator...
[INF][Crypto] Init HW accelerator... complete.
(...)

Impact

Annoyance – Minor irritation; no significant impact on usability or functionality.

Environment

No response

Additional Context

No response