What happened to the Seger J-Link.

[PJank.1]

The segger J-Link support has vanished. What is going on? Are you going to support only ST-Link. I afraid ST_Link is not too good for professional development as it is:

• extremelly slow
• no RTOS avare debugging
• no software breakpoints

+ many other small issues

[Markus GIRDLAND]

I believe I might have answered you in another thread, but just to be safe:

J-Link support is filtered out from targets it doesn't support by default in v1.1.0 but it will be fixed in the next release. For any other target that it does support by default J-Link can still be selected.

[pj_stm]

You have chosen the worst possible way. You want to make a dumb tool (IDE) to be smarter than the developers. Do not filter anything. I know how to debug and what targets are supported by the particular version of the particular gdbserver . The worst thing is if I have to search for silly workarounds. Big minus.

[Markus GIRDLAND]

There were differing sides in the dev team but that's basically the exact argument that the "no filtering" side were using :smiling_face_with_smiling_eyes:

Edit: 1.2.0 should be out in a few hours, it's fixed there.