• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 33 subscribers
  • Views 572 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.

[TPS65982] OCP timing

Ichiro Fukui
Intellectual 1310 points

Hi,

Our customer is asking when OCP function would be set and activated. Could you answer the question which described in attachment?

Since the product is going to production very soon, I appriciate your prompt reply. I hope to have an answer COB today in Dallas time.

Thanks in advance!

regards,

 Fukui2016-10-30_VBUS_OCP.pptx

  • 0
    TI__Expert 6280 points
    Hi Fukui-san,

    For items 1/2. From the Type-C spec the maximum time from attachment to VBUS tCCDebounce (200ms) and tVBUSON (275ms) 475ms. For the minimum timing is tCCDebounce (100ms). Once the connection has been determined, the Type-C current limit will be set according to the Type-C current advertised. This time will be after the tCCDebounce timing. From the TPS6598x spec the we will set VBUS by 275ms (the timing will vary) but the timing will be roughly 220ms from detection to setting the current limit and then enabling the switch as soon as the current limit has been set.

    For item 3. The current limit is set before sending the PSRDY which lets the sink know its okay to start drawing power. PSRDY can take up 550ms due to variable supplies that may have to transition to a higher or lower voltage.

    For item 4. As soon as as the tPDDebounce has expired (20ms) the current limit and switch are disabled.

    These are very specific numbers, are there any concerns that they currently have?

    Jacob
  • 0 in reply to Jacob Ontiveros
    TI__Intellectual 1310 points
    Jacob-san,

    Thanks for reply.

    I will confirm with customer if they have any concern on this, but those question were from EC firmware development team....

    regards,
    Fukui