DK boards (nrf52832DK and nrf52840DK) fail to load JLINK driver

RE: DK boards (nrf52832DK and nrf52840DK) fail to load JLINK driver

tesc — Wed, 11 Sep 2019 09:32:06 GMT

Hi,

I am happy to hear that it seems to be working now!

If you experience new difficulties with getting the boards to work, there is a list of checks for common problems in the thread My nRF52/nRF51 DK kit doesn't work. If none of that works it is probably a deeper fault, comparable to what you got after system recovery.

Regards,
Terje

RE: DK boards (nrf52832DK and nrf52840DK) fail to load JLINK driver

Keith Brafford — Tue, 10 Sep 2019 18:38:15 GMT

When I used the J-Link configurator on a working machine I verified that my boards have the latest firmware (jan 7 2019).

I was finally able to get it to work, but I am not sure which of these steps was the solution:

I did another system restore to a previous date about a week earlier than the one I did before
Plugged in one of the nRF52 boards. Failed driver.
Copied the inf file into the Windows\inf folder (a potential solution from a thread on segger:
https://forum.segger.com/index.php/Thread/3918-SOLVED-J-Link-driver-issue/
Re-enumerated. Failure.
Right-clicked on the failed load in the device manager and tried to update the driver. I pointed it to the JLink 6.34b\USBDriver folder and it seemed to recognize that it is a valid driver (which is new—before this system restore, pointing it at 6.44e didn’t work, but this earlier system restore left me with more JLink drivers to choose from, so I picked the next older one that I had before 6.44: 6.34b). But updating it didn’t cause it to load correctly
Right-clicked on the failed load in the device manager and Uninstalled the driver (while keeping the device plugged in and turned on). I also told Windows to “remove the files” after it uninstalled. It uninstalled, then immediately self-installed the 6.34 version of the driver
It worked for a few minutes…I was able to enumerate and see all the components of the driver for all of the boards, and I was able to use Nordic’s command line tools to connect through the segger-ob processor to halt, run, and reset the board
Then the driver hung the machine on an enumeration, again…kinda like what seemed to happen the first time.
I waited a long time, and had to power off the machine
Had to wait over night to let the RAID boot drive do its sanity check
This morning, so far, the driver still loads. I have two nRF52840 boards and one nRF52832 board attached at the same time, and the command line tools seem to be working.

I'll let you know if this situation seems stable, or if the problem returns.

RE: DK boards (nrf52832DK and nrf52840DK) fail to load JLINK driver

tesc — Tue, 10 Sep 2019 16:00:13 GMT

Hi,

As some boards work and others do not, this is extremely unlikely to have anything to do with the particular J-Link. Also the fact that boards work on other computers, just not this one computer where something seems to be wrong with the drivers...

Can you check in "J-Link Configurator" what Emulator Firmware is found on both the working and non-working boards? (On a different computer, that is.) Should be a date and time, e.g. "2019 Jan 7 14:07".

I have found that when installing a newer version of the J-Link drivers, Windows 7 needs to install drivers again when I connect boards that are previously used with the same computer. Did you get any indication of such activity, and/or any message such driver installation failed?

Regards,
Terje

RE: DK boards (nrf52832DK and nrf52840DK) fail to load JLINK driver

Keith Brafford — Tue, 10 Sep 2019 00:46:49 GMT

Can you provide a clue as to the hardware difference between a Segger JLink and the Jlink-onboard type of device? I don't get why the Segger JLink still loads a driver, but the OB one doesn't, but for the two boards where OB still works, it appears to be the same Segger driver that gets loaded.

RE: DK boards (nrf52832DK and nrf52840DK) fail to load JLINK driver

Keith Brafford — Tue, 10 Sep 2019 00:22:57 GMT

Yes, on the non-working boards I've tried the "update driver sw" and pointed it to the USBDriver folder in the JLink installation. Doesn't seem to recognize it as a compatible driver.

when the board is connected and issue the recover command I get the ERROR: There is no debugger ... message like you posted.

nrfjprog version: 10.3.0
JLinkARM.dll version: 6.50a

I have also tried with JLinkARM.dll version 6.44e and it does the same thing. That's the version that NRFConnect tried to install.

RE: DK boards (nrf52832DK and nrf52840DK) fail to load JLINK driver

tesc — Thu, 05 Sep 2019 08:59:08 GMT

Hi,

On the non-working boards, can you try, from Device Manager, to right click to get right-click menu, then "Update Driver Software..."? (Or, in the case of no driver, probably something like "Install Driver" or similar.)

Regarding the nature of the issue, what happens when the board is connected to the computer and you try the command "nrfjprog --recover"? (I.e. what is the error message printed by nrfjprog, and is there anything else happening? "ERROR: There is no debugger connected to the PC"?)

What is the output from "nrfjprog --version"?

Regards,
Terje

RE: DK boards (nrf52832DK and nrf52840DK) fail to load JLINK driver

Keith Brafford — Tue, 03 Sep 2019 17:53:52 GMT

I renamed the SEGGER folder in the registry to SEGGER_OLD, then reinstalled the cmd line utilities (which installed jlkink 6.44e again) and it made a new registry entry, but the problem is still here.

RE: DK boards (nrf52832DK and nrf52840DK) fail to load JLINK driver

Keith Brafford — Tue, 03 Sep 2019 17:23:06 GMT

This exists:
HKEY_USERS\S-1-5-21-863567031-3561377604-2044554372-1000\Software\SEGGER

and has a J-flash, J-Link, and J-LinkRemoteServer sub folder

RE: DK boards (nrf52832DK and nrf52840DK) fail to load JLINK driver

Keith Brafford — Tue, 03 Sep 2019 17:12:39 GMT

New information: I have several nRF DK '32 boards and two '40 boards.

The two '32 boards that I had successfully connected to the win7 host prior to bricking it with the nrfconnect install STILL SEEM TO WORK. that is, those two still enumerate and show up as ids that nrfjprog sees and issues commands to.

The other '32 boards and the '40 boards (that were not connected previously to this machine) do not work. Yet they all work in the linux VM or on a different windows 10 and mac machine.

Is this relevant?

When I plug in the working '32 board, the device driver properties show in the "Universal Bus Serial controllers" section as "J-Link driver" with the Hardware Ids as:
USB\VID_1366&PID_1015&REV_0100&MI_02
USB\VID_1366&PID_1015&MI_02

This is the same on the windows 10 machine as well

When I plug in a non-working '32 board, I get only a COM16 (badged as no driver) in "Other devices" whose Hardware Ids show as:

USB\VID_1366&PID_1015&REV_0100

USB\VID_1366&PID_1015

When I plug this same board into the windows 10 machine, the IDs show up as before
"Universal Bus Serial controllers" section as "J-Link driver" with the Hardware Ids as:
USB\VID_1366&PID_1015&REV_0100&MI_02
USB\VID_1366&PID_1015&MI_02

I've also tried using the jlink configurator to reprogram the firmware from the windows 10 machine and reset the user data, nothing seems to help.

RE: DK boards (nrf52832DK and nrf52840DK) fail to load JLINK driver

Keith Brafford — Tue, 03 Sep 2019 17:02:00 GMT

>Is there anything left in the registry, after uninstalling J-Link and Nordic Semi software? (E.g a SEGGER folder under HKEY_USERS -> random folder name -> Software in the registry.)

I will re-de-install everything and check for that next.

RE: DK boards (nrf52832DK and nrf52840DK) fail to load JLINK driver

Keith Brafford — Tue, 03 Sep 2019 17:01:22 GMT

No conflicts with VMWare. Their scheme of intercepting the board and letting me choose where to connect it works great. If I choose the VM, it is connected, and linux nrfjprog works. If I choose the host, it shows up as an unknown device in the device manager, even though my expensive JLINK is handled correctly by the same host.

I have gathered more info that I will post as an outer level comment.

RE: DK boards (nrf52832DK and nrf52840DK) fail to load JLINK driver

tesc — Tue, 03 Sep 2019 14:25:44 GMT

Hi,

And there are no conflicts with regards to what machine (host or VM) takes ownership of the USB port and boards?

Regarding removing JLINK versions, removing them through the "Programs and Features" method has always worked fine on my Win7 system...

I have sometimes experienced that I must give Windows time to "install drivers" when I plug a DK into a USB port which it has not been connected to before, but after that everything has been fine. (In some occasions it has taken several minutes, though.)

Is there anything left in the registry, after uninstalling J-Link and Nordic Semi software? (E.g a SEGGER folder under HKEY_USERS -> random folder name -> Software in the registry.)

Regards,
Terje

RE: DK boards (nrf52832DK and nrf52840DK) fail to load JLINK driver

Keith Brafford — Tue, 03 Sep 2019 14:12:22 GMT

Yes. I also uninstalled the “windows driver” jlink entries in the programs/features control panel as suggested in the Nordic doc

RE: DK boards (nrf52832DK and nrf52840DK) fail to load JLINK driver

tesc — Tue, 03 Sep 2019 11:54:58 GMT

Hi,

Have you tried also to (uninstall and) install nRF Command Line Tools? In addition to the SEGGER J-Link Software and documentation pack, it contains tools such as the nrfjprog executable and the nrfjprog DLL.

Regards,
Terje