Command 'dap init' failed. CDBGPWRUPACK=0

RE: Command 'dap init' failed. CDBGPWRUPACK=0

Jared — Mon, 22 Jul 2024 12:01:32 GMT

Hi,

Please create a new ticket for this issue,

regards

Jared

RE: Command 'dap init' failed. CDBGPWRUPACK=0

nrdicuser — Sun, 21 Jul 2024 17:02:11 GMT

$ nrfjprog --recover -f NRF52 --log
Recovering device. This operation might take 30s.
[error] [ Client] - Encountered error -21: Command recover executed for 3276 milliseconds with result -21
[error] [ Worker] - Could not connect to CPU core. This may indicate that AP protection is enabled.
Could not find supported CPU.
ERROR: Recover failed. Please make sure that the correct device family is given
ERROR: and try again.

RE: Command 'dap init' failed. CDBGPWRUPACK=0

nrdicuser — Sun, 21 Jul 2024 16:58:41 GMT

Connecting ...
 - Connecting via USB to probe/ programmer device 0
 - Probe/ Programmer firmware: J-Link V9 compiled May  7 2021 16:26:12
 - Probe/ Programmer S/N: 59768885
 - Device "NRF52840_XXAA" selected.
 - Target interface speed: 4000 kHz (Fixed)
 - VTarget = 3.306V
 - InitTarget() start
 - InitTarget() end - Took 2.75ms
 - Failed to attach to CPU. Trying connect under reset.
 - InitTarget() start
 - InitTarget() end - Took 3.36ms
 - Found SW-DP with ID 0x2BA01477
 - Failed to power up DAP
 - ERROR: Failed to connect.
Could not establish a connection to target.
 - ERROR: Connect failed

RE: Command 'dap init' failed. CDBGPWRUPACK=0

nrdicuser — Thu, 18 Jul 2024 06:04:57 GMT

I have the same problem.

Debug: 111 676 arm_adi_v5.c:679 dap_dp_init(): nrf52.dap
Debug: 112 678 arm_adi_v5.c:711 dap_dp_init(): DAP: wait CDBGPWRUPACK
Debug: 113 681 arm_adi_v5.h:641 dap_dp_poll_register(): DAP: poll 4, mask 0x20000000, value 0x20000000
...
Debug: 159 1101 arm_adi_v5.h:655 dap_dp_poll_register(): DAP: poll 4 timeout
Debug: 160 1106 command.c:541 run_command(): Command 'dap init' failed with error code -5
User : 161 1108 command.c:613 command_run_line():
Debug: 162 1115 command.c:541 run_command(): Command 'init' failed with error code -4
User : 163 1120 command.c:613 command_run_line():
Debug: 164 1122 target.c:2171 target_free_all_working_areas_restore(): freeing all working areas
Debug: 165 1137 cmsis_dap.c:1197 cmsis_dap_swd_switch_seq(): SWD-to-JTAG
Debug: 166 1144 cmsis_dap.c:764 cmsis_dap_swd_write_from_queue(): Executing 0 queued transactions from FIFO index 0, same swd ops

RE: Command 'dap init' failed. CDBGPWRUPACK=0

Jared — Tue, 07 Nov 2023 08:23:36 GMT

Hi,

Please create a new ticket for this issue, a new engineer will be help you out once the ticket has been made,

regards

Jared

RE: Command 'dap init' failed. CDBGPWRUPACK=0

Gbr — Mon, 06 Nov 2023 15:11:42 GMT

The official SEGGER J-LINK just has arrived. Now I can use "nrfjprog --recover -f NRF52 --log". But the results is similar: I have no access to the device. 😞

Recovering device. This operation might take 30s.
[error] [ Client] - Encountered error -21: Command recover executed for 10012 milliseconds with result -21
[error] [ Worker] - 10 second timeout elapsed, no time left to wait for debug port to power up.
ERROR: Recover failed. Please make sure that the correct device family is given
ERROR: and try again.

There is no more messages. What is this -21 ? And how could I fix it?

RE: Command 'dap init' failed. CDBGPWRUPACK=0

Gbr — Thu, 19 Oct 2023 19:40:47 GMT

Thanks. The supported one is on its way, it will be here in two weeks. However, I'm still wondering why this one is not working. Meanwhile, I have tested another non-official debugger, the black magic probe, and I have the same result. I cannot connect to the thing. I really hope that the official works.

RE: Command 'dap init' failed. CDBGPWRUPACK=0

Jared — Thu, 19 Oct 2023 09:33:43 GMT

Use an officially supported debugger, 🙂

regards

Jared

RE: Command 'dap init' failed. CDBGPWRUPACK=0

Gbr — Wed, 18 Oct 2023 17:59:40 GMT

I have exactly the same issue! Do you have any solutions?

RE: Command 'dap init' failed. CDBGPWRUPACK=0

Jared — Thu, 31 Aug 2023 09:08:44 GMT

Hi,

The only debugger that we officially support is the SEGGER J-link,

If you want to debug a nRF52840, then I suggest that you use either a standalone debugger from SEGGER or a devkit from us that has a onboard debugger,

regards

Jared