Blunk Microsystems has developed a TargetOS BSP for the M54XXEVB that includes an Ethernet driver for TargetTCP, our embedded TCP/IP stack. I have found that I am unable to connect to a 1000/100/10Mbps switch. The PHY never completes auto-negotiation.

We have one customer who sometimes has trouble getting a physical connection on their network, depending on which device they plug into. Another customer is also unable to connect via a 1000/100/10Mbps switch. I have not seen any PHY connect problems using either a 10 Base-T hub or a 100/10 Base-T switch in my office.

While investigating the 1000/100/10 Mbps switch connect problem, I found that when I periodically read the BCM5222 100BASE-TX Auxiliary Status Register (addr 17), bit 0 (MLT3 Code Error Detected) is always set.

Also, periodically reading the BCM5222 Auxiliary Multiple PHY Register (addr 30), I see that bit 5 (Acknowledge Detected) gets set, but bits 6 (Acknowledge Complete) and 7 (Auto-Negotiation Complete) are never set, indicating that the auto-negotiation state machine doesn't progress after leaving the acknowledged detect state.

Has anyone else seen these problems? Are there any known problems with the BCM5222 circuitry? Do you have any suggestions for BCM5222 register initialization that will help solve these PHY connect problems?

Best regards,
Tim

------------------------------------------------------------
Tim Stoutamore, Principal Engineer
Blunk Microsystems
6576 Leyland Park Drive
San Jose, CA 95120-4558
Tel: 408/323-1758
stout@blunkmicro.com
http://www.blunkmicro.com
------------------------------------------------------------