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 SNI auto-negotiation 10MHz pin-settings

Hi team,

Customer of mine setup DP83848i at pin level (I dont have register settings for now): Pins for selecting the SNI : MII_MODE Signal: Pull-up corresponding to a logic '1' SNI_MODE Signal: Pull-up corresponding to a logic '1'   Pins for selection ETHERNET PHY mode: AN_EN Signal: Pull-up corresponding to a logic '1'. AN1 Signal: Pull-down corresponding to a logic '0'. AN0 Signal: Pull-down corresponding to a logic '0'.
The expectation is that in this configuration ,the PHY Ethernet would be limited to10 Mbits / s and the auto-negotiation is enabled for the HALF / FULL Duplex mode.   Behavior of Ethernet PHY experienced: 1) No connected equipment on Ethernet link, then the Ethernet PHY is configured in MII Mode 100Mbits / s and the frequency of the clock is 25MHz TX_CLK => Why Ethernet PHY MII mode configures 100Mbits / s while the HW configuration requires SNI @ 10MHz? 2) system connected to a portable PC set to auto-negotiation, from the PC data, the clock remains at 25MHz TX_CLK corresponding to the IBD method 100Mbits / s. At the end of auto-negotiation protocol, the TX_CLK clock reverts to 10MHz. But with another PC, auto-negotiation seems to fail and TX_CLK clock remains at 25Mhz ( we see that when the auto-negotiation process starts, TX_CLK switches to 10MHz clock goes back to 25MHz   Note: If you configure the Ethernet PHY-10Mbit / s mode forced. (Disabled Auto-negotiation), so in this case, when starting the card, the Ethernet PHY-TX_CLK the clock is 10MHz corresponding to the SNI mode, as expected  
Did we miss any pin configuration?
  • Olivier,

    The straps they have chosen appear to be correct for operation in 10M SNI mode. I am not sure there is a problem here. Is the only concern related to the fact that they see a 25MHz clock during the auto-negotiation process? I believe this is normal for auto-negotiation. Once the process completes, the clock should adjust to the 10MHz SNI clock.

    Patrick
  • Bonjour,

    The issue is that the frequency does NOT come back to 10MHz. If nothing else is on the ethernet link, the TX_CLK remains to 25MHz. And if there is someone to negotiate with then there is only a swift shift to 10MHz, but TX-CLK goes back to 25Mhz and stays there.
    Only if the autonegotiation is deactivated, then TX_clk behaves as expected at 10MHz.

    Yet the auto-negotiation is only for half-duplex / full duplex, right?
  • Hello,

    Autonegotiation deals with selecting the speed as well as Half/Full Duplex. Since the part goes in to 10M SNI mode when forced, the next step would be to check the status of the PHY after autonegotiation is completed. Is it possible to get register values for BMCR (0x00h), BMSR (0x01h), ANAR (0x04h),  PHYSTS (0x10h) and 10BTSCR (0x1Ah) when PHY completes autonegotiation? Also, is the link partner configured for 10M SNI?

    -Regards,

    Aniruddha