• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 64 subscribers
  • Views 436 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 classfication(LLDP)

Joe Chen
Prodigy 40 points

About classfication, There are same problems.

This agreement doesn't match 802.3at(Type-2).

The 802.3at requirements are twice graded.

We measured the TPS23851 only one pules detect.

This may at PD equipment supply will have impact.

How to set?? or how to slove test fail this problem??

 

How to do Link Layer Discovery Protocol - LLDP (IEEE STD 802.1AB) based this function??
 

  • 0
    TI__Mastermind 42795 points

    According to the IEEE802.3at specification, a type 2 PSE that does not provide 2-event physical layer classification must provide data link layer (DLL) classification. A PSE using TPS23851 for ethernet power falls into the latter category as it does not support 2 event physical classification.

    The IEEE spec has more information in section 33.6 about DLL classification, but your software engineers will have to work out the implementation details for your ethernet PHY.

  • 0 in reply to Eric Wright
    Genius 5095 points

    We are debug the PSE controller now,there is have some questions to consult you

    1、MCU communication with TPS23851 by IIC，however，the ninth data is “1” when we write parameter to register，that‘s meaning write become read parameters, which isn't our want. And we can sure this is not our code cause it,so we want  to know what is this phenomenon??

    2、Whether have sample code or not for us to debug，because we can't set the tps23851 as 802.3at PSE controller，it only can as 802.3af PSE controller，which maybe caused by the question（1）。

    Thank you for your reply.