• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 32 subscribers
  • Views 1364 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.

DP83848I: Migrating from TLK110 to DP83848

Kummi
Mastermind 6220 points
Part Number: DP83848I
Other Parts Discussed in Thread: TLK110

Hi,

Do we have any migration guide on TLK110 to DP83848.

Because of some issues we are planning to replace TLK110 PHY with DP83848.
It is mentioned that DP83848 is functionally equivalent device to TLK110 and
is pin to pin compatible if we don't use SW_Strap.

We would like to know is it easy to replace TLK110 with DP83848 with respect
to Software perspective? Does the same software work?
Please let us know what registers need to be considered when migrating to DP83848.
If necessary I can send you the current driver software.

Best Regards
Kummi

  • 0
    TI__Mastermind 19780 points
    Hi Kummi,

    2 major topics to consider when looking at SW compatibility between PHYs:

    1. PHY ID is sometimes used to validate the presence and model of a PHY. That PHY ID is in register 0x2 and 0x3 for all IEEE 802.3 PHYs, and it is different between all models.
    2. Any register addresses above 0x15 are not defined by IEEE and will be different between PHYs.
    a. Comparing TLK110 to DP83848 shows that register 0x0 to 0x7 are the same.
    Register 0x8 and 0x9 are in TLK110 but not in DP83848
    Register 0x10 is the same
    Register 0x11 is different
    Register 0x12 to 0x15 are the same
    All register above 0x15 are different between TLK110 and DP83848

    Your TLK110 driver, where it accesses registers that are not the same, should be modified.

    Best Regards,
  • 0 in reply to Rob Rodrigues
    Mastermind 6220 points
    Hi Rob,

    Thank you very much for the information.

    We thought DP83848's CLK_OUT feature could be used to provide RMII_REFCLK for the MAC.
    But came to know CLK_OUT clock is not suitable for the RMII communication.

    Actually our customer's application was designed on 2012,
    we didn't had any information about TLK110's CLK_OUT issue during that time,
    so CLK_OUT was connected to the RMII_REFCLK. Now it is difficult to modify the connection.

    Do we have any other PHY option that could replace TLK110 and which has CLK_OUT feature?

    Currently our customer's application has issues with TLK110(mentioned below)
    and we are looking for the options to replace the PHY or any software solution.
    e2e.ti.com/.../597647

    Best Regards
    Kummi