Skip to content

nrf53: nrf5340dk_nrf5340_cpunet not executing. #34469

@Mattemagikern

Description

@Mattemagikern

Describe the bug
Received my nrf53 a couple of days ago.
After testing it for a day I attached a debugger to it to solve ble problem, after I detached the debugger, I was unable to flash the board again.

$ nrfjprog -f NRF53 --sectorerase --program build/zephyr/zephyr.hex --coprocessor CP_NETWORK --reset
Parsing image file.
ERROR: The operation attempted is unavailable due to readback protection in
ERROR: your device. Please use --recover to unlock the device.
exit status 16

This issue was solved by a tip in the zephyr slack channel by executing:

nrfjprog  --recover --coprocessor CP_NETWORK
nrfjprog  --recover

However after this I'm able to flash the device but the network cpu dosn't seem to be executing any code.
I'm not able to see any output from ACM0,ACM1,ACM2 when flashing the network cpu. But I do get output If I flash the application CPU.
I'm not sure where to go from here.

To Reproduce
Steps to reproduce the behavior:

  1. west build zephyr/samples/hello_world -b nrf5340dk_nrf5340_cpuapp && west flash
  2. See output in /dev/ttyACM2
  3. rm -rf build && west build zephyr/samples/hello_world -b nrf5340dk_nrf5340_cpunet && west flash
  4. No output in any of the nrf com ports.

Expected behavior
I expect to see:

*** Booting Zephyr OS build zephyr-v2.5.0-2332-g10fc05ced659  ***
Hello World! nrf5340dk_nrf5340_cpuapp

and

*** Booting Zephyr OS build zephyr-v2.5.0-2332-g10fc05ced659  ***
Hello World! nrf5340dk_nrf5340_cpunet

from the device.

Environment (please complete the following information):

  • OS: Linux
 Distributor ID:	Ubuntu
Description: Ubuntu 20.04.2 LTS
Release: 20.04
Codename: focal
  • Toolchain:
nrfjprog version: 10.12.1
JLinkARM.dll version: 7.00a
  • Commit SHA or Version used: 10fc05c

Additional information:
This is not limited to the printk output ofc.
If I flash the network cpu with zephyr/samples/bluetooth/peripherals the device isn't found on the nRF Connect app either though it has previously done so before me attaching the debugger.

Best regards,

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions