S32k312 SCST exception hardfault

[sungjun]

Hello? NXP Team.

I am applying SCST to S32K312 MCU.

The version I am using is the paid version.

I placed rom/ram in the guide document in the linker file, but when i run atomic test,

exception hardfault occurs.

where should i look? If there is a guide, please expain it.

below is the content of the t32, stack frame screen.

////////////////////////////////////////////////////////

Hardfault_Hander()

->exception

m7_scst_exception_mem_fault_test(asm)

->exception

C40_Ip_MainInterfaceSectorEraseStatus()

end of frame

///////////////////////////////////////////////////////

[Mirek_Franek]

Hello,
thank You for additional information.
When m7_scst_ISR_dispatcher is reached, please place breakpoint at label m7_scst_pass_control_to_alien_ISR, then run execution. Are You able to reach this label?

If Yes, what are the values stored in R1 and R3 registers?

If No, please step through ISR_Dispatcher and try to find instruction, after which Hardfault_Handler is reached.

Could You please also provide:
Which version of SCST are You using?
What compiler (Vendor / Version) are You using?

Thank You!
Best Regards

Mirek

[Mirek_Franek]

Hello,
m7_scst_exception_mem_fault_test intentionally triggers 2 exceptions for testing purposes.

1. Please go to label m7_scst_exception_mem_fault_test
2. Place breakpoint at label m7_scst_ISR_dispatcher
3. Run execution till breakpoint. Check exception ids:
 - 1st exception should be hardfault (exception id 3)
 - 2nd exception should be memManageFault (exception id 4)
   Please check that each exception is serviced by SCST ISR handlers m7_scst_exception_mem_fault_ISR0 or m7_scst_exception_mem_fault_ISR1.
4. No further exceptions should occur in this test.

Could You please describe how it behaves at Your side? Is m7_scst_ISR_dispatcher reached, exceptions triggered and served?
Thank You!

Best Regards

Mirek

[kjy106906]

Thank you

m7_scst_ISR_dispatcher is reached.

and 1st exception is 3, but instead of jumping to m7_scst_exception_mem_fault_ISR0, it jumps to the existing handler Hardfault_Handler().

Is there are any possible cause?