Debugging problems with non-secure application

RE: Debugging problems with non-secure application

Priyanka — Thu, 22 Jan 2026 20:22:14 GMT

Hi Bert,

I am checking this with internal team and will keep you updated.

Could you specify the nRF Connect SDK version that you are working with?

-Priyanka

RE: Debugging problems with non-secure application

NordicBert — Wed, 21 Jan 2026 12:42:51 GMT

Hi Priyanka,

thanks for your answer. I tried it, but still no success. I am getting the same error.

Also I noticed that before CONFIG_TFM_CMAKE_BUILD_TYPE_DEBUG was set.

Best regards,

Bert

RE: Debugging problems with non-secure application

Priyanka — Tue, 20 Jan 2026 12:36:43 GMT

Hi Bert,

I guess what is happening is, usually for a normal build with no TF-M, everything runs in a single secure image, so the stepping will also work properly as expected. But in a non-secure build with TF-M, what happens is that the application runs in the non-secure environment, while the TF-M owns the secure processing environment. This misconfiguration is likely what is causing the issue.

So by default since you can only debug the non-secure firmware and the TF-M runs separately, in order to debug the TF-M you must build it with separate debug symbols as mentioned here: CONFIG_TFM_CMAKE_BUILD_TYPE_RELWITHDEBINFO

Please try this and let me know how it goes.

-Priyanka

RE: Debugging problems with non-secure application

NordicBert — Fri, 16 Jan 2026 08:40:09 GMT

Hi Priyanka,

I have CONFIG_DEBUG_OPTIMIZATIONS=y in my prj.conf.

Best regards,

Bert

RE: Debugging problems with non-secure application

Priyanka — Fri, 16 Jan 2026 08:25:06 GMT

Hi Bert,

Do you select the "Optimize for Debugging" option when building?

-Priyanka