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

[Joakim Jakobsen]

I understand.
I haven't seen an issue with nRF Connect showing devices in the drop-down menu that are not connected before.

Are you using Windows?
If yes, which version are you currently using?
If no, which OS are you using?

Cheers.

[Adrian Eggenberger]

Hi

Sorry for the late response. I was out of office during the last week.

I'm using a Windows 10 Build 1803.

Regards Adrian

[Joakim Jakobsen]

No problem.

Thanks! Then we have the same setup.

"In the Device Manager I can see the COM12 of the only connected DK with the 9 at the end (second in the list)."

I actually think I misread the question.
So in the device manager in Windows, the DK appears as COM12.
But in nRF Connect the device showing up as COM12 is the device that is currently not connected to the computer?

If you disconnect the device from your computer, nothing appears?

Cheers,
Joakim

[Adrian Eggenberger]

Hi

To clear things up a bit I've made some pictures. The COM-Ports have changed, but the problem remains the same.

A nRF52DK with the ending "..99" is connected to the PC. No other DK is connected. As can be seen on the pictures the nRF52 DK generates two entries in the nRF Connect/Programmer (latest version) instead of two. One with the correct serial number (...99) and one with an other previously used serial number (..15).

Since a week the same issue also occurs with a new nRF52840 Dongle. This makes the dongle somehow useless.

For me it looks as the registry entry the nordic tools uses are somehow mixed up. I guess erasing all the registry entries related the the nRFConnect applications would fix the issue. What can happen if we erase all the registry entries on nRFConnect? What registry keys need to be erased?

Regards Adrian