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.
/* Test the CPU ECC mechanism for RAM accesses.
* The checkBxRAMECC functions cause deliberate single-bit and double-bit errors in TCRAM accesses
* by corrupting 1 or 2 bits in the ECC. Reading from the TCRAM location with a 2-bit error
* in the ECC causes a data abort exception. The data abort handler is written to look for
* deliberately caused exception and to return the code execution to the instruction
* following the one that caused the abort.
*/
checkRAMECC();
The value of uninitialized variable is indeterminate. The CRC of those variables on the RAM is not a good solution because the content of those variables will be changing dynamically. So you don't really know the golden signature to compare with.
If the const global variables is linked to a specified data section (please refer to #pragma DATA_SECTION), you can calculate the CRC of this section in RAM.
