You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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:
west build zephyr/samples/hello_world -b nrf5340dk_nrf5340_cpuapp && west flash
See output in /dev/ttyACM2
rm -rf build && west build zephyr/samples/hello_world -b nrf5340dk_nrf5340_cpunet && west flash
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):
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,
The text was updated successfully, but these errors were encountered:
You need to build and flash a cpuapp firmware with BOARD_ENABLE_CPUNET enabled:
west build samples/hello_world -b nrf5340dk_nrf5340_cpuapp -- -DCONFIG_BOARD_ENABLE_CPUNET
west flash
rm build -r
west build samples/hello_world -b nrf5340dk_nrf5340_cpunet && west flash
You should see cpuapp output on /dev/ttyACM2 and cpunet output on /dev/ttyACM0.
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.
This issue was solved by a tip in the zephyr slack channel by executing:
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:
west build zephyr/samples/hello_world -b nrf5340dk_nrf5340_cpuapp && west flash
rm -rf build && west build zephyr/samples/hello_world -b nrf5340dk_nrf5340_cpunet && west flash
Expected behavior
I expect to see:
and
from the device.
Environment (please complete the following information):
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,
The text was updated successfully, but these errors were encountered: