nRF Connect invalid/no COM port

[Adrian Eggenberger]

Hi

I've a problem with one or maybe two of my nRF52 DK's. If I open nRFConnect 2.4.0 Programmer (or the BLE app) and connect only one of my nRF52 DK's the device selector shows the following image:

The serial number of the connected nRF52 DK matches the 2nd entry in the list. The first entry is also one of my nRF52 DK's, but not connected at the moment. The system itself has assigned the connected DK the comport COM12. It seems that the registry with comport/jLink mapping is broken somehow.

How can I fix this?

Regards Adrian

[Joakim Jakobsen]

Hi!

So the first entry in the device selector is a DK (showing as COM12) that is not connected to your computer?

Can you see the DK as a connected COM port in the device manager on your computer? Or is it only in the nRF Connect apps that it apears?
I guess this does not only show up in the BLE/Programmer app? You see the same issue i.e in the RSSI Viewer app?

I can see that you have the latest version of the nRF Connect. Have you also made sure that the Programmer/Bluetooth low energy app is updated to the latest version? You can check this by opening the "Add/remove apps" tab in nRF Connect, and check that all apps are up to date.

Best regards,
Joakim.

[Adrian Eggenberger]

Hi Joakim

The first entry is a DK i use sometimes, but at the moment it was not connected to the computer. In the Device Manager I can see the COM12 of the only connected DK with the 9 at the end (second in the list).

The effect is the same on all App in nRF Connect. They are all updated to the last version (e.g. 2.2.0 of the Bluetooth Low Energy App).

Regards Adrian

[Adrian Eggenberger]

Hi Joakim

Selecting one of the invalid entries causes an error message. I expect this is because both informations (comport/jlink serial) is needed on a device.

It somehow seems that my registry entries for the nRF Connect are broken (don't know why). Is there a list of registry paths I can delete to start from scratch?

Regards Adrian

[Joakim Jakobsen]

Adrian Eggenberger said:

Selecting one of the invalid entries causes an error message. I expect this is because both informations (comport/jlink serial) is needed on a device.

 What kind of error do you get from this? Maybe you could upload a screenshot?

Adrian Eggenberger said:

It somehow seems that my registry entries for the nRF Connect are broken (don't know why). Is there a list of registry paths I can delete to start from scratch?

 I'm not quite sure about this, but I'll do some research and find out.

Best regards.

[Adrian Eggenberger]

The attached screenshots have been made after selecting the entries from the list.

[Joakim Jakobsen]

Thank you.

I'll investigate the issue, and get back to you.

Regards,
Joakim

[Joakim Jakobsen]

Hi again.

I haven't been able to reproduce or find any useful information to solve this.

The only suggestion I have so far is to re-install nRF Connect, and see if that may resolve the issue.

Best regards,
Joakim

[Adrian Eggenberger]

The reinstallation of the nRFConnect didn't help, but I've found a solution myself. The root cause for the problem was broken registry entries für the jLink devices (VID 0x1366) in the path "Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB".

The solution was to delete all the entries in this path for the devices with VID 0x1366. This can be done by the regedit.exe, but it needs system rights. I was only able to do this with the help of the freeware tool "RunAsSystem" that can be found here: https://www.uwe-sieber.de/misc_tools_e.html.

1) Start the regedit with "RunAsSystem "%windir%\regedit.exe"
2) Change to the folder "Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB"
3) Delete all entries starting with "VID_1366"

Maybe this helps someone… 

Regards Adrian