Hi Juergen,<div><br></div><div>Ok, it light me on the way that my board don't use an eeprom to set the FEC address so I probably have to fix that somewhere ...maybe a macro #define NO_EEPROM or something like that ??</div>
<div><br></div><div>Can you, please, show me the <b><i>md -s /dev/phy0</i></b> command output from you mini6410.</div><div><br></div><div>Thanks.<br><br><div class="gmail_quote">---------- Message transféré ----------<br>
De : <b class="gmail_sendername">Juergen Beisert</b> <span dir="ltr"><<a href="mailto:jbe@pengutronix.de">jbe@pengutronix.de</a>></span><br>Date : 23 mars 2012 09:22<br>Objet : Re: Network Issue with Mini2440<br>À : <a href="mailto:barebox@lists.infradead.org">barebox@lists.infradead.org</a><br>
Cc : Kamel BOUHARA <<a href="mailto:k.bouhara@gmail.com">k.bouhara@gmail.com</a>><br><br><br>Hi Kamel,<br>
<div class="im"><br>
Kamel BOUHARA wrote:<br>
> I'm trying to port the last release of barebox to my sbc2440-III board with<br>
> the base config. of a mini2440 but unfortunately I'm facing a network issue<br>
> when trying to boot from nfs or to load files with tftp.<br>
><br>
> After checking all the parameters (pll, ram init etc.) I figured out that<br>
> the chip select and interrupt pinout were not good and I changed them to<br>
> fit with my board schematic.<br>
> So I have a well boot on barebox everything seems to work as you can see<br>
> here :<br>
</div>> [...]<br>
<br>
I changes the DM9000 driver recently. So, I tested both DM9000 revisions I<br>
have access to (based on the Barebox's next branch).<br>
<br>
First on the Mini2440. It comes with a DM9000E:<br>
<br>
---------------------------------------------------------------------------<br>
<br>
mini2440:/ tftp barebox-mini2440 /dev/ram0<br>
TFTP from server 192.168.1.7 ('barebox-mini2440' -> '/dev/ram0')<br>
#################################<br>
mini2440:/ go /dev/ram0<br>
## Starting application at 0x30000000 ...<br>
<br>
barebox 2012.02.0-00259-g773e35b (Mar 23 2012 - 08:53:16)<br>
<br>
Board: Mini 2440<br>
<div class="im">NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit)<br>
Bad block table found at page 65472, version 0x01<br>
Bad block table found at page 65408, version 0x01<br>
</div>nand_read_bbt: Bad block at 0x019e0000<br>
nand_read_bbt: Bad block at 0x02540000<br>
dm9000@dm90000: Found DM9000E at i/o: 0x20000300<br>
s3c_mci@mci0: registered as mci0<br>
<div class="im">refclk: 12000 kHz<br>
mpll: 405000 kHz<br>
upll: 48000 kHz<br>
fclk: 405000 kHz<br>
hclk: 101250 kHz<br>
pclk: 50625 kHz<br>
SDRAM1: CL2@101MHz<br>
Malloc space: 0x33a00000 -> 0x33dfffff (size 4 MB)<br>
Stack space : 0x339f8000 -> 0x33a00000 (size 32 kB)<br>
</div>envfs: wrong magic on /dev/env0<br>
no valid environment found on /dev/env0. Using default environment<br>
running /env/bin/init...<br>
<br>
Hit any key to stop autoboot: 3<br>
mini2440:/ devinfo eth0<br>
resources:<br>
driver: none<br>
<br>
Parameters:<br>
ipaddr = 192.168.1.241<br>
ethaddr = 36:CF:EC:0D:18:Bd<br>
gateway = <NULL><br>
netmask = 255.255.255.0<br>
serverip = 192.168.1.7<br>
mini2440:/ ping 192.168.1.7<br>
<div class="im">phy0: Link is up - 100/Full<br>
</div>host 192.168.1.7 is alive<br>
<br>
---------------------------------------------------------------------------<br>
<br>
And here with my Mini6410. This comes with a DM9000A like your system.<br>
<br>
---------------------------------------------------------------------------<br>
<br>
barebox 2012.02.0-00259-g773e35b-dirty (Mar 23 2012 - 09:19:48)<br>
<br>
Board: Mini 6410<br>
Will write 0x00021300<br>
<div class="im">dm9000@dm90000: Found DM9000A at i/o: 0x18000300<br>
</div>eth@eth0: got MAC address from EEPROM: 08:90:90:90:90:90<br>
refclk: 12000 kHz<br>
apll: 532000 kHz<br>
mpll: 532000 kHz<br>
CPU: 532000 kHz<br>
hclkx2: 266000 kHz<br>
hclk: 133000 kHz<br>
pclk: 66500 kHz<br>
Malloc space: 0x57bc0000 -> 0x57fbffff (size 4 MB)<br>
Stack space : 0x57bb8000 -> 0x57bc0000 (size 32 kB)<br>
Open /dev/env0 No such file or directory<br>
no valid environment found on /dev/env0. Using default environment<br>
running /env/bin/init...<br>
<br>
Hit any key to stop autoboot: 3<br>
mini6410:/ devinfo eth0<br>
resources:<br>
driver: none<br>
<br>
Parameters:<br>
ipaddr = 192.168.1.187<br>
ethaddr = 08:90:90:90:90:90<br>
gateway = 192.168.1.1<br>
netmask = 255.255.255.0<br>
serverip = 192.168.1.7<br>
mini6410:/ ping 192.168.1.7<br>
<div class="im">phy0: Link is up - 100/Full<br>
</div>host 192.168.1.7 is alive<br>
<br>
---------------------------------------------------------------------------<br>
<br>
Regards,<br>
Juergen<br>
<font color="#888888"><br>
--<br>
Pengutronix e.K. | Juergen Beisert |<br>
Linux Solutions for Science and Industry | <a href="http://www.pengutronix.de/" target="_blank">http://www.pengutronix.de/</a> |<br>
</font></div><br><br clear="all"><div><br></div>-- <br><br><div>_______________________________<br><i><font face="'comic sans ms', sans-serif">Kamel BOUHARA</font></i></div><div><div>62 Bis Rue Carnot<div>60610 Lacroix Saint-Ouen</div>
<div><br></div><div>Tel : +33617832904</div><div><br></div></div></div><br>
</div>