nRF Programmer cannot recognize nRF5340-DK (SEGGER JLink driver is newer than nRF Connect for Desktop version)

[puz_md]

Hello, after installing nRF Connect and nRF Programmer v3.0.4, I cannot connect to my nRF5340-DK.

The DK is corrctly recognized as a mass storage device, and it is listed as "J-Link" (with a number below) under "SELECT DEVICE" in nRF Programmer, but if I select it, the log says "Unsupported device":

I have SEGGER JLink v7.84b (64 bit version) installed, which is newer than the driver version that came with the latest nRF Connect for Desktop.

Does nRF Programmer require exactly the JLink driver cersion that came with nRF Connect for Desktop? I have never seen a development tool that doesn't work with newer driver versions which are backward compatible. This does not make sense to me.

Do I really have to downgrade my JLink driver version? Is it okay to use 64 bit drivers or do I need te 32 bit version for nRF Programmer? Or could this problem be related to my issues during nRF Connect for Desktop installation which I discussed in my other ticket (see here)?

I never expected running into so much trouble when migrating my system to the new nRF Connect and development framework...

[Joakim Jakobsen]

Hi.

I never expected running into so much trouble when migrating my system to the new nRF Connect and development framework...

Sorry to hear that you are running into so many problems. We'll do our best to help solve your issues.

11:12:26:355 Installed JLink version does not match the provided version (V7.66a)

Could you try again using version 7.66a and see if that solves the issue? Or you can install by the latest version of nRF-Command-Line-Tools.

Br,
Joakim

[puz_md]

Hi Joakim,

anything new from your side? Could you please confirm if there is an issue using nRF Connect or nRF Programmer (or even the nRF Connect extension for VS Code) with 64 bit SEGGER JLink driver?

I think special system setup requirements should be documented somewhere easily to be found. As many software developers use SEGGER software and hardware on other platforms than nRF Connect SDK, I suppose there will also be a lot people using just 64 bit JLink drivers wo don't want to downgrade to an outdated version that comes with the nRF Connect for PC installer. I would also be happy if Nordic could make the nRF Connect SDK compatible with 64 bit JLink drivers, of course (which would be the best solution in my opinion).

[Joakim Jakobsen]

Thanks for the information you provided on the issue.

puz_md said:

anything new from your side?

I don't have any news as of now. I've made a report to our developers, and I'll get back to you with any information from them.

Br,
Joakim

[Achim Kraus]

I would also appreciate, if this gets solved.

Very irritating!

Using the nRF Connect Programmer (v3.0.8) and a nRF9160-DK works, using a nRF5340-DK not.

Using Visual Studio both are working.

The both devices are using different USB product IDs.

I guess, mainly the "is it really a Nordic Device check" is broken.

Edit:

It depends on using a debug header (TC2030-CTX). With that, the DK switches to the external debug interface and if on start no nordic device is connected to that external debug interface, the nRF5340-DK is refused by the programmer.

The nRF9160-DK doesn't show that effect. That works with and without that debug header.