Debuging on a custom board

RE: Debuging on a custom board

NilsDR — Mon, 15 Jan 2024 08:19:40 GMT

It seems like this is an issue with the version of the nrfconnect vs code extension. I found this similar thread: Debug option in nRF connect extension(v2023.11.301) in vscode is unable to start a debug session .

Downgrading to version v2023.9.169 solved the problem for me, while downgrading to v2023.9.336 got the error again. Something introduced in that upgrade must be causing the problem.

RE: Debuging on a custom board

NilsDR — Fri, 12 Jan 2024 13:32:44 GMT

Hello Naeem,

Thank you for your quick response.

1) Yes I've made a build configuration that uses debug optimizations.

2) No this project is being developed for the first time and is created on the 2.4.0 SDK and 2.4.0 toolchain

3) Yes this is only a problem with my custom board. If I build and debug the exact same project for another non-custom board it works just fine. My custom board is made "out of tree" from the zephyr repo and resides in a folder called boards in the root of the project folder. Maybe it is not linked correctly in some way?

RE: Debuging on a custom board

Naeem Maroof — Fri, 12 Jan 2024 13:22:53 GMT

Hello,

1) Do you add the Debug Optimizations in the build process?

2) Are you migrating a project from another SDK? Please make sure the sample is from the same SDK for which you are building and the toolchain is same.

3) Does this error only occur for your custom board?

/BR, Naeem