Hi,
I'm developing s32k312 these days, and a problem has confused me. The s32ds ide cannot trigger the interrupt(pit) when debugging, which I tried both jlink and pemicro, and their driver have both be updated to the latest. The interrupt cannot be triggered only in debugging, it works fine when burned into flash and boot and run automatically after POR.
I thought this problem due to my project, so I created a PIT example project from the sdk, but it behaved the same as my project, PIT interrupt cannot be triggered when debugging.
Anybody has met the same problem as mine? Please share the experience with me. Thanks!
解決済! 解決策の投稿を見る。
here you can see it works fine on myside.
the test hardware is S32K312EVB-Q172
the test software is RTD 2.0.2
the debugger is J-link and OpenSDA, both works fine on myside.
Hi@jhuang1
I tested the interrupt function of PIT on S32K344 (this should be the same as S32K312), it works as expected on my side.
two investigation directions
1. Is it possible to change a debugger and test again
https://community.nxp.com/t5/MPC5xxx/stuck-in-OSIF-TimeDelay/m-p/1354830
2. the setting of compilation optimization level
Hi Senlent,
I have tested the program on s32k344,and it worked ok. The s32k312 is on my new board. I tested the second action, setting the optimization level to the other levels, but it still work unnormaly. Occasionally the interrupt can hit the break point, no interrupt triggering mostly.
here you can see it works fine on myside.
the test hardware is S32K312EVB-Q172
the test software is RTD 2.0.2
the debugger is J-link and OpenSDA, both works fine on myside.
Hi Senlent,
The RTD I tested in last program is 2.0.0, and I changed it to 3.0.0 now, the pit interrupt can be triggered finally. I would test RTD 2.0.2 these days, it seems RTD 3.0.0 has changed a lot relative to 2.0.0.
Thanks for your advise!
Thanks for your feedback, I will reproduce the issue on my side.
I'll get back to you next Monday, I'm out of the office right now.