Segger J-Link Plus not listed in VS Code connected devices

[abhiash4nRF]

Hello Experts,

On my Windows 10 PC, I have installed nRF for Desktop v5.0.2 and J-Link Pack version 7.94e got installed along with it.

Also installed Nordic command line tools using " nrf-command-line-tools-10.24.2-x64 ".

In VS code have installed and enabled all nRF extensions however the J-Link Plus connected never appears in Connected Devices for a nRF5340 custom board.

Also the Welcome and Applications Screen never appears as shown in the screen snap below.

Tried different versions of J-Link package however no progress. 

I am using ncs v2.6.0 and VS code v1.92.1

Also uninstalled and installed VS Code, Tool Chain, a couple of times however no effect 

 PS: previously with the same hardware I had no such issues. Something has changed.

Kindly guide me towards the solution

Thanks,

AbhiAsh

[Priyanka]

Hi Abhishek,

Do you open VSCode directly, or via the Toolchain Manager? While opening via the Toolchain manager too, do you face this issue? 
Also, as mentioned by @jorg fischer, your debug adapter might also need a firmware update.

Regards,

Priyanka

[abhiash4nRF]

1. On my PC I installed the J-Link Package v7.98 release
Then using J-Link configurator I updated the J-Link Plus to latest firmware available
Product = J-Link PLUS V12.00
HostFW = 2024 Jul 3 16:56
EmuFW = 2024 Jul 3 16:56

2. When I launch the VScode directly then still it does not show J-link in connected devices
   Then I also launched it using nRF for Desktop > Tool Chain Manager v1.5.1 .... same behaviour

3. Then I used the J-Link Commander i.e. Jlink. With this it connects to the target

Specify target interface speed [kHz]. <Default>: 4000 kHz
Speed>
Device "NRF5340_XXAA_APP" selected.

LOG>
Connecting to target via SWD
ConfigTargetSettings() start
ConfigTargetSettings() end - Took 30us
InitTarget() start
InitTarget() end - Took 2.36ms
Found SW-DP with ID 0x6BA02477
DPIDR: 0x6BA02477
CoreSight SoC-400 or earlier
AP map detection skipped. Manually configured AP map found.
AP[0]: AHB-AP (IDR: Not set)
AP[1]: AHB-AP (IDR: Not set)
AP[2]: MEM-AP (IDR: Not set)
AP[3]: MEM-AP (IDR: Not set)
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xE00FE000
CPUID register: 0x410FD214. Implementer code: 0x41 (ARM)
Feature set: Mainline
Cache: No cache
Found Cortex-M33 r0p4, Little endian.
FPUnit: 8 code (BP) slots and 0 literal slots
Security extension: implemented
Secure debug: enabled
CoreSight components:
ROMTbl[0] @ E00FE000
[0][0]: E00FF000 CID B105100D PID 000BB4C9 ROM Table
ROMTbl[1] @ E00FF000
[1][0]: E000E000 CID B105900D PID 000BBD21 DEVARCH 47702A04 DEVTYPE 00 Cortex-M33
[1][1]: E0001000 CID B105900D PID 000BBD21 DEVARCH 47701A02 DEVTYPE 00 DWT
[1][2]: E0002000 CID B105900D PID 000BBD21 DEVARCH 47701A03 DEVTYPE 00 FPB
[1][3]: E0000000 CID B105900D PID 000BBD21 DEVARCH 47701A01 DEVTYPE 43 ITM
[1][5]: E0041000 CID B105900D PID 002BBD21 DEVARCH 47724A13 DEVTYPE 13 ETM
[1][6]: E0042000 CID B105900D PID 000BBD21 DEVARCH 47701A14 DEVTYPE 14 CSS600-CTI
[0][1]: E0040000 CID B105900D PID 000BBD21 DEVARCH 00000000 DEVTYPE 11 TPIU
Memory zones:
Zone: "Default" Description: Default access mode
Cortex-M33 identified.

[Priyanka]

Hi Abhishek,

Could you attach the Support Information? (Ctrl+Shift+P) -> nRF Connect:Generate Support Information.

-Priyanka

[abhiash4nRF]

Hi Priyanka,

In VS Code when I do View > Command Palette > nRFconnect: Generate Support Information

there is no activity at all

Thanks,

Abhishek

[Priyanka]

That looks strange. It should ideally appear in the output window:

If this also doesn't work, could you try uninstalling the extension, SDK, nRF Connect for Desktop application and re-installing them? 

Apologies for the trouble, but sometimes some problems during download or installations can cause strange activity after installation.

-Priyanka

[PjGlasso]

abhiash4nRF said:

Device "NRF5340_XXAA_APP" selected.

Hi there,

I don't think this is the correct device... Try picking a different device.

HTH

GL :-) PJ :v: