S32 Design Studio 3.6.6 hang while debugging over Segger

[durga_choudhury]

There is an issue with S32DS v 3.6.6 where attempts to relaunch (or completely stop and start a new debug session without restarting the IDE) hangs the IDE when the debug pod is a Segger Jlink Plus. The hang seems to be while trying to launch the GDB server for the Jlink. The only recovery is to 1. Kill the S32DS IDE AND 2. Kill the Jlink GDB server from the Windows task manager.

I can confirm that this is a software bug (not necessarily with the IDE itself) and not a hardware issue because the *same* board with the *same* pod on the *same* host PC work fine on S32DS for ARM 2.2. I cannot provide a 'recipe to reproduce', but it happens almost every 3-4 relaunch attempts, so fairly reproducible.

Some details:

Chip used: S32K148 in 144 package; board is custom designed

Host OS: Windows 11

[jiri_kral]

Hi, 

please make sure that you are using the latest Segger eclipse plugin. You can download installer from Segger web pages, the installer will ask if you like to update plugin in existing S32DS on your PC. 

[durga_choudhury]

In my Windows host, I have Segger tools installed at two different locations:

1. C:\NXP\S32DS.3.6.6\Drivers\Segger\  This was installed by the S32DS installer. I use the gdb server backend, JLinkGDBServerCL.exe, from this location (this is actually automatically chosen by the S32DS IDE) This location has only the gdb server from Segger, not the other Jlink tools.

2. C:\Program Files\SEGGER\JLink\  This location is populated when I run the Segger JLink installation program JLink_Windows_V848_x86_64.exe. This has the whole suite of Jlink tools, including another version of the gdb server backend. I use some of the tools from here, e.g. the RTT viewer as a console.

Are you asking me to use the gdb server from location #2 above? I tried that, but it did not work. Unlike the gdb server from location #1, which freezes up occasionally, this one did not work *at all* (I don't remember the specifics of what went wrong, but it was basically a version mismatch.)

If  you are suggesting something else, please clarify.