Unable to start JLink with VSCOde about cortex-debug HOT 5 CLOSED

Oops, close by mistake.

I see no effort from you to debug what you are looking at and how to configure things. Please do so.

from cortex-debug.

There are lots of errors, that are happening and we are reporting them to you. Did you look into this? If you cannot run the tools manually the way we run them (all instructions in the Debug Console), neither can we.

J-Link is connected.
Failed to get index for device name 'Unspecified'.GDBServer will be closed...
Shutting down...
Could not connect to target.
Please check power, connection and settings.Error: Unable to start GDB even after 5 seconds or it couldn't even start Make sure you can start gdb from the command-line and run any command like "echo hello".
If you cannot, it is most likely because "libncurses" or "python" is not installed. Some GDBs require these
GDB session ended unexpectedly. exit-code: 253
GDB could not start as expected. Bad installation or version mismatch. See if you can start gdb from a shell prompt and check its version (Must be >= 9)

Also, I cannot make heads or tails of what you posted. That is not what our entire Debug Console looks like. It is barely recognizable.

I will close this if you do not respond or do not do your investigation.

from cortex-debug.

Hi, attaching the entire snapshot of the debug console on Visual studio code:

from cortex-debug.

Please learn to use markdown, so you can paste unformatted text. Here i can at least some relevant stuff. Having text form, we'll allow me to copy/paste stuff. Are you sure you are showing me that actual configuration from launc.json. Nothing matches.

You need to read the whole output in the Debug Console to make sure things make sense. From what I see, we think you are debugging the JLink executable. Not your firmware. Pay attention to every error message in your Debug Console

from cortex-debug.

@haneefdm

I have similar issue, created a better topic for it if you want to close this one. It could be a version issue.

#954

from cortex-debug.