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.

[Lix Paulian]

Thank you for the clarification, but saving the configuration does not help, because THE property required does not exist (e.g. ipAddress).

In what the “more free but less automated debug configuration supported” concerns, I must admit that I do not understand what you mean. Can you maybe clarify?

[Cartu38 OpenDev]

​@Lix Paulian 

Doing résolve launch configuration is just to get inspiration from. In real it exposes what the tool is doing behind the scene. So yes it should comfirm your missing parameter is not used.

Non automated/free generic one is a template to be filled fully by you. Because no process applied on top of what you are going to write is what is going to be executed. This generic is doing no assumption at all. The first is you can ask for any gdb server and any of its native parameter. 

[Lix Paulian]

Thank you for the additional information.

[yocosha]

​@Lix Paulian 
Hi,
Did you find a solution for this issue? if you did, could you please share it?

Thanks

 

[Lix Paulian]

Hi yocosha, no, I have no solution. For the time being I am accepting that I have to enter the IP address each time when the Segger driver pops up before download. After a conversation with Gemini it appears that there might be a solution, but it is so convoluted that I preferred to keep the things as they are until hopefully ST implements the missing functionality.