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,

[Edvin]

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

[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

[SoukTi]

Hi, I have the same issue only with nrf5340,

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

I'm using 2.8 myself. I tried to debug on both windows and linux hosts but same error.

I can submit the board file but I would prefer to do it through a private ticket

[SoukTi]

I copied the nrf5340dk board definition and directly modified that and it now works. Not sure what fixed it though.

[Jens-Ajisai]

Any news? I get the same issue "Unknown device type "nrf5340". Only Nordic devices are supported. "when I try to debug the nRF5340 on Thingy91X. I use Toolchain v2.9.0 with nRF Connect for VS Code. I use a nRF9151dk as debugger.
Flashing works fine for nRF5340. Debugging only for the nRF9151 core.

I try to debug an unmodified connectivity_bridge application.

[Edvin]

How did you connect the debugger?

Please note this anomaly:

https://docs.nordicsemi.com/bundle/errata_Thingy91X/page/ERR/Thingy91X/latest/anomaly_151_4.html 

Best regards,

Edvin

[Jens-Ajisai]

Thanks for pointing out this errata.
The debug board is not inserted and I connected to P8. The SWD switch is turned to nRF53. Flashing works fine, only debugging not.

I click on debug. A list pops up to select which image to debug. I select the first for the app (not any boot loader nor ipc_radio).

I use a sys build targeting thingy91x/nrf5340/cpuapp.

[Edvin]

Hello,

I got hold of a Thingy91x, and I see the same as you. Let me look into this with our developers, and I will get back to you!

Best regards,

Edvin

[Edvin]

Short update:

This is reported internally, and they will look into it, hopefully fixing it in the next release of the VS Code Extension.

BR,

Edvin

[Jens-Ajisai]

Thanks for checking.