Unable to flash / debug device based on nRF52840 with J-LINK in the nRF Connect SDK (VS Code)

[Jev]

Hi, 

I am completely new to the nRF Connect SDK and trying to get used to it and having trouble with flashing / debugging the device using J-Link.

It shows the J-Link in the Connected Devices as 50117619, and displays the correct MCU, I can recover, and erase the device without issues, but when comes to flashing it gives me the error mentioned below. As well as it showing J-Link as J-Link in the nRF Programmer app.

The following error in the Terminal:

Flashing build to 50117619
C:\Windows\system32\cmd.exe /d /s /c "west flash -d c:\Nordic\MyApps\MyCentral\build --skip-rebuild -i 50117619"

-- west flash: using runner jlink
FATAL ERROR: required program JLink.exe not found; install it or add its location to PATH

Where and how should I add the PATH for the JLink.exe, please? Why it is so complicated?

Hardware: Adafruit Feather nRF52840 Express

SDK: nRF Connect SDK v2.3.0

Programmer: J-Link Base

Thanks,
Jev

[Simonr]

Hi Jev

I'm sorry about the late reply to this case, but Karl has been otherwise engaged as of late, so I have been asked to take over. I spent some time reading into this, and it seems to be the same problem reported in this and this case. Unfortunately there weren't one fix to the two cases, but there were a few fixes that proved potent at least. First off, what Windows version exactly are you using. It was seen specifically on Windows 10 PRO for workstations and not on Windows 10 PRO for instance. 

The first thing you can try is to downgrade the nRF Connect for VS Code extension to v2022.7.111, as that got rid of the J-Link error you're seeing. Then a build error due to a path issue seemed to trig instead, that could be fixed by adding the following to the PATH Environment Variable:

%SystemRoot%\system32

%SystemRoot%\system32\cmd.exe

A third user reports only being able to remedy this by reinstalling Windows. Håkon who handled those two cases is unfortunately out of office sick today, but I will discuss this with him when he's back if he ever found a potent workaround/fix for this.

Best regards,

Simon