• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 29 subscribers
  • Views 334 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: Erreta sheet "DEVICE#56"

Christopher TRITANT
Expert 1080 points
Part Number: TMS570LC4357

Good morning,

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

Could you tell us more information about the meaning of "debugger connect" ? Does it mean physical connection with debugger ?  Does it mean logical connection with debugger ?

Could you tell us more information about the conditions of this errata sheet "Upon a debugger initially connecting to the device" ?

Could you tell us more information about the implications of this errata sheet "The nError pin will toggle" (comapred to Errata title "nERROR assertion") ?
- Is the nError pin change of state is permanent or is it just a pulse ?
- Is it a change of state on the nError pin (active state to passive state or passive state to active state) or only a change of state to the active state ?
- Is this change of state on the nError pin appear once (upon initial connection with the debugger) or untimely (once connected with the debugger)?

Best regards,

Christopher

  • 0
    TI__Mastermind 49120 points
    Hi Christopher,

    A "debugger connection" means that the debugger is able to halt the processor, so it is a physical connection from an external JTAG-based debugger tool, which scans in a JTAG instruction sequence to halt the CPU.

    - Is the nError pin change of state is permanent or is it just a pulse ?

    The nERROR pin is driven low for a duration defined by the nERROR Low-Time Count (LTC) field of the ESMLTCR register. The application needs to clear the nERROR assertion by writing 0x5 to the ESM Key Register else the nERROR pin will get driven low again as soon as the LTC count expires.

    - Is it a change of state on the nError pin (active state to passive state or passive state to active state) or only a change of state to the active state ?

    Yes, the nERROR pin will get driven low.

    - Is this change of state on the nError pin appear once (upon initial connection with the debugger) or untimely (once connected with the debugger)?

    The wrong assertion of the nERROR pin is only seen upon first connection of the debugger (halting of the CPU).

    Regards,
    Sunil