Forum Discussion

Altera_Forum's avatar
Altera_Forum
Icon for Honored Contributor rankHonored Contributor
13 years ago

Auto-Negotiation FAILED

I have a custom board with the 88E111 Ethernet PHY. At one point, the board would light up LEDs indicating a link has been made and it was in 100 mode.

I did not change my design at all, but now I can't make a link. This first happened when I tried to plug the board directly into the LAN from the wall, rather than through the switch, in an attempt to get DHCP to work. I now have the board connected to a switch which goes to a PC and company LAN.

The lights on the switch indicate that there is a physical connection made on the port the board is plugged into. They blink with 10 mode activity. But, the board doesn't indicate a link.

Running the simple socket server design produces this output: 


prepped 1 interface, initializing...
INFO    : TSE MAC 0 found at address 0x08000000
INFO    : PHY Marvell 88E1111 found at PHY address 0x12 of MAC Group
INFO    : PHY - Automatically mapped to tse_mac_device
INFO    : PHY - Restart Auto-Negotiation, checking PHY link...
WARNING : PHY - Auto-Negotiation FAILED
MARVELL : Enabling auto crossover
MARVELL : PHY reset
MARVELL : Mode changed to RGMII/Modified MII to Copper mode
MARVELL : Enable RGMII Timing Control
MARVELL : PHY reset
INFO    : PHY - Checking link...
INFO    : PHY - Link not yet established, restart auto-negotiation...
INFO    : PHY - Restart Auto-Negotiation, checking PHY link...
WARNING : PHY - Auto-Negotiation FAILED
WARNING : PHY - Link could not established
WARNING : PHY - Auto-Negotiation not completed! Speed = 100, Duplex = Full
OK, x=0, CMD_CONFIG=0x00000000
I am completely stumped on how I can't even make a link now, without changing any hardware or software.

Before moving cables to plug the board directly into the wall, it would pass the auto negotiation and then fail at DHCP. I have gone back to the original setup exactly but the result is the same. No link at all.

15 Replies

  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    13 years ago

    You're sure the cable is connected correctly? Auto-Negotiation is a property of the PHY itself. You receive this value via MDIO interface, so it's MDI side problem.

  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    13 years ago

    --- Quote Start ---

    You're sure the cable is connected correctly? Auto-Negotiation is a property of the PHY itself. You receive this value via MDIO interface, so it's MDI side problem.

    --- Quote End ---

    Yes, also I've switched cables to be sure.

    Do you think I may have a broken connector?

    I've also tried the setup in a completely different lab with different cable, switch, and wall connection and it did not make a difference.
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    13 years ago

    Do you use DHCP or Static IP.....in your pc?

    If you use DHCP....try to use a Static IP....
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    13 years ago

    I built a new board with a different LAN connector and I'm still having the exact same issue. It worked all day, now nothing.

  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    13 years ago

    I seem to have fixed the problem, hopefully permanently, by adding a 100 clock cycle delay til I drive the ethernet PHY reset line high when the board powers up.

  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    13 years ago

    --- Quote Start ---

    I seem to have fixed the problem, hopefully permanently, by adding a 100 clock cycle delay til I drive the ethernet PHY reset line high when the board powers up.

    --- Quote End ---

    Is it Marvell 88E1111 chip? Did You read the datasheet then? It needs about 50ms reset after power up. Kinda annoying bug.
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    11 years ago

    --- Quote Start ---

    I have a custom board with the 88E111 Ethernet PHY. At one point, the board would light up LEDs indicating a link has been made and it was in 100 mode.

    I did not change my design at all, but now I can't make a link. This first happened when I tried to plug the board directly into the LAN from the wall, rather than through the switch, in an attempt to get DHCP to work. I now have the board connected to a switch which goes to a PC and company LAN.

    The lights on the switch indicate that there is a physical connection made on the port the board is plugged into. They blink with 10 mode activity. But, the board doesn't indicate a link.

    Running the simple socket server design produces this output: 

    
prepped 1 interface, initializing...
INFO    : TSE MAC 0 found at address 0x08000000
INFO    : PHY Marvell 88E1111 found at PHY address 0x12 of MAC Group
INFO    : PHY - Automatically mapped to tse_mac_device
INFO    : PHY - Restart Auto-Negotiation, checking PHY link...
WARNING : PHY - Auto-Negotiation FAILED
MARVELL : Enabling auto crossover
MARVELL : PHY reset
MARVELL : Mode changed to RGMII/Modified MII to Copper mode
MARVELL : Enable RGMII Timing Control
MARVELL : PHY reset
INFO    : PHY - Checking link...
INFO    : PHY - Link not yet established, restart auto-negotiation...
INFO    : PHY - Restart Auto-Negotiation, checking PHY link...
WARNING : PHY - Auto-Negotiation FAILED
WARNING : PHY - Link could not established
WARNING : PHY - Auto-Negotiation not completed! Speed = 100, Duplex = Full
OK, x=0, CMD_CONFIG=0x00000000
    I am completely stumped on how I can't even make a link now, without changing any hardware or software.

    Before moving cables to plug the board directly into the wall, it would pass the auto negotiation and then fail at DHCP. I have gone back to the original setup exactly but the result is the same. No link at all.

    --- Quote End ---

    So did you finally solved this issue? I'm having the same exact message and running out of options. Thanks!
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    11 years ago

    I am now having the same problem as you did

    Have you ever fiugred it out ?
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    11 years ago

    --- Quote Start ---

    I am now having the same problem as you did

    Have you ever fiugred it out ?

    --- Quote End ---

    Yes, what worked for me was as dumb as upgrading to quartus 13.1. Altera even knows about the IP bugs on 13.0 but they don't tell you until you voice your frustration. I spent at least a week debugging this issue and all I needed was a SW upgrade :mad: