To increase functional and system reliability, the memories in many device modules and subsystems are protected by Error Correcting Code (ECC), which performs Single Error Correction (SEC) and Double Error Detection (DED). Detected errors are reported via ESM. Single bit errors are corrected, and double bit errors are detected. The ECC Aggregator is connected to these memory and interconnect components which have the ECC. The ECC aggregator provides access to control and monitor the ECC protected memories in a module or subsystem.
SDL provides support for ECC aggregator configuration. Each ECC aggregator instance can be independently configured through the same SDL API by passing a different instance. The safety manual also defines test-for-diagnostics for the various IPs with ECC/parity support. The SDL also provides the support for executing ECC aggregator self-tests, using the error injection feature of the ECC aggregator. The ECC aggregators should be configured at startup, after running BIST.
Features Supported
The SDL provides support for the ECC through:
- ECC Configuration API
- ECC self-test API
- ECC error injection API
- ECC static register readback API
- ECC error status APIs
There are over 40 ECC aggregators on the device each supporting multiple memories and interconnects.
SysConfig Features
Features NOT Supported
Important Usage Guidelines
There are two types of ECC aggregator RAM IDs supported on the device (wrapper and interconnect). The wrapper types are used for memories where local computations are performed for particular processing cores in the device, and the interconnect types are utilized for interconnect bus signals between cores or to/from peripherals.
For wrapper RAM ID types, after injecting an error, the memory associated with that RAM ID needs to be accessed in order to trigger the error interrupt event. It is the application's responsibility to trigger the error event through memory access after injecting the error.
Example Usage
The following shows an example of SDL ECC API usage by the application to set up the ECC to monitor for errors, as well as how to perform ECC self-test. The ESM should be configured to notify of the desired ECC events for the IPs. Please refer to the TRM for a list of the ESM events.
The following function is required to be defined by the application. It is used by the ECC module to notify the application in case of certain ECC errors that are reported through the R5F exception handlers. If it is not defined, it will result in a linker error. An example implementation is given below.
uint32_t errorSrc,
uint32_t address,
uint32_t ramId,
uint64_t bitErrorOffset,
uint32_t bitErrorGroup)
{
DebugP_log(
"\r\n ECC Error Call back function called : eccMemType %d, errorSrc 0x%x, " \
"address 0x%x, ramId %d, bitErrorOffset 0x%04x%04x, bitErrorGroup %d\n",
eccMemType, errorSrc, address, ramId, (uint32_t)(bitErrorOffset >> 32),
(uint32_t)(bitErrorOffset & 0x00000000FFFFFFFF), bitErrorGroup);
}
Certain ECC events on CPU memory are reported as Exception events. In this case, the ECC SDL provdes a set of exception handlers that can be used to enable the SDL ECC self-test functionality and for notification of the ECC errors. The following example shows how to set up the exception handlers to use the SDL ECC implementations, and also provide application-specific handlers that will be called by the SDL handlers after the handler checks for ECC errors:
{
.udefExptnHandlerArgs = ((void *)0u),
.swiExptnHandlerArgs = ((void *)0u),
.pabtExptnHandlerArgs = ((void *)0u),
.dabtExptnHandlerArgs = ((void *)0u),
.irqExptnHandlerArgs = ((void *)0u),
};
void ECC_Test_undefInstructionExptnCallback(void)
{
DebugP_log(
"\r\nUndefined Instruction exception\r\n");
}
void ECC_Test_swIntrExptnCallback(void)
{
DebugP_log(
"\r\nSoftware interrupt exception\r\n");
}
void ECC_Test_prefetchAbortExptnCallback(void)
{
}
void ECC_Test_dataAbortExptnCallback(void)
{
}
void ECC_Test_irqExptnCallback(void)
{
}
void ECC_Test_fiqExptnCallback(void)
{
}
void ECC_Test_exceptionInit(void)
{
{
.swiExptnCallback = ECC_Test_swIntrExptnCallback,
.pabtExptnCallback = ECC_Test_prefetchAbortExptnCallback,
.dabtExptnCallback = ECC_Test_dataAbortExptnCallback,
.irqExptnCallback = ECC_Test_irqExptnCallback,
.fiqExptnCallback = ECC_Test_fiqExptnCallback,
};
return;
}
To configure ECC for an instance and specified ram IDs:
static SDL_ECC_MemSubType ECC_Test_AGGR1_A0subMemTypeList[MAIN_AGGR1_AGGR1_MAX_MEM_SECTIONS] =
{
SDL_ECC_AGGR1_IAM64_MAIN_INFRA_CBASS_CBASS_MAIN_0_AM64_MAIN_INFRA_CBASS_CBASS_IK3VTM_N16FFC_MAIN_0_VBUSP_P2P_BRIDGE_IK3VTM_N16FFC_MAIN_0_VBUSP_BRIDGE_BUSECC_RAM_ID,
SDL_ECC_AGGR1_IAM64_MAIN_INFRA_CBASS_CBASS_MAIN_0_AM64_MAIN_INFRA_CBASS_CBASS_MAIN_SYSCLK0_4_CLK_EDC_CTRL_CBASS_INT_MAIN_SYSCLK0_4_BUSECC_RAM_ID,
};
{
.
numRams = MAIN_AGGR1_AGGR1_MAX_MEM_SECTIONS,
.pMemSubTypeList = &(ECC_Test_AGGR1_A0subMemTypeList[0]),
};
Initialization of ECC
int32_t ECC_Example_init (void)
{
int32_t retValue=0;
void *ptr = (void *)&arg;
SDL_ErrType_t result;
#if defined (R5F_CORE)
ECC_Test_exceptionInit();
DebugP_log(
"\r\nECC_Test_init: Exception init complete \r\n");
if (retValue == 0) {
result =
SDL_ECC_initMemory(SDL_ECC_AGGR1, SDL_ECC_AGGR1_IAM64_MAIN_INFRA_CBASS_CBASS_MAIN_0_AM64_MAIN_INFRA_CBASS_CBASS_IK3VTM_N16FFC_MAIN_0_VBUSP_P2P_BRIDGE_IK3VTM_N16FFC_MAIN_0_VBUSP_BRIDGE_BUSECC_RAM_ID);
if (result != SDL_PASS) {
DebugP_log(
"\r\nECC_Test_init: Error initializing Memory of R5FSS0 CORE0 ECC: result = %d\r\n", result);
retValue = -1;
} else {
DebugP_log(
"\r\nECC_Test_init: Initialize of R5FSS0 CORE0 ECC Memory is complete \r\n");
}
}
#endif
if (retValue == SDL_APP_TEST_PASS) {
result =
SDL_ESM_init(SDL_ESM_INST_MAIN_ESM0, &ECC_Test_esmInitConfig_MAIN, SDL_ESM_applicationCallbackFunction, ptr);
if (result != SDL_APP_TEST_PASS) {
DebugP_log(
"ECC_Example_init: Error initializing MAIN ESM: result = %d\n\n", result);
retValue = SDL_APP_TEST_FAILED;
} else {
DebugP_log(
"ECC_Example_init: Init MAIN ESM complete \n\n");
}
}
if (retValue == SDL_APP_TEST_PASS) {
result =
SDL_ESM_init(SDL_ESM_INST_MCU_ESM0, &ECC_Test_esmInitConfig_MCU, SDL_ESM_applicationCallbackFunction, ptr);
if (result != SDL_APP_TEST_PASS) {
DebugP_log(
"ECC_Example_init: Error initializing MCU ESM: result = %d\n\n", result);
retValue = SDL_APP_TEST_FAILED;
} else {
DebugP_log(
"ECC_Example_init: Init MCU ESM complete \n\n");
}
}
if (retValue == SDL_APP_TEST_PASS) {
result =
SDL_ECC_init(SDL_ECC_AGGR1, &ECC_Test_AGGR1A0ECCInitConfig);
if (result != SDL_APP_TEST_PASS) {
DebugP_log(
"SDTF_init: Error initializing M4F core ECC: result = %d\n\n", result);
retValue = SDL_APP_TEST_FAILED;
} else {
DebugP_log(
"\n\nSDTF_init: AGGR1 ECC Init complete \n\n");
}
}
return retValue;
}
Once the ECC is configured, then error notifications will come to the ESM module, and will activate the ESM-registered application callback. The application callback may want to retrive the error information in order to take some action based on the error, like clearing the ECC interrupts, logging the error information, or some other action:
To clear and acknowledge the ECC interrupt:
if (eccErrorInfo.injectBitErrCnt != 0)
{
}
else
{
}
Execute an ECC Self-Test for a specified ECC aggregator (memtype) and RAM Id (subtype):
Inject an error for a specified ECC aggregator (memtype) and RAM Id (subtype)
injectErrorConfig.pErrMem = (uint32_t *)(0u);
injectErrorConfig.flipBitMask = 0x5;
injectErrorConfig.chkGrp = 0x1;
subType = SDL_ECC_AGGR1_IAM64_MAIN_INFRA_CBASS_CBASS_MAIN_0_AM64_MAIN_INFRA_CBASS_CBASS_MAIN_SYSCLK0_4_CLK_EDC_CTRL_CBASS_INT_MAIN_SYSCLK0_4_BUSECC_RAM_ID;
subType,
&injectErrorConfig);
if (result != SDL_EFAIL ) {
DebugP_log(
"\r\n Error inject at pErrMem 0x%p EFAIL test failed",
injectErrorConfig.pErrMem);
retVal = -1;
} else {
testLocationValue = injectErrorConfig.pErrMem[0];
DebugP_log(
"\r\n Error inject at pErrMem 0x%p: EFAIL test complete",
injectErrorConfig.pErrMem);
}
return retVal;
Read the Static registers:
if (result != SDL_PASS) {
DebugP_log(
"\r\nECC_Test_init: Error reading the static registers: result = %d\n\n");
retValue = -1;
} else {
DebugP_log(
"\r\nECC_Test_init: M4F Memtype Register Readback successful \n\n");
}
API
APIs for SDL ECC (ECC_AGGR)