• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 98 subscribers
  • Views 198 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

AM263P4-Q1: ESM TPCC events

Carwyn Griffiths
Prodigy 90 points

Part Number: AM263P4-Q1

Hi, can you clarify the use of the two TPCC parity events of the ESM module.

  • ESM_LVL_EVENT_63 tpcc_a_err_intagg
  • ESM_PLS_EVENT_4 TPCC_errint

Using the ECC parity example code as guidance I'm able to setup and inject faults for tpcc_a_err_intagg succesfully.

I'm unable to find any details on TPCC_errint in the TRM. I'm enabling the event as shown in example code but occasionally get false errors reported during startup. Can you clarify how this event is triggered and how it differs from the tpcc_a_err_intagg event.

Thanks

Carwyn

 

  • 0
    TI__Guru* 79886 points

    Hi Carwyn,

    Apologies for the delayed response!

    I am already on top of this issue and discussing internally.

    I will provide my updates soon.

    --
    Thanks & regards,
    Jagadish.

  • 0 in reply to jagadish gundavarapu
    TI__Guru* 79886 points

    Hi Carwyn,

    Apologies for the delayed response!

    Parity Error: Raises only ESM_LVL_EVENT_63 tpcc_a_err_intagg Interrupt

    Access Error: Raises both ESM_LVL_EVENT_63 tpcc_a_err_intagg and ESM_PLS_EVENT_4 TPCC_errint

    --
    Thanks & regards,
    Jagadish.

  • 0 in reply to jagadish gundavarapu
    Prodigy 90 points

    Hi Jagadish,

    Thanks for the reply, that explains what we're seeing. We have disabled ESM_PLS_EVENT_4 due to the error reporting and started seeing ESM_LVL_EVENT_63 being reported, so suggests we are seeing the Access Error.

    Can you provide more details of what triggers an Access Error (it isn't clear from the TRM) and whether any initialisation steps are required before enabling the ESM module to prevent false errors being reported.

    Thanks,

    Carwyn

  • 0 in reply to Carwyn Griffiths
    TI__Guru* 79886 points

    Hi Carwyn,

    Could you try this?

    Configure Param 0 corresponding to EVT 0 with ACNT=0x0, BCNT=0x0, and CCNT=0x0 (other param fields can be configured as required) to generate a null event leading to TPCC error.

    After this try to trigger DMA transfer that should generate access error.

    --
    Thanks & regards,
    Jagadish.

  • 0 in reply to jagadish gundavarapu
    Prodigy 90 points

    Hi Jagadish,

    Apologies for the delayed response.

    I've carried out the above test with setting the CNT values to 0 during initialisation and this does trigger the fault. 

    Is this the only cause of the access error? If so, then it looks likely that the initialisation order between DMA and ESM modules may be the root cause of the issue in our software. Is there a recommended initialisation routine that should be followed?

    Thanks,

    Carwyn

  • 0 in reply to Carwyn Griffiths
    TI__Guru* 79886 points

    Hi Carwyn,

    Apologies for the delayed response:

    Additional causes of access error:

    Besides zero count values, TPCC Access Errors can be triggered by:

    • Invalid memory addresses in SRC/DST fields
    • Protection violations (accessing restricted memory regions)
    • Alignment errors (misaligned addresses for the transfer size)
    • Invalid channel/PaRAM set access
    • Triggering uninitialized DMA channels

    Best Practices:

    1. Always initialize DMA before ESM in your startup sequence
    2. Initialize all PaRAM sets (even unused ones) to safe default values
    3. Clear error status registers before enabling ESM monitoring

    --
    Thanks & regards,
    Jagadish.