• State Not Answered
  • Replies 4 replies
  • Subscribers 69 subscribers
  • Views 189 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 334407
Options

nRF Connect for VS Code refuses to start debug on my custom board

basvkesteren

Hi,

Working on a new project, custom board, using an nRF52840. Wrote my own DTS and all that. Program works as intended, but the nRF Connect for VS Code plugin refuses to start debugging.

Error-message is:

Unknown device type "nrf52840". Only Nordic devices are supported.

I can start ozone manually and load the .elf, but doing this from vscode would be.. nice?

Is this not supported on a custom (Nordic SOC-based) board, or is there something missing in my custom board definition, or project setup? How does the vscode plugin determine the device type?

Thanks,

Parents
  • 0

    Hello,

    I would think that it is a reasonable limitation that you can't debug other chip brands using a Nordic Debugging tool (as we would have to do additional work to support this), but that is not what you are trying to do. You are actually trying to debug on a Nordic chip, so I guess that it is the way that the extensions tries to determine what device it is that doesn't work as intended. 

    Let me run this by our VS Code Extension team, and check if they know how this is checked, and whether it is possible to change this. I will get back to you when I know more, but it might not be before next week.

    Best regards,

    Edvin

  • 0 in reply to Edvin

    Hello,

    Sorry for not coming back to you sooner. If you are still stuck on this, is it possible to upload your custom board files? Can you also specify what NCS version you are using?

    Best regards,

    Edvin

Reply Children
Related