• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 100 subscribers
  • Views 80 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

[FAQ] TDA4VH-Q1: ECC Testing Procedure for Inaccessible RAM IDs

Josiitaa RL
Mastermind 23985 points
Part Number: TDA4VH-Q1

Tool/software:

Does the SDL ECC test cover error injection tests on the inaccessible endpoints? If not, what is the testing procedure for these endpoints?

  • 0
    TI__Mastermind 23985 points

    Hi, 


    In the ecc_func_app present in SDL, to test the inaccessible RAM IDs, an error is injected by SDL, but since there is no direct way to access the memory, the error interrupt is forced by manipulating the ECC’s interrupt status registers. For information regarding the accessibility of the RAM ID, corresponding to specific ECC endpoints, you can refer to the sdlr_soc_ecc_aggr.h file in sdl/include/soc/$SOC/.

    This is done within the SDL_ecc_aggrSetEccRamIntrPending() API.

    However, in the real case scenario, you would not have to force the error on wrapper type endpoints and the application would have to perform a read access to trigger the interrupt as stated in the TRM.

    The following xls has the testing procedures to perform this memory access. Note that this is an initial version and is subject to changes. Currently we do not have test code or examples to perform this memory access. This is the responsibility of the system integrator. 

    j784s4_ecc_metadata_inaccessible_rams_v3.xlsx

    Regards,

    Josiitaa