Hi Marco, I have added my comments after >>. 1) According to the TRM by the CCM self test, the match test, the mismatch test and the error forcing mode check the correct comparison of the signal from the 2 CPUs by pre-defined sequences. Can I verify by my own the correct working of the CCM by introducing (by code or by debugging) different output values to both the CPUs and looking at the status of the CCM? If yes, could you explain me please how ? >> It is sufficient to test the following aspects in the defined sequence: a) Check that a diagnostic feature's failure indication mechanism is working correctly. This is done via the CCM Self-Test Error Forcing mode. b) Run a self-test on the diagnostic feature's logic. This is done via the CCM Self-Test mode. c) Check that a mis-compare is actually signaled by the CCM. This is done via the CCM Error Forcing mode. Once all the above checks are passed, only then you can actually use the CCM to compare CPU outputs correctly. There is no other way to intentionally disturb / corrupt the CPU outputs to the CCM. It is possible that the two CPU's registers do not power up to the same value, in which case any operation that would cause the CPU to output a register value to memory could cause a real CCM compare error. However, this may not always work as the CPU registers could indeed power up to the same values. 2) When the debug is executed, only the registers (e.g. R0-R15) are displayed like only a CPU is there. Is there some mechanism to avoid the user to "hack" the MCU respect to the safety intended behavior (e.g. for parallel calculation or clustering) ? >> I do not understand the question. Can you please clarify? Regards, Sunil
↧