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.

TPS65982: Condition asserted "Error_PowerEventOccurred"[3] in IntEventX register

Part Number: TPS65982

Hi Team,

Could you tell me the condition asserted "Error_PowerEventOccurred"[3] in IntEventX register?  
It is very helpful if you have a diagram describing the condition.

Regards,

Takashi Onawa

  • Hi Onawa-san,

    I do not have a diagram describing the condition for this event. However, the "Error_PowerEventOccurred" event will occur if there is a Short to GND on VBUS. The "Error_PowerEventOccurred" will also occur of there is an over-voltage protection event on VBUS. An over-voltage protection event will occur if the VBUS voltage goes above the negotiated PD voltage.

    Thank you,
    Eric
  • Hi Eric-san,

    Thanks for your prompt response on this. OK, I understood the "Error_PowerEventOccurred" event will occur "Short to GND on VBUS" logical OR "over-voltage protection" event.

    > if the VBUS voltage goes above the negotiated PD voltage.

    Could you tell me more detail of the condition occurring the  over-voltage protection event?

    Especially, I need to clarify trigger condition such as threshold and de-glitch time.

    Regards,

    Takashi Onawa

  • Hi Onawa-san,

    As you mentioned in your other post, the OvpUsage[23:22] in 0x28 System Configuration Register and OvpTripPoint[21:16] in 0x28 System Configuration Register are used to enable OVP and set the point where an OVP event will occur.

    The image below from the Host Interface Technical Reference manual explains what each setting will do:

    If OvpUsage is set to 00b, you can manually enter an OVP trip point in the OvpTripPoint field. Otherwise, you can set the OvpUsage field to trigger an OVP when the VBUS voltage exceeds either 5%, 10%, or 15% of the expected maximum on the current PDO. 

    For example, if you set OvpUsage to 10b (10% of expected max) and you have a 5V PD contract established, there will be an OVP event if VBUS exceeds 5.5V.

    Thank you,

    Eric

  • Hi Eric-san,

    Thanks for your prompt response on this.

    〉If OvpUsage is set to 00b, you can manually enter an OVP trip point in the OvpTripPoint field.
    〉 Otherwise, you can set the OvpUsage field to trigger an OVP when the VBUS voltage exceeds
    〉 either 5%, 10%, or 15% of the expected maximum on the current PDO.

    OK, I understood that there are two option in OVP of TPS65982 as followings

    Option1

    OVPUsage : 00b
    We can select one OVP point that can be changed by the "OVP trip point" register.

    Option2

    OVPUsage : 01b, 10b, 11b
    We can set OVP voltage level for each PDOs, ether 5%, 10% or 15%.

    Sorry, the following two point are unclear for me.

    #1
    If TPS65982 gets the OVP condition, what happens? PD Hard reset or just closed FETs?
    PD specification saying that PD controller should issue Hard reset in Sink use case. So in Sink case,  TPS65982 should issue Hard reset. But in Source case, no spec on the OVP behavior.

    #2
    I want to know if TPS65982 triggers OVP once VBUS voltage goes beyond the selected level, or the trigger is applied when the exceeded state continues.

    If TPS65982 behaves as latter, are there any registers to set the de-glitch time(exceeded state timer) for the selected OVP levels in Opetion2 case?

    Regards,

    Takashi Onawa

  • Hi Onawa-san,

    #1, The TPS65982 will issue a Hard Reset when either a Sink or Source when an OVP event occurs.

    #2, TPS65982 will trigger OVP once VBUS voltage exceeds selected level.

    Thank you,
    Eric