• State Verified Answer
  • Locked Locked
  • Replies 12 replies
  • Subscribers 77 subscribers
  • Views 4072 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 277098
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Debug session fails to run Zephyr blinky sample in VSCode with nRF Connect

ParkerMcD

Hello,

I'm trying out nRF Connect running inside VS Code and I'm running into issues debuggin my code.  I followed the Nordic setup tutorial and installed the latest nRF Connect SDK, then nRF Command Line Tools with Segger Tools, Visual Studio Code and finally added the nRF Connect extension package (Cortex-Debug,  NRF Connect, nRF Kconfig etc.).  I then created an application as directed, and then a build configuration with debug options enabled.  I then built the application and flashed my board (Thingy:52) and saw the LED blink on my development board.  Up till this point everything worked great, then I tried hitting the debug button under the action menu and received the following error below:

I also tried building, downloading code and debugging in the Segger nRF Connect IDE and everything worked great!  So I assumed my base toolchain is good.  I'm not very experienced with setting up IDEs and based on the tutorial this step should just work without me editing any .jason files etc.  Any obvious things I'm missing?  

Hardware/Software Setup:

OS:  Windows 10

VS Code Version:  1.60.2

nRF Connect SDK Version:  v1.7.0

J-Link Version:  7.54c

Debugger:  j-link segger EDU edtion

Development Board:  Thingy:52

Thanks!

Parker

Parents
  • 0

    Hi Parker,

    Thanks for your patience whilst we look into this. We'd like to gather a bit more information about your environment so that we can more easily reproduce this problem. To that end, we've created a build that more accurately detects the installed tools in the Generate Support Information command.

    Since this is a private build, I can't upload it directly to this issue, but I can do so if you create a new private ticket. You can do so by clicking the "Support +" button at the top of the page, and then selecting "Private Support Ticket". You might need to add some more information to your DevZone profile for this option to be available.

    Best regards,

    Dee

    VS Code Team

  • 0 in reply to Dee Roberts

    Great!  I'm making a private ticket now.

    Cheers,

    Parker

Reply Children
No Data
Related
Terms of service