Slow Debugging

[Noah]

Hello, I have been recently experiencing an issue with connecting to a debug target.

The Problem:

There is some odd behavior when connecting to a debug target. Best case scenario, the “target remote” gdb command takes 30-60 seconds to connect [see gdb1.gif] before connecting. Other times, visual studio will entirely hang and has to be closed with task manager.

This sort of thing does not happen with all targets (NXP IMX mcu’s seem to work fine).

The GDB log when connecting to the target is shown in the attached file called gdb_log1.jpg

My Setup:

Target: NXP MKV56F1M0VLQ24

Debugger: Segger J-Link

[see debugSettings.jpg]

VisualGDB Version: 5.6R3 build 4531

What I’ve Tried:

I have looked through the forums and tutorials but there wasn’t much that seemed applicable.

I was wondering if I could have some help getting to the root of this issue because it slows me down a lot.

Thank you for your help!

Attachments:

You must be logged in to view attached files.

[support]

Hi,

Based on the timing view, the delay is coming from the Segger GDB stub and not from VisualGDB. Please consider forwarding this information to Segger support for further help.

[Author]

Posts