Unable to debug code in S32 design studio V3.4

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Unable to debug code in S32 design studio V3.4

240 Views
P007
Contributor II

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]"DisassemblyDisassembly

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.

S32DS-S32PLATFORM S32K146EVB #JFLASH#Debugging

Tags (1)
0 Kudos
Reply
3 Replies

181 Views
Julián_AragónM
NXP TechSupport
NXP TechSupport

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.

Julin_AragnM_0-1727282054173.pngJulin_AragnM_1-1727282057939.png

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

Best regards,
Julián

0 Kudos
Reply

121 Views
P007
Contributor II

@Julián_AragónM 

the issue is observed on both my code and example code

Configurations

P007_0-1727757095617.png

P007_1-1727757113982.png

 

 

0 Kudos
Reply

83 Views
Julián_AragónM
NXP TechSupport
NXP TechSupport

Hi @P007,

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

Julin_AragnM_0-1727903474648.png

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

 

0 Kudos
Reply