• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 63 subscribers
  • Views 237 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.

TPS23851 detection

Munin Lin
Prodigy 230 points

Hello,

When TPS23851 connect to PD(overload condiiton) or non PD(like laptop),

i try read detection status all result "Short-circuit (< 150 Ω)", I need to distinguish standard PD or non PD,

Do you have any suggestion?

Thanks.

  • 0
    TI__Mastermind 42795 points

    TPS23851 is designed to support PD's which are compliant with the IEEE802.3 standard. If the device on the PD end of the cable is not compliant, then the TPS23851 will not power it.

  • 0 in reply to Eric Wright
    Prodigy 230 points

    Hi Eric,

    please help to solve my below question:

    1. We run an overnight I2C (GPIO simulating I2C bus protocol) reading test (twice per second) on two target boards (same schematichs, layout) with same softwae version.  One board is good and another board may read a wrong value within 30 minutes. Can we say it is hardware problem and how to make sure it is?

     

    2. There is a target board connected to a PoE  light-loading  PD (like IP CAM) e.g. 1.5W via an ethernet interface  and then run a weekend I2C reading test (duration: 56 hours*60min*60seconds* twice). There are no any worng values which are read. Vice versa, this board connected to a high load PD e.g. 12 ~ 13W, there are wrong  values observed within 1 hour.  Can we say it is hardware problem and how to make sure it is?

     

    3. Another good board is connected to same high-loading PD. Even passing one hour, it still no wrong values observed.

    Thanks.

  • 0 in reply to Munin Lin
    TI__Mastermind 42795 points

    Hello Kevin,

    From your description, it seems hardware related (since one board works and another does not). Do you have access to an I2C bus sniffer such as Beagle by Total Phase? The Aardvark can work too. These can sniff the bus and log transactions (Total Phase provides free software) so you can get more detail about the register being accessed and other information.

    Another cause could be bus speed. What bus rate are you using?