j-link connection fail on nrf52833 DK board.

[bini2007]

We have found a nrf52833 DK (PCA101000) with id, 685888541 with 2024.4.

So, it might be used as previous project in our company.

Anyway, I tried to test with this DK board. but I found the fail of j-link connection via PC.

First of all, when I attached dk board to PC, device manager on PC shows device drivers shown as MSD Volume USB Device, J-link driver and JLink CDC UART Port.

So I guessed the DK board was normal. Even thought it looks normal, I found the failure on J-link connection on on-board JLink on nRF52833 DK board.

The error are as following:

D:\ProgramFiles\SEGGER\JLink_V794e>JLink.exe
SEGGER J-Link Commander V7.94e (Compiled Jan 15 2024 15:20:36)
DLL version V7.94e, compiled Jan 15 2024 15:18:46

Connecting to J-Link via USB...O.K.
Firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Oct 30 2023 12:12:17
Hardware version: V1.00
J-Link uptime (since boot): 0d 00h 01m 36s
S/N: 685888541
License(s): RDI, FlashBP, FlashDL, JFlash, GDB
USB speed mode: High speed (480 MBit/s)
VTref=3.300V


Type "connect" to establish a target connection, '?' for help
J-Link>connect
Please specify device / core. <Default>: NRF52833_XXAA
Type '?' for selection dialog
Device>
Please specify target interface:
  J) JTAG (Default)
  S) SWD
  T) cJTAG
TIF>S
Specify target interface speed [kHz]. <Default>: 4000 kHz
Speed>10
Device "NRF52833_XXAA" selected.


Connecting to target via SWD
InitTarget() start
InitTarget() end - Took 90.4ms
Found SW-DP with ID 0x2BA01477
DPIDR: 0x2BA01477
CoreSight SoC-400 or earlier
Scanning AP map to find all available APs
AP[0]: Stopped AP scan as end of AP map has been reached
Iterating through AP map to find AHB-AP to use
Attach to CPU failed. Executing connect under reset.
Failed to power up DAP
Connect fallback: Reset via Reset pin & Connect.
InitTarget() start
InitTarget() end - Took 89.8ms
Found SW-DP with ID 0x2BA01477
Failed to power up DAP
Cannot connect to target.
J-Link>

Please let me know how to solve this problem.

Thanks,

Jaehong Park

[bini2007]

In addition to above,

I have tested it with "nrfjprog --recover" and "nrfjprog --eraseall". The error log are followings:

D:\ProgramFiles\Nordic Semiconductor\nrf-command-line-tools\bin>nrfjprog.exe --recover
[error] [ Client] - Encountered error -105: Command connect_to_emu_with_snr executed for 329 milliseconds with result -105
ERROR: Unable to connect to a debugger.
[error] [ Worker] - JLinkARM.dll Open returned error 'Cannot connect to J-Link.'
ERROR: The JLinkARM DLL timed out while communicating to the J-Link probe.
ERROR: If the error condition persists, run the same command again with
ERROR: argument -- log, contact Nordic Semiconductor and provide the generated
ERROR: log.log file to them.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.

D:\ProgramFiles\Nordic Semiconductor\nrf-command-line-tools\bin>nrfjprog.exe --eraseall
[error] [ Client] - Encountered error -105: Command connect_to_emu_with_snr executed for 298 milliseconds with result -105
ERROR: Unable to connect to a debugger.
[error] [ Worker] - JLinkARM.dll Open returned error 'Cannot connect to J-Link.'
ERROR: The JLinkARM DLL timed out while communicating to the J-Link probe.
ERROR: If the error condition persists, run the same command again with
ERROR: argument -- log, contact Nordic Semiconductor and provide the generated
ERROR: log.log file to them.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.

D:\ProgramFiles\Nordic Semiconductor\nrf-command-line-tools\bin>

Please advice me how to solve it.