SPC5748C SM issue list

[jiuyang_zhang]

1.In our design, we use a part of SMs(not all), we hope to calculate the real SPM and LFM, but we do not know the method to calculate the SPM/LFM results, pls tell me the details steps to update the results.

2.Pls summary the detail triger source of FCCU_EOUT, as we only find the internal failures(not detail)

3.If we excute all the safety-self-test, what is the each excute time and the total excute time? pls provide.

4.SM_305: could you pls explain the detail method compar for APP SW.

5.SM_316: what is the 'Address Decoder,? is the ram address check or register address check?

6.SM_225: what is the hardware lock? is the MCU have?and can our sw configure it or not?

7.For the FMEDA: which SM impact the each module`s SPM/LFM results, pls provide;  we just want to know which SM don't have to configure.

Pls answer ASAP, thanks in advance.

 

[aarul]

Hi

Please find replies below for each item above:

1. Please contact NXP FAE supporting you to get the FMEDA configured based on your application and safety mechanisms you are using.

2. Please refer to "FCCU non critical fault mapping table" in FCCU section in SPC5748C reference manual.

3. Please refer to SCST users manual for details regarding execution time.

4. SM_305 is about Reciprocal comparison. There are two independent cores and both the cores are running the application software and the results of those cores are exchanged and compared using software in each to core to detect the mismatch if any.

5. SM_316 is about running self-test and checking the results independently. The address decoder mechanism explained in the safety manual is a way to check this independently. The idea is that if the self-test result is incorrect then an access is made to an unpopulated address space which will trigger an illegal address trap.

6.SM_225 is Register protection module. It is hard lock for register and the function of hard lock is to prevent the modification of safety relevant configuration register during application execution.Yes, the software can configure it but once it is hard locked it cannot be cleared (Refer to description of REG_PROT_GCR in Reference Manual). It can only be cleared by a system reset. You can do a soft-lock if you want to reprogram again.

7. Same as 1 above.

Regards

-Aarul