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.

DP83867IR: No MDI I/F establish

Part Number: DP83867IR

We have design with DP83867IRPAPR and 7499111121A magnetic connector (which have shorted CT)

We got working MDIO I/F with the ability to read/write registers

We have config the starp I/F according to 1000 Base-T config

There is clear 25Mhz Clk-out

We got clear Auto-Negotiation signals in ch A & B

As it look our MDI I/F is not establish

My question are:

1. Does a MDI I/F can be establish with PC or Ethan Switch only with starp 1000 Base-T config or we still need to config the device register?

2. Does the MDI I/F will be establish  only after RGMII activity

3. Can 7499111121A magnetic connector (which have shorted CT) couse the MDI I/F not to function?

Thanks

Oded

 

  • Hi Oded,

    As shown in the datasheet, the center taps should not be shorted together. Is it possible for your to replace the connector with one that does not have center taps shorted together?
    Can you provide the register values of 0x00, 0x01, 0x04, 0x09, 0x10, 0x11, 0x14, 0x31, 0x6E, and 0x6F?

    -Regards
    Aniruddha
  • Dear Aniruddha,

    Thanks for you quick answer

    We have order the RJ45 connector that TI use in the eval, it will arrive in 5 days.

    Meanwhile here the status and register map

    We are using PAP package

    We are now config the Phy only by strap resistors, 

    We only define resistor for address and for Autoneg Disable = 0 (RX_DV/RX_CTRL = mode 3), all others starp are config as mode 1

    Power supply = OK

    Reset= 1.8V

    TX_clock = clear 25 Mhz, 2.5V

    MDIO = OK

    Auto-Negotation link pulses appears only in Ch A, No pulse at ch B? is that problem?

    0x0000 1140  
    0x0001 7949
    0x0004 01E1 
    0x0009 0300  
    0x0010 5048  
    0x0011 0302  
    0x0014 29C7  
    0x0031 00b0 
    0x006e 000c 
    0x006f 0100 

    At 0x0031  there are some reserve that define 0 but here are "1"?

    At 0x006e PHY address value from straps=C, but we are using PAP while here RGZ values shown?

    At 0x006f  there are some reserve that define 0 but here are "1"?

    Do you got any other idea what is wrong?

    Thanks

    Oded

  • Dear Aniruddha,
    another issue:
    just run 1000 Base Test Mode 1:
    Reg 0x001F = 0x8000 //reset PHY
    Reg 0x0000 = 0x0140 //1000 Base-T Mode
    Reg 0x0010 = 0x5008 //forced MDI Mode
    Reg 0x0009 = 0x3B00 //Test Mode 1
    Reg 0x0025 = 0x0480 //output test mode to all channels
    Reg 0x01D5 = 0xF508

    The right pattern appears only in CH1 , no pattern in Ch 2-4