Native J-Link over IP support and persistent ID handling

[Lix Paulian]

I am having a hard time to use a JLink via IP on the local LAN. I can connect, but every time I launch a debug session, a pop-up from Segger appears asking me for the JLink identifier: I have to enter the IP address, and then it works. But this is rather nerving to have to enter the IP address every time I launch a debug/run session.

It seems that the extension does not officially support JLink over IP. If this is true, please add this important feature in a future update. Specifically that the jlinkgdbtarget configuration type in the launch.json schema be updated to support an ipAddress field or a generic serverArgs/serverParameters array (matching how they already handle stgdbtarget and openocdtarget).

Currently because the extension forces a hardcoded string layout and uses the silent (-s) flag, it actively suppresses SEGGER's standard native fallbacks (like reading workspace JLinkGDBServer.ini files).

Thank you for an otherwise excellent tool (STM extensions + VSC).

 

 

[Cartu38 OpenDev]

​@Lix Paulian 

I’ve no idea myself about JLink setup nor STM future plan about.

Pending answer from STM, be aware a more free but less automated debug configuration is supported:

Most probably you can pass here all parameters you want to JLink GDB server.

Possibly too as alternative or help :

At first launch it will save for you a resolved configuration you can take as inspiration or to hack possibly.

[Lix Paulian]

Hello Cartu38 OpenDev,

 

If I understand well, you are suggesting that I install an extra extension for debugging. Correct?

[Cartu38 OpenDev]

Hello Cartu38 OpenDev,

 

If I understand well, you are suggesting that I install an extra extension for debugging. Correct?

Nope. This generic launch configuration is part of STM32CubeIDE for Visual Studio Code extension pack.

Such said it is served by a dedicated extension.