S32K312 sCheck to open the ECC test, run the sCheck_CortexM7_ErrRead function to enter the hardfault

[Yongxingjia]

S32K312 sCheck to open the ECC test, run the sCheck_CortexM7_ErrRead function to enter the hardfault.

According to the description in the S32K3_SAF_SCHECK_UM.pdf, the ramcode_no_cacheable segment has been placed in the Ram region, but the assignment of a local variable in the sCheck_CortexM7_ErrRead function will trigger a Hardfault. This address has been configured in the MPU to execute code, what is the possible reason here?

Before running uint64 result=0ULL；

After running uint64 result=0ULL

Is there any way to troubleshoot this problem？

S32K3 SAF 

[danielmartynek]

Hi @Yongxingjia,

What is the address of the result variable?

What do you see in the MMAR register? (MMARVALID = 1)

It detects a fault exception on a write, not code execution.

I see several regions overlapping, is it intended?

Did you enable sub-regions in that regions.

Also, the base address of a region should be aligned to the size of the region. For example, a 64KB region must be aligned on a multiple of 64KB, for example, at 0x00010000 or 0x00020000. I don't see that in your MPU configuration.

https://developer.arm.com/documentation/dui0646/c/Cortex-M7-Peripherals/Optional-Memory-Protection-U...

Regards,

Daniel

[Yongxingjia]

Hello,Daniel:

I configured it with reference to the demo of the S32K344，and the demo also overlapping it.

Now I've also modified the configuration of the MPU, but I'm getting a new problem

When "204102c2: str r2, [r0, #0]"is executed in the sCheck_CortexM7_ErrRead function, the vector table is relocated to the 0x20410480, 0x20410480 the storage is the 0xBF00BF00

When 204102fe: ldrd r0, r1, [r1] is executed in the sCheck_CortexM7_ErrRead function, the code executes exceptionally

What are the precautions about ECC in the sCheck integration, ECC-related testing and debugging have been for a long time, and there has been no progress, and the user manual is not very clear, or can you provide a S32K312 Demo project for reference, thank you!

[RadoslavB]

Hello @Yongxingjia ,

please could you:
- specify which sCheck test exactly causing this issue?
- find out the address for these symbols: "sys_stack_init", "sys_vec_0"
- which compiler are you using?

Kind Regards,
Radoslav