• State Verified Answer
  • Replies 13 replies
  • Subscribers 74 subscribers
  • Views 7077 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 210926
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

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

Parents Reply Children
  • 0 in reply to Adrian Eggenberger

    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

  • 0 in reply to Joakim Jakobsen

    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

  • 0 in reply to Adrian Eggenberger

    Thanks for clearing that up.

    What happens when you try to select one of the devices in the drop-down-menu?

    As I said, I haven't seen this before, so I have forwarded your request to our developers.

    I'll get back to you if they are able to find a solution to the problem, or need any more information.

    Best regards,
    Joakim.

  • 0 in reply to Joakim Jakobsen

    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

  • 0 in reply to Adrian Eggenberger
    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.

Related
Terms of service