Inconsistent Debugging with nRF Connect SDK on PC

[Embel_Tech]

Hello team,

        We are in the process of migrating from the nRF5 SDK to the nRF Connect SDK for our upcoming projects.

        We have followed all the official setup and installation steps for nRF Connect SDK on our desktop PC (Windows). As a quick test, we successfully ran the beacon example on the nRF52832 DK — everything worked as expected.

       However, when testing the central_uart example, we encountered inconsistent behavior during debugging:

Sometimes the project debugs successfully. and other times, it fails to start the debugger.

      Interestingly, after adding logging configurations in the project’s prj.conf file, it occasionally works — but still not consistently.

     To cross-check, we ran the same central_uart example on a laptop setup with identical installation steps — and it works reliably every time.

Query:
      Are there any known issues, limitations, or dependencies when using nRF Connect SDK on a desktop PC vs a laptop setup? Could there be any hardware, driver, or USB-related factors that might cause such inconsistent debugging behavior on PC?

      Any insights, suggestions, or similar experiences would be greatly appreciated.

[Øyvind]

Hello, 

What version of the DK or external debugger are you using during debugging? Do you have logs to share with us? 

  Are there any known issues, limitations, or dependencies when using nRF Connect SDK on a desktop PC vs a laptop setup? Could there be any hardware, driver, or USB-related factors that might cause such inconsistent debugging behavior on PC?

None that I'm aware of. 

We have followed all the official setup and installation steps for nRF Connect SDK on our desktop PC (Windows).

Did you install the Visual Studio code extension as well? If so, could you please provide the output of nRF Connect: Generate support information.

Kind regards,
Øyvind