application on nrf9160 board does not start

RE: application on nrf9160 board does not start

Håkon Alseth — Fri, 19 Aug 2022 07:24:41 GMT

Hi,

It is great to hear that you solved your problem. I hope you have a wonderful weekend!

Kind regards,

Håkon

RE: application on nrf9160 board does not start

stefanino — Fri, 19 Aug 2022 06:10:34 GMT

Hi Hakon,

I have to correct my last message. The proper configuration of MCUboot alone solved my problem.

RE: application on nrf9160 board does not start

stefanino — Thu, 18 Aug 2022 13:58:08 GMT

Hi Hakon,

thanks for the speedy reply.

In the meantime I managed to figure out that my board configures and uses pin 0.26 differently from the thingy.

Coincidentally that is used by default by MCUboot to detect UART bootloading, so setting CONFIG_MCUBOOT_SERIAL=n in the MCUboot configuration to disable that function get me a step further.

Now the blinky application can start correctly in stand-alone, ONLY if build for Secure. If I build for Non Secure still the app won't start.

My final app uses the modem library that requires Non Secure.

So how can I tell the mcuboot to boot the non secure partition?

thanks again

RE: application on nrf9160 board does not start

Håkon Alseth — Thu, 18 Aug 2022 13:33:02 GMT

Hi,

[quote user=""]

I'm developing a board based on the thingy91 (same nordic silicon, different sensors) and using nrf SDK v2.0.0

The blinky application is flashed and run correctly the first time upon flash complete, but won't start if I turn off and on the board again.

Has anyone seen similar behavior?

[/quote]

This is often due to sensors/libraries being enabled in the background, where there's a timing issue upon boot. Ie. a sensor being initialized before it's ready, maybe it needs a 100 ms delay before initial transmission etc.

If you enter debug mode, ie. attaching to a already running target, when this issue is produced, where does the code hang?

PS: You can use Segger Ozone to attach to a running target.

Kind regards,

Håkon