RE: example test problem

Simon — Fri, 05 Mar 2021 15:40:57 GMT

I was able to complete the 4 steps in doc/1.5.0/nrf/samples/nrf5340/netboot/README.html#nc-bootloader using NCS v1.5.0, an nRF5340 DK (v0.11.0) and the board selection nrf5340dk_nrf5340_cpuapp. I got the following output:

I: Turned off network core
I: Done updating network core
I: Bootloader chainload address offset: 0xc000
I: Jumping to the first image slot
*** Booting Zephyr OS build v2.4.99-ncs1  ***
Starting Nordic UART service example

The JLink and nrfjprog versions are the following:

$ nrfjprog -v
nrfjprog version: 10.12.1
JLinkARM.dll version: 6.96

In step 2 I used the following commands below. There has been some issues regarding path length due to Windows limitations, therefore I used the name "bld" for the build folder

cd <ncs location>nrf/samples/bluetooth/peripheral_uart
west build -b nrf5340dk_nrf5340_cpuapp -d bld -f -- -DCONFIG_BOOTLOADER_MCUBOOT=y -Dmcuboot_CONFIG_PCD=y

If you encounter issues could you try the command below, to see if approtect is enabled on the network core

nrfjprog --memrd 0x01FF8000 --coprocessor CP_NETWORK

It should read the network core approtect register, and it should return 50FA50FA (unprotected).

Best regards,

Simon

RE: example test problem

Simon — Mon, 01 Mar 2021 14:34:13 GMT

It seems like readback protection is enabled automatically when programming the network and app core, therefore you won't be able to execute step 4-->program to the secondary slot of the application core.

I confirmed this was the case by checking the content of the nRF53 Memory (using the nRF Connect fD. Programmer app) after executing step 3:

I will investigate why this is and how to work around it. I'll get back to you

Best regards,

Simon