Unable to connect JLink

[PedroMonteiro]

Unable to connect JLink via USB. Installed different versions of JLink without success. Device Manager showns "J-Link driver" under Universal Serial Bus controllers and nrfutil.exe:
C:\Program Files\SEGGER>nrfutil device list
1050094672
Product J-Link
Board version PCA10095
Traits devkit, usb
Supported devices found: 1

but:
C:\Program Files\SEGGER>nrfutil device --jlink-dll "C:\Program Files\SEGGER\JLink_V890\JLink_x64.dll" recover --serial-number 1050094672
 Failed to recover 1050094672, The operation you tried to run is not available for the selected device.
Error: One or more recover tasks failed:
* 1050094672: The operation you tried to run is not available for the selected device.
The operation is either not supported for this type of device or the device has issues and it cannot be recognized (NotFound)

[PedroMonteiro]

Hi,

Just received another DK and this one is running okay. I'm afraid the board is damaged. It started to fail USB enumeration but after several usb driver updates the led blinks for a while and gets steady. But

C:\Program Files\SEGGER>nrfutil device list
1050094672
Product J-Link
Board version PCA10095
Traits devkit, usb

Supported devices found: 1

C:\Program Files\SEGGER>nrfutil device recover
Error: Missing --traits or --serial-number options. Add at least one of the options or make sure you have exactly one supported device connected

I tried different USB cables and I'm running Windows 11 Pro version 25H2 x64

I had similar problems in the past but I was able to recover by re-installing USB drivers. Not anymore.

Regards,

Pedro 

[JONATHAN LL]

Hi Pedro, 

The new DK's have a different debugger chip on them so they behave a bit differently. We have seen some cases where customers end up damaging the USB line and the communication with the DK stops working though the debugger IC. the rest of the DK still works as normal, but its no longer as simple to program\debug on as you would need an external debugger. 

But looks like the debugger IC works here as it is able to report kit and device id. Often this is then related to some HW modifications to the board, maybe a jumper or a solder bridge is modified? 

But good to see that there is some progress here, seems most of the setup works as expected and that the issue lies with the DK.

Regards,
Jonathan

[PedroMonteiro]

Hi Jonathan,

Thanks for your reply. Does it means that the board is not useful anymore with its embedded JLink?

I have another question related to the APPROTECT. I am not able to program the NET Core without a mass erase. Should I open another ticket or continue here?

Regards,
Pedro

[JONATHAN LL]

Hi Pedro,

PedroMonteiro said:

Does it means that the board is not useful anymore with its embedded JLink?

you can still use the board to some degree, like using external debugger or if you have a bootloader on the nRF you can use that if you still want to use the DK, but its limited in use as the debugger SoC no longer works as intended. 

PedroMonteiro said:

have another question related to the APPROTECT. I am not able to program the NET Core without a mass erase. Should I open another ticket or continue here?

APPROTECT blocks access to both the NET and APP core so you will need to run a recover process to be able to write to them. 
You can create a new ticket and discuses best practices for working with the NET core. 

Regards,
Jonathan