• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 32 subscribers
  • Views 1885 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.

CCM CPU compare error when connecting debugger - TMS570LC4357

Piotr Roszak
Intellectual 530 points

Other Parts Discussed in Thread: TMS570LC4357, HALCOGEN

Hello,

Whenever I connect debugger to TMS570LC4357, I get 'CCM-R5F - CPU compare error' (ESM: group 2 channel 2).

What should I do to make debugger connection not disturbing for the CCM module?

Thanks,
Piotr

  • 0
    TI__Guru 72500 points
    Do you have code in the device? If so, is the code clearing each of the registers. The R5 CPU registers power up as random values. If the two cores use a register (such as pushing the LR to the stack) before the registers are initialized, you will get that core compare error. The startup code from HALCoGen will initialize all of the CPU registers.
  • 0 in reply to Bob Crosby
    Intellectual 530 points

    R5 CPU registers are initialized correctly.

    When debugger is not connected, the issue does not exist. CPU compare error occurs when I connect debugger to the working target (connecting only, without flashing).

    Thanks,
    Piotr

  • 0 in reply to Piotr Roszak
    Intellectual 530 points

    Steps to reproduce this issue:

    1. run any application on TMS570LC4357
    2. physically connect JTAG emulator (e.g. XDS200)
    3. launch debugger session in Code Composer Studio
    4. connect TMS570 by clicking 'Connect Target'

    After step 4. nError pin goes low (indicating error condition) and ESM group 2 channel 2 error is signalled, which is CCM error.

    Thanks for your help,
    Piotr

  • 0 in reply to Piotr Roszak
    TI__Guru 69070 points

    There should be an errata on the R5 explaining that there is an initial (false) CCM-R5 error generated the first time that you connect JTAG.
    But I cannot find it in the errata that I have linked...

    Anyway if you clear this ESM flag and then it doesn't come back when you connect / disconnect (without doing power cycle or power on reset) then I think you're just seeing the known silicon issue.

    EDIT: See errata Device #56 ...

  • 0 in reply to Anthony F. Seely
    Intellectual 530 points

    Thank you, it is exactly the behaviour I noticed. 

    To work around this silicon issue I need to check on the microcontroller if the debugger is connected or not. Could you provide me with information what is the best way to check it?

    Thanks,
    Piotr