It would be great if the STM32CubeProgrammer would do proper error handling for J-Link debug probes instead of crashing.
Issue:
Every times I try to the connect to a STM32 target that is not powered, or not properly connected the GUI pops up three error messages that need to be close separately and on the next connect it pops up another error message and get stuck. So that the program needs to be completely restarted.
Preferred behavior:
STM32Cubeprogrammer show only a single pop up or only log a warning message and recovers from this situation in that that allows it to connect to a STM32 target.
This is no regression and has been observed since j-link probes are supported.
The last time it has been observed is on a Windows 11 PC with intel CPU, targeting a STM32G4 MCU with STM32Cubeprogrammer v2.21.0, J-Link HW version V11.00(latest FW Apr 1 2025)
