Unable to run apps; debug stops at "SPM: prepare to jump into Non-Secure image".

RE: Unable to run apps; debug stops at "SPM: prepare to jump into Non-Secure image".

SCombellack — Fri, 14 Jun 2019 12:39:41 GMT

Aha! I have a working application! So I can't use Segger for deploying onto my board until it's updated?

RE: Unable to run apps; debug stops at "SPM: prepare to jump into Non-Secure image".

Håkon Alseth — Fri, 14 Jun 2019 11:23:54 GMT

This could be due to the "merged.hex" - where the spm (previously named secure_boot) assumes that the application resides from 0x8000 and upwards. Or the other way around in this scenario; your spm assumes that the application is on 0x40000, while the application is flashed from 0x8000.

The current SES for NCS v4.16 does not handle these merged projects very well, but will do this when v4.17 comes out.

If you go into your build folder in cmd.exe, and write "ninja flash", do you then get a merged.hex file that will be flashed onto your device?

Kind regards,

Håkon

RE: Unable to run apps; debug stops at "SPM: prepare to jump into Non-Secure image".

SCombellack — Fri, 14 Jun 2019 08:11:31 GMT

Hi, This is a new application. I have tried the GPS, simple_mqtt and another app I can't think of. They compile and go onto the board, but I see no serial. I haven't changed the proj.conf files apart from to add "CONFIG_SERIAL=y" when I saw nothing from the board.

I'm really confused! And it's stopping me doing any work with the board now..

RE: Unable to run apps; debug stops at "SPM: prepare to jump into Non-Secure image".

Håkon Alseth — Fri, 14 Jun 2019 06:56:28 GMT

Hi,

[quote user=""]I did have a working development board. I was working to disable serial and disable as much as possible to get the power usage down. It seemed to be working (although I did not have debug but I could watch the board usage in my Otii). Now I have performed an update of the development tools after the release of the latest firmware in May. I can build the new sample applications and SPM, they seem to work but I still have no debug output. I'm sure I have 'undone' everything I did to disable the serial debug, but my applications don't output debug text.[/quote]

Are you sure you didn't succeed in disabling serial in your application? Have you tried debugging to see where, or if, you're stuck in firmware? How does your prj.conf look like?

What happens if you run any other sample, like simple_mqtt / at_client or similar?

Kind regards,

Håkon