Hi Team,
For lock step exception handler, could see that we need to clear channel 31 group1 and channel 2 in group2.
Let me know if we need to handle further on this. Also, can you provide details on shadow status register details.
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hi Team,
For lock step exception handler, could see that we need to clear channel 31 group1 and channel 2 in group2.
Let me know if we need to handle further on this. Also, can you provide details on shadow status register details.
Hello,
In lock step mode, a CPU compare error asserts “CCM-R4F - compare” and “CCM-R4F self-test error” flags to the ESM. So both of them should be cleared.
To avoid an erroneous CCMR4F compare error, the application software needs to ensure that the CPU registers of both CPUs are initialized with the same values before the registers are used.
ESMSR2 is cleared after nRST. The shadow register (ESMSSR2) maintains the error flags until power-on reset (PORRST) is asserted. Because nRST clears the flags in ESM status register 2 (ESMSR2), the user has to read the shadow register to debug the failures after RST pin goes back to high.
Also, CCM-R4F self-test error happens only during self test and not during normal execution.
Hello,
1. ESMSSR2 is the shadow register. This register can maintain the error flags of group2 after nRST. The value of ESMSSR2 is only affected by nPORRST.
2. In lock-step mode, the inputs to the CCM compare logic are from CPI1 and CPU0, the difference in the output bus of compare logic may be caused by either 2 inputs or by the compare logic. This is why both “CCM-R4F self-test error” and “CCM-R4F -compare” are set.