[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [microblaze-uclinux] RE-connection Ethernet..... more
Thanks Aurash, here's the results from trying your suggestions:
- From a cold boot, the ethernet works (dhcpcd, telnet, ftp, httpd)
- The activity light flashes with transfers, but the link light is off on
the board(!!), lit on the router
- <ifconfig eth0 down> stops the ethernet, no change in link lights on board
- <ifconfig eth0 192.168.10.4> brings ethernet operation back, no change in
- unplugging the ethernet cable stops the ethernet, gives
<eth0: Duplex has been changed: now HALF_DUPLEX \ eth0: Link carrier
as previously described, link light on router goes out, link light on board
- plugging ethernet cable back in lights the link light on board(!!) and
link light on router, but no ethernet operation, no messages from the the
board console, the activity light flashes during a ftp connection attempt,
but it does not succeed.
- <ifconfig eth0 down> followed by <ifconfig eth0 192.168.10.4> left the
link lights on the board and router on, the activity light flashes during a
ftp connection attempt, but it does not succeed.
I found a few references to a "ICS1893 Phy workaround" in the mainline Linux
world, going back to Oct 2001, so presumeably the uClinux world has already
caught that issue (whatever it was).
The ICS1892 Phy on the NuHo Spartan3-2000 dev board uses the indicator LED
lines as configuration of its MII address during reset (MII #1 in this
case), which must be working if the EMAC can see it and use it(??). Looking
at the schematic, NuHo seems to have followed the ICS datasheet to the
letter in terms of the LED/config pin connections.
Possible question for anyone else with a NuHo S3 board - do you get the same
results re: LED and ethernet operation?
----- Original Message -----
From: "Aurash" <email@example.com>
Sent: Wednesday, August 24, 2005 6:23 PM
Subject: Re: [microblaze-uclinux] RE-connection Ethernet..... more
> Hi there,
> The PHY chip should start negotiating the link when you plug the cable
> back, what's the state of the link led?
> >ifconfig eth0 down
> and then run
> >ifconfig eth0 your_ip
> this should force the PHY to renegotiate if it's not in autonegotiate mode
> by default.
> Jim Law wrote:
>> Following up on the question below, I wonder if this isn't another
>> artifact of an unlicensed EMAC core???
> no, it's not, this should happen only after a couple of hours (~8 hours at
> my sytem is restoring the link imediately (1 sec max)
>> Hi all,
>> Things are bubbling along here - now firmly setup under VMWare and having
>> fun with our NuHo S3-2000 board.
>> ..... and there's always a 'but'......
>> If I disconnect the RJ45 Ethernet cable from the board, I get:
>> eth0: Duplex has been changed: now HALF_DUPLEX
>> eth0: Link carrier lost.
>> ... not too bizarre.
>> But when I re-connect the cable, I don't seem to re-establish the
>> port (i.e. it no longer responds to pings, telnet, ftp, etc. from
>> even though an ifconfig reports all is well.
>> Any guidance or experience with this one?
>> Jim Law
>> Iris Power Engineering
>> microblaze-uclinux mailing list
>> Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
>> Mailing List Archive :
> microblaze-uclinux mailing list
> Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
> Mailing List Archive :
microblaze-uclinux mailing list
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/