topic Re: When debugging S32K312, the interrupt callback function of PIT cannot be entered in S32K

When debugging S32K312, the interrupt callback function of PIT cannot be entered

猫和老鼠 — Thu, 11 Sep 2025 02:14:07 GMT

S32K312 uses RTD version 4.0. When debugging, the interrupt callback function of PIT cannot be entered. When not debugging, the interrupt can be entered normally.

The following is my configuration information and code:

Re: When debugging S32K312, the interrupt callback function of PIT cannot be entered

petervlna — Thu, 11 Sep 2025 07:17:05 GMT

Hello,

S32K312 uses RTD version 4.0. When debugging, the interrupt callback function of PIT cannot be entered. When not debugging, the interrupt can be entered normally.

Hello, have in mind that debugger often run some counters on background. So if you have multiple interrupts configured it is possible that some will preempt the PIT one.

It looks like simple synchronization issue in debug mode.

Set the PIT to highest priority interrupt and test it.

Best regards,

Peter

Re: When debugging S32K312, the interrupt callback function of PIT cannot be entered

猫和老鼠 — Thu, 11 Sep 2025 08:54:28 GMT

It shouldn't be this reason, the interrupt priority of the pit is already the highest, I am considering whether it is a problem with the jlink debugger.

Re: When debugging S32K312, the interrupt callback function of PIT cannot be entered

petervlna — Fri, 12 Sep 2025 07:30:41 GMT

Hello,

Nah. this is typical behavior when debugger is connected. I would not suspect debugger itself.

You are out of synchronization with counters, etc... in debug mode unless they directly support debug mode run.

Disable all interrupts except PIT. Wait for PIT to set TIF flag and the step in debug. You will enter the ISR.

Best regards,

Peter

Re: When debugging S32K312, the interrupt callback function of PIT cannot be entered

猫和老鼠 — Tue, 16 Sep 2025 02:09:05 GMT

In debug mode, the data in the register is like this, there is no data in the register, I don't know what's going on. Could you please take a look.

Re: When debugging S32K312, the interrupt callback function of PIT cannot be entered

猫和老鼠 — Tue, 16 Sep 2025 02:24:12 GMT

Currently, all interrupt callback functions used in debug mode cannot enter

Re: When debugging S32K312, the interrupt callback function of PIT cannot be entered

猫和老鼠 — Tue, 16 Sep 2025 02:56:05 GMT

In debug mode, the TIE of PIT-0 has always been 0, and the CVAL register has been decrementing several times.

Re: When debugging S32K312, the interrupt callback function of PIT cannot be entered

petervlna — Tue, 16 Sep 2025 06:40:32 GMT

Hello,

Ok, and is your TIF flag set after counter reach modulo?

This is simple HW comparator so it must be set in case you reach modulo. And if the interrupt is enabled it will be called.

Best regards,

Peter

Re: When debugging S32K312, the interrupt callback function of PIT cannot be entered

猫和老鼠 — Tue, 16 Sep 2025 07:07:12 GMT

I know that I also enabled interrupts, but in the debug mode, I can't access interrupts, but I can access interrupts without connecting the debugger. So do I need to configure some registers to ensure that interrupts can also enter the debug mode normally?

Re: When debugging S32K312, the interrupt callback function of PIT cannot be entered

petervlna — Wed, 17 Sep 2025 04:58:53 GMT

Hello,

Hmm so from uC point the ISR is working properly.

Only in the debug mode you have issues.

Did you try to set breakpoint to ISR and run the code from reset Did it reach the ISR?

For any setting withing debugger please contact debugger vendor, maybe there is something. But I have personally never encounter such issues on multiple debuggers.

This whole issue seems strange. Please share with me code which demonstrate the issue.

Best regards,

Peter

Re: When debugging S32K312, the interrupt callback function of PIT cannot be entered

猫和老鼠 — Wed, 17 Sep 2025 06:12:41 GMT

This is my project.Please try it.

Re: When debugging S32K312, the interrupt callback function of PIT cannot be entered

猫和老鼠 — Wed, 17 Sep 2025 06:13:18 GMT

Re: When debugging S32K312, the interrupt callback function of PIT cannot be entered

petervlna — Thu, 18 Sep 2025 07:43:54 GMT

Hello,

I have just tested your code.

PIT_0_ISR was entered and stopped at breakpoint in debug immediately after TIF for Timer 0 was set.

I see no issue in the code. If I step trough the code, or run it it will end up in ISR.

Best regards,

Peter

Re: When debugging S32K312, the interrupt callback function of PIT cannot be entered

猫和老鼠 — Thu, 18 Sep 2025 09:13:55 GMT

OK, I have solved this problem. It is faulty soldering of the chip. Thank you very much.