Hi, I transported the SAF v1.0.2 to a s32k312 project, it run to 0xdeadbeee address when running sCheck at start-up. It run to the illegal address after writing register DCMRWP3 in the function sCheck_CmuFc_TestRestore(), as showed in the attached picture.
1. The variable pDesc->intId is 211 at this time, but it should be no interrupt at index 211 on s32k312, why the SAF still check this interrupt id;
2. Why the writing to DCMRWP3 would generate a fault? This register should be writable according to the datasheet;
Hello,
Could you please specify if you are using privileged mode of core when you are accessing the DCMRWP3 register?
Other then that there should be no issue for accessing DCMRWP3 register.
Best regards,
Peter
Hello,
You can check Privileged mode via CPU CONTROL register (bit 0):
If user app is in User mode, customer is responsible to switch into Thread Privileged mode before sCheck tests.
Anyway, for the issue there was a bug in sCheck SAF K3 1.0.2.
If customer application is in in-field Life cycle, the restore register's part was failing:
[ASFT-8962] [sCheck] S32K3xx CMU_FC test causes reset when device in in-field life cycle - NXP JIRA
Please check which life cycle mode you are in via DCMLCC register:
If this is the cause, I recommend to use SAF K3 1.0.4 where the issue has been fixed.
Kind Regards,
Radoslav
No, we don't have S32DS demo released at the moment, we need to decide if we will support so many K3 derivatives with demo examples for each or just some, then we might have some time for preparing S32DS example as well.
Kind Regards,
Radoslav