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

TMS570LS0714: nERROR PIN

kyle lobo
Prodigy 60 points
Part Number: TMS570LS0714

Hi, 

I am using this part and would like to know some implementations for how to use this error pin. Is there a suggested implementation for resetting the processor by connecting this pin to the nPORRST? Unfortunately, when I make this connection, the part gets stuck in reset. 

  • 0
    TI__Guru**** 196666 points
    Hello Kyle,

    I don't recommend to connect nERROR pin to nPORRST. The TMS570 provides a possibility for CPU to trigger the nERROR pin response manually to test the system behavior or to notify external logic of an internal fault not automatically indicated to ESM. If the nERROR pin is connected to nPORRST pin, the diagnostic selftest will restart the device during the startup.

    System level management of the external error response can be simplified through the use of a TI TPS6538x power supply.
  • 0 in reply to QJ Wang
    Prodigy 60 points
    Thank you for your response.

    How do I differentiate between a diagnostic self test and a "real fault" from the ESM? Is the diagnostic self test shorter in duration?
  • 0 in reply to kyle lobo
    TI__Guru**** 196666 points
    Hi Kyle,

    Write “1010b” to the error forcing key register (ESMEKR). After that, the ERROR pin should output low (error force mode). Write “0000” to the error forcing key register (ESMEKR) back to the active normal mode.

    The ESM module cannot be switched into the error forcing mode if a failure has already been detected in functional mode.

    The error forcing mode doesn't set ESM error status register.
  • 0 in reply to QJ Wang
    Prodigy 60 points
    Hi QJ

    Thanks for your response. I do not understand your previous post.

    If the error pin is asserted during startup self diagnostics then it will trip my system level management.

    What I want to know is if the self diagnostics pulse duration on the error pin is known so that I can "filter" it out during startup. That way when a real failure occurs it will be a long duration pulse and I can use that to reset the processor power.
  • 0 in reply to QJ Wang
    Prodigy 60 points
    Please see latest post.
  • 0 in reply to kyle lobo
    TI__Guru**** 196666 points
    Hi Kyle,

    If the nERROR is asserted, the pin is LOW until the error is cleared. It is impossible to say the nERROR is caused by selftest or real failure using the "pulse duraion".

    The error pin selftest is done in error forcing mode, and the real failure occurs in normal functional mode.
  • 0 in reply to QJ Wang
    Prodigy 60 points

    Hi QJ,

    Thank you for your response. 

    To clarify, can i disable bootup self test such that every time the nERROR is asserted I can be assured that it is a real failure? I think you mentioned this is possible by disabling error forcing mode? 

  • 0 in reply to kyle lobo
    TI__Mastermind 49120 points

    Kyle,

    The ESM module supports a programmable “low time” for which the nERROR pin is asserted whenever it is activated. This low-time is programmed using the ESMLTCPR preload register. You can configure a smaller low-time during the diagnostic checks and a longer duration for a real error once the diagnostic checks are completed. The external safety companion needs to be programmed to ignore low-times lower than the chosen value.

    Regards,

    Sunil