This is a problem I've been fighting to for a long time. I'm sure it
would be something stupid I haven't noticed, but I don't know what
else to try. My Linux OS is working flawlessly with a correct eth0
device, so at least I know it's not (or should not) a hardware
problem.
Everything else works as expected, but the LAN91C96 driver does not
enable the board network interface.
Environment:
Hardware: Lubbock Board from Intel, wired to an IBM Laptop.
U-boot version: 1.3.3 (tried with 1.3.1, 1.20, same results)
mac address: tried with the one generated by the eth_gen_tool, and the
original hardware one.
Default 'lubbock.h' file, heavy edited one, etc... No luck.
$ printenv:
U-Boot 1.3.3 (Jul 8 2008 - 19:07:01)
DRAM: 64 MB
Flash: 64 MB
Hit any key to stop autoboot: 0
$ printenv
baudrate=115200
netmask=255.255.0.0
bootdelay=5
serverip=192.168.1.1
ipaddr=192.168.1.2
bootcmd=bootm 200000
bootargs=ip=192.168.1.2:192.168.1.1:192.168.1.1:255.255.255.0:pxa:eth0:off
mem=64M root=/dev/nfs nfsroot=192.168.1.1:/rootfs/nfs init=/sbin/init
console=ttyS0,115200
ethaddr=00:02:b3:00:8f:xx
stdin=serial
stdout=serial
stderr=serial
Something odd I noticed:
$ tftpboot
Warning: MAC addresses don't match:
HW MAC address: 01:00:01:00:01:00
"ethaddr" value: 00:02:B3:00:8F:xx
Using MAC Address 00:02:B3:00:8F:xx
Linux detects the correct Mac Address without any configuration, why
u-boot reads 01:00:01:00:01:00?
Any idea?
I will thank a lubbock.h file in case you got one with ethernet
working, just to try it out.
Thanks a lot.
-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
U-Boot-Users mailing list
U-Boot-Users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/u-boot-users
