- This topic has 1 reply, 2 voices, and was last updated 2 hours, 51 minutes ago by
.
-
Posts
-
Hi,
I have just bought a J-Link Ultra+ and its working correctly and I can flash the boards and debug correctly in Visual Studio 2022 however when I end a debugging session it does not halt the processor similar to the ST-Link I was using previously. Are their any commands I can pass in the settings of Visual GDB in Visual Studio 2022 to halt the processor when debugging ends?
I was not sure if this was a question for both Visual GDB team or Segger team.
Many thanks for your time.
Hope you can help me.
/Kevin
Hi,
This is likely caused by a particular combination of settings, and the challenge would be narrowing down the exact settings.
You can start by logging the J-Link GDB server command line and the GDB commands via VisualGDB (View->Other Windows->VisualGDB Diagnostics Console for command lines and VisualGDB Project Properties -> Advanced GDB Settings to enable GDB logging). This should help you reproduce the problem with just command-line tools from Segger, so you can share the repro steps to them and see if they have any suggestions.
- You must be logged in to reply to this topic.