• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 31 subscribers
  • Views 403 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.

TMS570LC4357: CCM-R5F - CPU compare error flag

Alexander Dold
Prodigy 10 points
Part Number: TMS570LC4357

Hello together,

so we are currently running into the following problem:

After we activated the VIM Interrupt Source Channel 20, which is for ESM low-level Interrupts, we are running in the "CCM-R5F - CPU compare error" flag set, which than asserts according to the manual the "CCM-R5F - self-test" flag.

To find the source of the exception we started the system with the debugger connected and stepped through each line of code. One thing we found was that, if we start-up the system with the debugger connected and step through each line of code, the compare error flag does not signal a mismatch and the system works as expected. Only when the system starts running without the debugger interferring, the compare error flag shows up.

Does somebody know if there is a way to find out which compared output signal (Global signals, interrupt signals, L1 cache interface signals, ...) did fail or has another clue which might help?

Thanks in advance and best regards,

Alex

  • +1
    TI__Guru**** 197036 points

    Hi Alex,

    Did you perform the CCM self-test? 

    Please check the device errata: DEVICE#56 nERROR assertion on debugger connect

    DEVICE#56 nERROR assertion on debugger connect
    Severity: 4-Low
    Expected Behavior: No errors should be detected when connecting to the device by JTAG 
    Issue: Sometimes a CPU compare error (ESM Group 2 channel 2) is generated when the debugger connects to device.
    Condition: Upon a debugger initially connecting to the device.
    Implication(s): The nError pin will toggle upon initial connection with the debugger.
    Workaround(s): Clear the nERROR by writing 0x5 to the ESMEKR key register in the ESM module and ignore the nERROR pin toggle which happens immediately upon the debugger connecting.

  • 0 in reply to QJ Wang
    Prodigy 10 points

    Hi QJ,

    we set the CCMKEYR1...4 to 0x0 which sets the Active Compare Lockstep mode. So we did not set the Self-Test mode.

    We also initialized all core registers to a predefined state before any function call is made, according to the TMS570LC4357 manual. But I will recheck if the initialization is correct.

    Thanks in advance, I'll have a look at it.

    Best regards,

    Alex

  • 0
    Prodigy 10 points

    Hello QJ,

    thanks for your hint with the Errata DEVICE#56, it solved the problem.

    If we start the Software with the debugger, or leave it running without interferring in any way with the debugger it won't show up. The error only occurs when we attached the debugger, while the system is running, which is what DEVICE#56 mentions.

    Thanks,

    Alex