topic Re: Unable to debug code in S32 design studio V3.4 in S32K

Unable to debug code in S32 design studio V3.4

P007 — Mon, 23 Sep 2024 12:58:01 GMT

Hi,

I'm facing issue with S32 Design Studio V3.4, when I try to debug the issue occur during that is

No source available for "(gdb[1].proc[42000].threadGroup[i1],gdb[1].proc[42000].OSthread[1]).thread[1].frame[0]"Disassembly

after reinstalling the Design studio, the problem is solved for some time, but again same thing happens.

Please let me know if anyone have solution this.

#JFLASH#Debugging

Re: Unable to debug code in S32 design studio V3.4

Julián_AragónM — Wed, 25 Sep 2024 16:35:44 GMT

Hi @P007,

Could you share your debug configurations? Is this issue only present in your project? Or is it present on the examples as well, please test this.

Also, this post may be helpful: Eclipse GDB Launches - "No source available for "gdb[38].proc[42000].threadGroup[...)" " - Stack Overflow.

Best regards,
Julián

Re: Unable to debug code in S32 design studio V3.4

P007 — Tue, 01 Oct 2024 04:33:18 GMT

@Julián_AragónM

the issue is observed on both my code and example code

Configurations

Re: Unable to debug code in S32 design studio V3.4

Julián_AragónM — Wed, 02 Oct 2024 21:12:57 GMT

Hi @P007,

Are you able to connect to target without uploading an image?

If so, please try and stop the MCU to see if it is stuck somewhere in application.

Also, you could try to reset or erase the chip from the JLink flash tool (e.g. JFlash.exe or JFlashLite.exe, you can find it in the installation directory of Segger J-Link).

If these still do not work, please try another MCU or debug probe to see if the issue is within the hardware.

Best regards,
Julián