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.

TDA4VM: ECC Aggregator Endpoint ID

Part Number: TDA4VM

Dear experts,

Our customer is looking into our ECC Aggregator details.

In TRM, we mentioned that we can input Endpoint ID to ECC_VECTOR.

But is there a table to mapping our IP to Endpoint ID? Also, which ECC Aggregator is connected to interconnect?

If you have any concern please drop me a mail. Thanks!

Thanks & Best Regards!

ZM

  • Hi ZM,

    Can you add more details on what exactly you are looking at?

    Best Regards,
    Keerthy

  • From this text in TRM, it mentioned the endpoint ID. But where is the definition of this ID?

    Second question, background is customer want to know our ECC coverage. TRM mentions that ECC aggregator may connect to interconnect. who is connecting and who is not? (could you please map it to table 12-17468)

  • MZ,

    Chapter 12 shows the breakdown of a typical ECC Aggregator instance and how the ECC wrapper and components registers can be used.  For actual programming, you have to use the ECC AGGR register instance corresponding to each device modules that has this feature available.  A complete list of modules with ECC Aggregator available is shown under Table 12-17469:  Device Modules and Subsystems with ECC Aggregator.

    For example, to program the ECC AGGR for Compute Cluster, you have to program COMPUTE_CLUSTER0_MSMC_ECC_AGGR0/1/2 with the endpoint (also referenced as RAM ID) mapping shown in Table 6-2, 6-3, 6-4 COMPUTE_CLUSTER0_MSMC_ECC_AGGR0/1/2 RAM ID Mapping, and Table 6-292. RAM ID Map for ECC Aggregator for mapping into R5F CPU0_VECTOR/CPU1_VECTOR registers.

    Note we have identified some missing ECC AGGR details and are working to resolve this for future TRM releases.

    Best Regards,

    Shiou Mei