Getting hardfault due to Clock_Ip_SetFlashWaitStates()

PratikY — Mon, 31 Jan 2022 14:25:11 GMT

I am using the S32K344EVB-Q257 board. I have developed an application for can Transit and it is working fine with FreeRTOS. But If I include Emios_Mcl_Ip_Init() or Emios_Pwm_Ip_InitChannel() API in application code. My firmware getting hard fault while calling Clock_Ip_SetFlashWaitStates() calls.

I am not able to understand why hard fault occurs before my newly added API call? @PetrS can you please help me to regarding it?

During debugging I have observe two issue

1) Clock_Ip_SetFlashWaitStatesCallback() address becomes zero

2) Fee_JobScheduleLookupTable, all entry becomes zero.

first hardfault occurs at point 1 , if I replace Clock_Ip_SetFlashWaitStatesCallback() code into Clock_Ip_FLASH_SetFlashIWS() hardfault fault occurs at 2nd point when Fee_JobSchedule() is called if I replace Fee_JobSchedule() with Fee_JobSystemDone() codewords fine as expected.

In debug console, I am getting the following error

UsageFault: An instruction executed with an invalid EPSR.T or EPSR.IT field.
HardFault: A fault has been escalated to a hard fault.

Re: Getting hardfault due to Clock_Ip_SetFlashWaitStates()

PratikY — Tue, 01 Feb 2022 05:06:41 GMT

Hello @PetrS , can you please help me regarding this issue?

S32 SDKのトピックRe: Getting hardfault due to Clock_Ip_SetFlashWaitStates()

Getting hardfault due to Clock_Ip_SetFlashWaitStates()

Re: Getting hardfault due to Clock_Ip_SetFlashWaitStates()