Part Number: TDA4VL-Q1
What is the effort required by the system integrator to enable and test ECC on the different IPs on the SoC using ECC aggregators?
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.
Part Number: TDA4VL-Q1
What is the effort required by the system integrator to enable and test ECC on the different IPs on the SoC using ECC aggregators?
Hi,
Please refer to the table below for details on how each ECC endpoint can be tested using ECC aggregators -
| ECC Type | Inject Type | Accessible Mem | Checker Type | Single bit injection possible? | Test Procedure | Double bits injection possible? | Test Procedure |
|
ECC Wrapper
|
Inject only | NO | N/A | Yes | SDL APIs can be used only for error injection. Error detection and correction is a part of the IP itself. | Yes | SDL APIs can be used only for error injection. Error detection and correction is a part of the IP itself. |
| Inject with error capture | YES | N/A | Yes | SDL APIs can be used, memory access also a part of the SDL ecc_func_app in sdl/test | Yes | SDL APIs can be used, memory access also a part of the SDL ecc_func_app in sdl/test | |
| Inject with error capture | NO | N/A | Yes |
SDL APIs can be used only to inject error Details on memory access to trigger error available in - [FAQ] TDA4VL-Q1: ECC Testing Procedure for Inaccessible RAM IDs and [FAQ] TDA4VH-Q1: ECC Testing Procedure for Inaccessible RAM IDs |
Yes |
SDL APIs can be used only to inject error Details on memory access to trigger error available in - [FAQ] TDA4VL-Q1: ECC Testing Procedure for Inaccessible RAM IDs and [FAQ] TDA4VH-Q1: ECC Testing Procedure for Inaccessible RAM IDs |
|
|
EDC Interconnect
|
Inject with error capture
|
NO
|
Redundant | Yes | SDL APIs can be used, no memory access required. Refer ecc_func_app in sdl/test | No | N/A |
| Parity | Yes | SDL APIs can be used, no memory access required. Refer ecc_func_app in sdl/test | No | N/A | |||
| Error Detect and Correct | Yes | SDL APIs can be used, no memory access required. Refer ecc_func_app in sdl/test | Yes | SDL APIs can be used, no memory access required. Refer ecc_func_app in sdl/test | |||
| YES | Redundant | Yes | SDL APIs can be used, no memory access required. Refer ecc_func_app in sdl/test | No | N/A | ||
| Parity | Yes | SDL APIs can be used, no memory access required. Refer ecc_func_app in sdl/test | No | N/A | |||
| Error Detect and Correct | Yes | SDL APIs can be used, no memory access required. Refer ecc_func_app in sdl/test | Yes | SDL APIs can be used, no memory access required. Refer ecc_func_app in sdl/test |
For details on the meaning and types of ECC endpoints, please refer - [FAQ] TDA4VM: Types of ECC Aggregators, RAM IDs and Error Injection
Regards,
Josiitaa