VS Code debugging not behaving properly

RE: VS Code debugging not behaving properly

JONATHAN LL — Tue, 08 Nov 2022 14:54:32 GMT

Thanks for your detailed feedback,

I have made sure to add the additional SEGGER features as a feature request internally.

Regards,
Jonathan

RE: VS Code debugging not behaving properly

Kyrre Aalerud — Mon, 24 Oct 2022 07:12:56 GMT

VS Code is 1.72.2 and nRF pack is v2022.9.6 and we connect to nRF5340 board with similar setup to original DK using DK as programmer.
In Segger Studio everything is fast, and was working fine (although segger has horrible code lookup, possibly from too low bits hash table?). Changing to SDK 2.1.0 with Segger no longer supported, we are forced to use VS Code.

With Segger Studio, you were able to reconnect to a device you already flashed and that had been running. There was a choice between just connecting or flash the unit and reset it. This option appears missing.

In addition, hitting reset processor from debugger appears to loose connection to RTT which then has to be re-established after running target again. This looses valuable data during boot (when debugging boot). In Segger Studio this connection was re-established and no data was lost. It also reset mcu properly and connected debugging with halted cpu at reset vector properly. With VS Code the system appears to "run away" during reset before debugger catches up.

RE: VS Code debugging not behaving properly

JONATHAN LL — Fri, 21 Oct 2022 14:42:11 GMT

Hi,

What hardware are you connecting?

Do you experience the slow flashing with all samples or just some?

What do you mean by connecting to target without reflashing? Do you have to click flash again before you are able to debug?

What version of the extension are you using? and what version of VS code?

Regards,
Jonathan