Blinky non-secure sample not running

RE: Blinky non-secure sample not running

Bard — Mon, 01 Feb 2021 18:24:15 GMT

The issue is probably related to this issue 263035 and therefore resolved.

Thank you

RE: Blinky non-secure sample not running

Kenneth — Mon, 01 Feb 2021 17:26:58 GMT

Hi,

Not sure if you still have issues, but fyi the nRF5340 is now in mass production, and I recommend to get a new nRF5340-DK with the production silicon. You should also update to Connect SDK v1.4.x for latest fixes and features (this is required if you want to use the nRF5340 moving forward, the nRF5340 preview DK is not recommended for development).

Kenneth

RE: Blinky non-secure sample not running

Bard — Tue, 05 Jan 2021 11:20:01 GMT

Back on this issue...

Now: using Connect SDK ver 1.3.1, Custom Board

Secure and non-secure version both behave identical. But only starting after running: nrfjprog --pinreset

Do not start otherwise; not even with toggling of the reset pin.

Why do I have to issue nrfjprog --pinreset to start? How to proceed?

RE: Blinky non-secure sample not running

Bard — Fri, 25 Sep 2020 06:13:42 GMT

I'm using both a custom board and PDK 0.8.0. I didn't modify any configs, but I added a new gpio output - pin24 (see code above)

Same result: No compile error. Only secure version running

Note: debugger only working with secure version, with non-secure -> lots of missing header files

RE: Blinky non-secure sample not running

haakonsh — Thu, 24 Sep 2020 13:17:45 GMT

Did you modify any configs?

Are you using the PDK v0.7.0?

I'll try to re-produce it on my end.

RE: Blinky non-secure sample not running

Bard — Thu, 24 Sep 2020 07:41:51 GMT

Another observation:

I have to run: nrfjprog --pinreset for the secure version to start. Forcing nReset manually does not work.

RE: Blinky non-secure sample not running

Bard — Thu, 24 Sep 2020 07:19:13 GMT

It's no compile error. I monitor the P0.24 pin, and it toggles fine with the secure version, not at all with the non-secure.

RE: Blinky non-secure sample not running

haakonsh — Thu, 24 Sep 2020 07:00:40 GMT

Is it a build error, runtime error, or does it simply not run at all?