• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 434 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.

Original question:

TMS570LC4357: Erreta sheet "DEVICE#56"

TMS570LC4357: Erreta sheet "DEVICE#56"

Christopher TRITANT
Expert 1080 points
Part Number: TMS570LC4357

Hello,

Regarding the erreta sheet "DEVICE#56" in TMS570 LC4x (Revision B) errata sheets document (SPNZ232A (May 2016)), about nERROR assertion on debugger connect:

- Do you have more information about the frequency of appearance for this errata ? (at each debugger connection ?)

- Event if this is not a quantitative assessment, do you have an idea of probability for this errata (frequent, sometimes, rarely) ?

Best regards,

Christopher

  • 0
    Expert 1080 points

    hello,

    Could you provide us more information about our request ?

    Regards,

    Christopher

  • 0 in reply to Christopher TRITANT
    TI__Guru**** 196206 points
    Hello Christopher,

    If there is working code in flash, CPU starts execute the instructions and the CCM-R5F starts compare the output of the two cores upone the reset is released. The JTAG operations is to place the CPU in a halting debug state where the code execution is halted. Because halting debug events are asynchronous, there is a possibility for the debug requests to cause loss of lockstep. Based on my test, it happens frequently.

    If there is no code running while connecting JTAG debugger, their will be no error.