• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 31 subscribers
  • Views 439 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.

Reset and debug ETM pins

Jiri Janacek
Genius 3315 points


Dear all,

this thread has been submitted to complete the previous one - please may you comment the following questions?

Thanks a lot, cheers, Jiri

Well, you wrote that pin (09) RSTn can remain unconnected. Should I consider a link via the jumper JP9 1-2 to be connected with the system warm reset RST_ (ball B17 on 3137ZWT device)? What is your opinion?

I think that connection is not necesarry - the debug reset forced by nTRST (pin 21) is sufficient, is not? I mean that hard power reset nPORRST has a similar affect as warm reset in that case - a debug session is lost and the new one must be established, does not?

Yes, in "special" cases there is only way to get alive to unconnect the debugger probe and switch off the power line ;-)

  • 0
    TI__Mastermind 23000 points

    Hello Jiri,

    Regarding the different reset signals on the TMS570LS with respect to debug:

    • nTRST (JTAG reset) will only reset the JTAG state machine.  As the debug logic is ARM Coresight, it is not reset by the JTAG protocol reset
    • nPORRST will reset the entire device
    • nRST will reset the majority of the device, but not debug logic.  It is architecturally possible to maintain a debug session and use nRST to reset device but not debug/trace; most debuggers do not contain the recovery logic to implement this feature.
    • The ICEPICK advanced system reset (as named in CCS) allows the debugger to drive an nRST internally via debug commands.  This reset mechanism allows debugger awareness of the nRST such that recovery is easier.
    Regards,
    Karl