S32KのトピックRe: s32k312 debug for sds3.5

s32k312 debug for sds3.5

fengba_360 — Mon, 26 Aug 2024 03:10:36 GMT

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.

Re: s32k312 debug for sds3.5

fengba_360 — Mon, 26 Aug 2024 15:20:08 GMT

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?？

Re: s32k312 debug for sds3.5

Julián_AragónM — Tue, 27 Aug 2024 18:29:52 GMT

Hi @fengba_360,

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

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:

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

Best regards,
Julián

Re: s32k312 debug for sds3.5

fengba_360 — Wed, 28 Aug 2024 00:51:49 GMT

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

Re: s32k312 debug for sds3.5

Julián_AragónM — Thu, 29 Aug 2024 14:11:19 GMT

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