Part Number: TMS570LC4357
Hi experts,
the Safety Manual suggest testing Parity, ECC and protection mechanisms of the various IP of the TMS570LC4357. The problem I am facing is that the I am not certain which Test lead to an Abort and thus to an exception.
For example the Diagnostic IOM5A suggest checking the error trapping of the IOMM.
(Q1) If I understand correctly writing to an umimplemented Adresses should signal an error in IOMM-Registers and ESM 1.37 (if enabled) and not an exception, since table 2-2 of the Technical Reference Manual does not list a abort as reaction?
The ECC and Parity tests, e.g. RAM13 and RAM12 lead to Errors signaled to ESM 2.7 and 3.15, which leads to the SW needing to reset ESM and nERROR (and RAMERR bits) after the tests.
The problem I am now facing is, that the Technical Reference Manual lists Parity and ECC Errors as conditions generating an abort. But the test descriptions themselves do not mention having to deal with exceptions.
If this would throw an exception, it would mean that running this test periodicly would leave our SW with fatal error event the first time the Test is run after startup tests, since we treat exceptions as fatal events.
(Q2) So does injecting faults into ECC and Parity lead to an exception or is this refering to specific ECC and Paritys? If so, which ones?
Thank you and best regards,
Max Wittekind
