Hi,
for one of our products we are evaluating an option of porting the application from nRF5 SDK (nRF52) to nRF Connect SDK (nRF54). Seeing the similarity between the nRF Connect SDK Bare-metal and nRF5 SDK, bare-metal SDK seems to be a good candidate to achieve faster time to market. However, with the switch to nRF54 we are also looking into possibility of obtaining a safety certification for the product, for which the Zephyr option possibly seems to be a better candidate due to built-in TF-M support.
My question is, are there any plans to introduce TF-M support or any other solution to achieve separation between secure and non-secure processing environments in bare-metal SDK? If it's out of scope for the bare-metal SDK, is it even a plausible undertaking to add TF-M to bare-metal taking into account the presence of softdevice?
Kind regards,
Robert
