s32k312 debug for sds3.5

[fengba_360]

When you encounter the error "No source available for "__interrupts_ram_start() at 0x2000035a"" while debugging an S32K312 MCU using SDS3.5, it typically indicates that the debugger is unable to locate the source code for a specific function or entry point that is being executed. In this case, __interrupts_ram_start() is likely a function or a section of code that is automatically generated or defined by the linker script or startup code for your project.微信图片_20240826104208.png

[fengba_360]

When I disable the pre-run/reset option in the debug settings, I can enter the simulation debugging normally. However, I didn't encounter this issue when using s32ds2.2 to develop for s32k144. Could you please explain why this kind of issue arises when using s32ds3.5 to develop for s32k312?？微信图片_20240826231426.png

[Julián_AragónM]

Hi @fengba_360,

I can see you have the "Skip All Breakpoints" option enabled, could you try debugging while this option is disabled? 

Julin_AragnM_0-1724783304490.png

This issue may be caused by the debugger not being able to enter the first breakpoint at main, since the pre-run/restart option only issues a reset and halt to the MCU after flashing the project:

Julin_AragnM_1-1724783311504.png

If this issue keeps happening, you can also try to contact the SEGGER - Forum directly.

Best regards,
Julián

[fengba_360]

If I enable breakpoint debugging, I am unable to simulate as well. I can only proceed by disabling the pre-run/reset option.

[Julián_AragónM]

Hi @fengba_360,

Is there a reason you need to enable the pre-run/reset option? Since it is not needed for normal debugging operation, and it does not work with your current project, is there a reason you need to enable it? 

Best regards,
Julián