Bluetooth mesh Provisioning with NRF54L15 and SDK 3.01

[Doug K]

I have a couple questions regarding the Bluetooth Mesh provisioner role and TF-M builds.

I am using an NRF54L15 and currently swapped to v3.01. Previously on versions <3.0 I was able to build my app that provisions BLE Mesh devices using the cpuapp version of the board. Now I it only compiles using the Non-secure TF-M version. 

Using the TF-M version is fine, only problem I have is that I was looking at the board file and UART30 is disabled when using the non-secure version. I am using UART30 for my custom board. 

So my questions are:

1) Why does the Bluetooth Mesh Provisioning Sample require the Non-Secure build? Can it work with the "cpuapp" build with some config options added?

2) If I need to use the Non-Secure version, is disabling UART30 required?

You can duplicate my problem using the "mesh_provisioner" sample with the NRF54L15DK with SDK v3.01. 

Thanks,

[Doug K]

I am having some issues posting the console output here. I'll see if I can get a shortened version posted:

ncs/toolchains/0b393f9e1b/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: zephyr/libzephyr.a(trusted_backend_aead.c.obj): in function `trusted_get_info':

ncs/v3.0.1/nrf/subsys/trusted_storage/src/aead/trusted_backend_aead.c:62: undefined reference to `storage_get_object'

ncs/v3.0.1/nrf/subsys/trusted_storage/src/aead/trusted_backend_aead.c:102: undefined reference to `storage_get_object'

ncs/toolchains/0b393f9e1b/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: zephyr/libzephyr.a(trusted_backend_aead.c.obj): in function `trusted_set':