topic Re: Systick interrupt causes HardFault in S32K

Systick interrupt causes HardFault

davithakobyan — Wed, 06 Feb 2019 12:22:05 GMT

Hi,

I face a HardFault problem when using the LIN master example together with initializing Systick interrupt.

To reproduce the problem one should simply create a LIN master project from the examples using S32 Design Studio for S32K144EVB-Q100 board. Once the project is create initialize Systick like in the figure below:

So basically the program does nothing except initializing the system and systick clocks (although the problem may persist even without system clock initialization), however, when debugging the program ends up in the HardFault and the SysTick_Handler is never called. The HardFault seems to be triggered when it is time for Systick interrupt to appear.

Changing slightly some irrelevant code may make the program again work (i.e. triggerint Systick interrupt), which points rather to RAM corruption.

Can NXP team confirm this?

Thanks a lot.

Re: Systick interrupt causes HardFault

danielmartynek — Wed, 06 Feb 2019 15:44:58 GMT

Hi,

I have tried to reproduce the hardfault following your description with SDK v2.9.2, but it triggers the SysTick interrupt as expected.

Which SDK version do you use?

Thanks,

Daniel

Re: Systick interrupt causes HardFault

davithakobyan — Fri, 08 Feb 2019 06:40:23 GMT

Thank you for your comment.

I have SDK BETA 2.9.2 version.

Unfortunately, on the next day I could also not reproduce the behavior.

Close the issue for now.