• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 64 subscribers
  • Views 140 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

LP8764-Q1: nRESETOUT GPIO10 value chagne via Register access

Bala Mahadeva iyer
Prodigy 190 points
Part Number: LP8764-Q1

I have assigned GPIO10 for nRESETOUT\ function. 

I want to assert this signal when Watchdog error is encounted. But I do not want to power down the chip.

If I assert this signal when WD_ERROR is encountered, Is it possible for another master to de assert this nRESETOUT via an I2C register write ?

  • 0
    TI__Expert 7060 points

    Hi Bala,

    In principal yes, the idea has just been warm reset sequence would turn signal first low and then back to high after in the end of the sequence.

    Br, Jari

  • 0 in reply to Jari Niemela13
    Prodigy 190 points

    Hello Jari

    I have the following in my FSM. I do read that the WD_ERR_STATUS Register read 0xF2. But I do not see the nRSTOUT (GPIO10) asserted low.

    I am asserting nRSTOUT But I am not seeing the RESET# ping go low. Why is that ?

              

  • 0 in reply to Bala Mahadeva iyer
    Prodigy 190 points

    Also, the Idea is to issue nRSTOUT while in WD_ERROR, without disturbing any of the power rails. While in that state, an external system manager CPU will intervene and either release the nRSTOUT (after capturing the I2C bus , do a write to MISC_REG and releasing it for the local CPU) or force it to STANDBY state by de asserting GPIO4 (This is an enable to the PMIC power sequencing) and then asserting GPIO to take the system back to ACTIVE state (No i2c access from the system manager cpu and the local Cpu has to read the interrupt register on boot and convey the system manager regariding a watchdog event. I hope this can be implemented. Please confirm. Thanks

  • +1 in reply to Bala Mahadeva iyer
    TI__Expert 4480 points

    Hi Bala,

    Our device experts have received your questions and will be looking into them shortly.

    Regards,
    Megan

  • +1 in reply to Bala Mahadeva iyer
    TI__Expert 4651 points

    Hello Bala,

    When you mention RESET# ping, do you mean nRSTOUT pin?

    Have you mapped the ACT2WDE sequence to the WD_ERROR RISE trigger in the "triggers settings" tab of GUI? Also, review your trigger priority list in case another one takes precedence over this one.

    Best regards,

    Florian