• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 30 subscribers
  • Views 455 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.

CCS/TMS570LS3137: Debugging Issue

Andy Bolanos
Prodigy 40 points
Part Number: TMS570LS3137

Tool/software: Code Composer Studio

Hello,

I'm working in verification project, the code I'm verifying has to run a function if a VIM Vector Table Parity Error occur. Right now I'm using the CCS to create an Interrupt Vector Table Parity. First, I change the value of the PARCTL to disable the VIM parity, then I change the values of the VIM Interrupt table starting in the direction 0xFFF82000 and last I change the PARCTL to enable the VIM parity. The issue is that is only working for the first direction if I change the value of any of the other direction the microcontroller is not detecting the parity error.

I would like to know if it a problem because of the CCS or the microcontroller, or maybe the code.

Thanks.

  • 0
    TI__Guru 59540 points
    Hi Andy,

    After you have created the first parity error, did you go through the steps needed to clear the error completely as outlined in the TRM? Once the parity error is latched it will not trigger a second time until the parity error is serviced and cleared.
  • 0 in reply to Chuck Davenport
    Prodigy 40 points

    Hi Chuck,

    Yes, the error is cleared completely. Working in the last hours I found out other memory address that triggers the error. So I was wondering if parity is only checked when the interrupt is hit?

  • 0 in reply to Andy Bolanos
    TI__Guru 59540 points
    For sure, the parity error will only occur when the vector is used/taken. Until then it would be classified as a safe fault under IEC61508 and ISO26262 because, although the fault is present, it is not causing any harm to the system operation.