topic Re: NXP S32k312 debugger connection issue after adding Image Vector Table Marker in S32K

NXP S32k312 debugger connection issue after adding Image Vector Table Marker

dextervictoria — Tue, 27 Aug 2024 09:24:36 GMT

Hi,

I'm using S32k312 (100 pin)which is working perfect with debugger. I need to add Image Vector Table at location 0x400000 for working without debugger. When I add this change, software run fine without debugger but when connected back to debugger, breakpoints are not hitting in initial code start areas like startup code, main function etc (program continuously running).

What will be the reason for this?

Thanks and regards
Dexter.

Re: NXP S32k312 debugger connection issue after adding Image Vector Table Marker

danielmartynek — Wed, 28 Aug 2024 07:47:14 GMT

Hi Dexter,

The SBAF searches for a valid IVT at these addresses only:

What debugger do you use?

Regards,

Daniel

Re: NXP S32k312 debugger connection issue after adding Image Vector Table Marker

dextervictoria — Thu, 29 Aug 2024 06:18:17 GMT

Hi Daniel,
I placed IVT at 0x400000 address. I'm using isystem debugger. Also tested in Lauterbach; shows same behaviour.
Breakpoints at initial functions like boardstart, main, other init functions are not recognised. But break points are recognised from cyclic os tasks.

Regards,
Dexter.

Re: NXP S32k312 debugger connection issue after adding Image Vector Table Marker

danielmartynek — Fri, 30 Aug 2024 12:10:58 GMT

Hi @dextervictoria,

I understand you are attaching the debugger while the MCU is already running, that mean after the startup code.

With Lauterbach, you can use a script like this:

SYStem.CPU S32K312
wait state.power()
SYStem.Mode Attach
Break

This should wait while the MCU is not powered, and attach/break once the MCU is powered.

Regards,

Daniel