I've, unfortunately, just come across this problem. I'm really stuck because
I'm connecting directly to a PC via a crossover cable.

Anyone got any opinions on the following.

Adding code to try to cycle the interface if it detects it's down for more
than a few seconds.

Allowing an external reset to the board if the interface is down for more
than a few minutes.

Reconfiguring the Gigabit Ethernet port on the PC to lock it at 100FDX???


Any ideas appreciated..

PK

-----Original Message-----
From: rabbit-semi@yahoogroups.com [mailto:rabbit-semi@yahoogroups.com] On
Behalf Of Scott Henion
Sent: Sunday, 5 July 2009 3:15 PM
To: rabbit-semi@yahoogroups.com
Subject: Re: [rabbit-semi] Re: RCM4300 ethernet cable detect problem

mfawzy79 wrote:
> actually, I'm already using DC 10.54 and i'm still having the problem
>
>
There is a bug in the ASIX chip that will cause it to not negotiate
correctly with some hubs/switches. The fix was to use a very long reset
to the chip, something like 3 seconds. It would work on a power-up but
not on later resets.

The bug was fixed in the Softools port of the stack. AFAIK, ZW never
implemented the fix. I also notice on the newer modules the no longer
feed a pin to the ASIX chip to use as a reset. So, your only option may
be to get a different hub/switch.

--
------------------------------------------
| Scott G. Henion| shenion@... |
| Consultant | Stone Mountain, GA |
| SHDesigns http://www.shdesigns.org |
------------------------------------------




------------------------------------

Yahoo! Groups Links