Hi NXP,
I have a question regarding NXP S32G274, for the SRAM ECC.
According to S32G2 Reference Manual, Section 35.2.2 Features (for SRAM Controller), the SRAMC features include:
According to S32G2 Safety Manual, Section 1.4.6.2 SRAM monitoring requirements:
But according to S32G2 Safety Manual "Addendum_S32G2.xlsx", Assumption "27102":
"The application software periodically—at least once per drive cycle—checks all the ERM module's ECC correctable error counters and reacts as follows:
- If a counter is 0, does nothing.
- If a counter is greater than or equal to 1, where possible within the application and memory location, corrects the memory location by performing a read, writes back the read data, and then reads the memory location again. The application software then checks that the counter value shows that the error was corrected, and then resets the counter by writing all zeros."
My understanding is that SRAM Controller will perform ECC (SECDED) automatically per SRAM word (64-bit data, 29-bit address, 8-bit CRC). Therefore, any ECC single bit error should be corrected automatically. But the assumption "27102" suggests that application SW is responsible to trigger ECC single-bit error corrections.
Which is correct?
Kind Regards, Manny.
Hi,
Please find response for your query:
The application SW is responsible to trigger ECC SED/DED notification. The assumption states that application SW shall check the ECC SEC functionality periodically atleast once per driving cycle. The ECC SEC/DED errors are reported in ERM module (Error reporting module), The ECC correction will happen but whether it should be notified via interrupt is configured in ERM.
The ECC will do automatically SEC correction and DED detection but it won't be notified if interrupts are disabled in ERM registers.
Please check Chapter 65 Error Reporting Module (ERM) section 65.3.1 and 65.3.1 in S32G2 Reference Manual, Rev. 2
Hope it helps!
Best regards,
Bhavik
Hi, thanks for your reply. I have just downloaded the latest S32G Reference Manual (Rev5). Could you identify the section in this latest revision to refer to for further information regarding application SW responsibility regarding ECC SECDED. Thanks.
Hi,
The assumption does not ask to "trigger" ECC correction, instead it just requires you to monitor number of ECC corrections. Based on which application software can decide to take the next action (or do nothing).
Regards,
NaveenM