2011-08-21 04:43:10 BF537E Auto negotiation issue
billy walton (UNITED KINGDOM)
Message: 103056
Hi,
I have a board which we have just got back from the pcb makers, which uses a BF537E device
All works fine, however, when we connect the ethernet to it, it seems to have a auto negotiation issue, i get the following OP
PHY: 0:00 - Link is Up - 100/Half
PHY: 0:00 - Link is Up - 100/Full
PHY: 0:00 - Link is Up - 100/Half
PHY: 0:00 - Link is Up - 100/Full
PHY: 0:00 - Link is Up - 100/Half
PHY: 0:00 - Link is Up - 100/Full
PHY: 0:00 - Link is Up - 100/Half
PHY: 0:00 - Link is Up - 100/Full
PHY: 0:00 - Link is Up - 100/Half
PHY: 0:00 - Link is Up - 100/Full
PHY: 0:00 - Link is Up - 100/Half
PHY: 0:00 - Link is Up - 100/Full
This just continues to cycle like this
Has anyone seem similar before? or have any ideas as to how i might solve it?
The design was a copy of a dev boards implementation, and that works fine - the only real difference i see is track routing.
Any help appreciated
Billy
eth0 Link encap:Ethernet HWaddr 00:1A:7A:FE:00:15
inet addr:192.168.0.72 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:232 errors:0 dropped:0 overruns:0 frame:0
TX packets:566 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:237 errors:0 dropped:0 overruns:0 frame:0
TX packets:237 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
bfin_mii_bus: probed
bfin_mac: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:00, irq=-1, mdc_
clk=2500000Hz(mdc_div=25)@sclk=131MHz)
bfin_mac bfin_mac.0: Blackfin on-chip Ethernet MAC driver, Version 1.1
TCP cubic registered
NET: Registered protocol family 17
QuoteReplyEditDelete
2011-08-26 05:06:59 Re: BF537E Auto negotiation issue
Aaron Wu (CHINA)
Message: 103157
The Full/Half mode is detected by the PHY chip automatically, and the detection result is sent to MAC/CPU by MDC/MDIO interface. This auto negotiation is done by the PHY without software interference, so you may pay attention on your PHY design and the PHY capability of the other terminal of connection. Yes as you said, the difference for track routing may make sense.
Looks like your internet invironment is not stable so the PHY is keeping reset.
QuoteReplyEditDelete
2011-08-30 03:02:20 Re: BF537E Auto negotiation issue
billy walton (UNITED KINGDOM)
Message: 103186
Hi Aaron,
Thanks for your reply
I cant think the network as if i plug in my ref board using the same cables, all is OK
I have done a full compliance test now on my project and it passed every test
It has to be either track routing, quality of board or connector now - or maybe - possibly more likely, i have some pads exposed for future development, im thinking maybe one of these is picking up a little noise which is sending it off - ill try to ground them all next i think
Billy