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,

I uninstalled JLink v7.84b (64 bit) and installed JLink v7.66a (64 bit). Same problem as before.

Then, I additioanlly installed JLink v7.66a (32 bit) Now JLink was recognized and Programmer is working.

There seems to be a problem when it comes to 32 bit and 64 bit driver versions. I never experienced any problem with 64 bit JLink driver on any other software, so I think it should also work with nRF Programmer... well, maybe you can fix it in a coming release, or otherwise update your tutorials on infocenter.nordicsemi.com / developer.nordicsemi.com so that it is clear that the 32 bit driver is needed.

Update: I uninstalled both v7.66a driver versions again and installed v7.84b (first 64 bit, then 32 bit). nRF Programmer still recognizes my nRF5340-DK correctly now.

Info: I did not check if thre is a different effect if I install the 32 bit version before 64 bit.

Info: v7.84b 64bit + 32bit also works for "Bluetooth Low Energy" tool and RSSI viewer in combination with nRF52832-DK. I didn't have time to check if the error occurs there, too, if only the 64 bit driver version is installed.

Conclusion: The problem is related to 64 bit driver versions, not newer JLink driver versions.

Best regards,

Michael

[Kurtws]

I'm experiencing the same issue. It's exceptionally frustrating that a new product directly out of the box doesn't even pass step 1, connect.

I can't figure out how to install the 32-bit versions of these programs, the nRF Connect for desktop just does them all automatically. 

Bluetooth Low Energy doesn't detect anything at all.

Programmer sees an unsupported device.

How do I get this to work? Thanks

[puz_md]

Hi Kurtws,

As described above, my solution was as follows:

1. Go to seger.com and download the newest J-Link driver as 32 bit (optional also 64 bit)

2. Login with administrator account, open "Add and remove Programs" (or similiar) via the Start button, in the pop-up search for "J-Link" and remove all existing driver versions.

3. In the administrator account, Install thedriver downloaded in step 1. (If you install both 64 bit and 32 bit, install 64 bit first.)

4. Now nRF Programmer should work (I use it from my User account).

[Kurtws]

Amazing, thank you!

I had them all installed but I guess in various orders.

After uninstalling every j-link installation, installing the 64-bit first then 32-bit of 784d, it can be recognized by the programmer. 

life saver