[U-Boot] U-boot networking not working

[U-Boot] U-boot networking not working

[Mark Underwood]

Hi,

I've got an sbc6000x from www.armkits.com. I've been working through how
to put debian onto this board and was making some progress (im just a
beginner), but now I
dont have network access when at the U-boot prompt. The Board is
connected to the network as the link light is on on the interface. As
soon as I try to ping the board itself ie ping 192.192.192.200 (the
default ip address) the link light goes out. this is from the command
line

U-Boot> ping 192.192.192.200
dm9000 i/o: 0x30000000, id: 0x90000a46 
DM9000: running in 16 bit mode
MAC: de:ad:be:ef:01:01
operating at 100M full duplex mode
ping failed; host 192.192.192.200 is not alive


now if I go ahead and boot the board i can ping once im in the linux
root file system
that is currently on the board (I've changed the IP address on bootup in
the linux image.)

~ $ ping 192.168.0.21
PING 192.168.0.21 (192.168.0.21): 56 data bytes
64 bytes from 192.168.0.21: icmp_seq=0 ttl=64 time=0.5 ms
64 bytes from 192.168.0.21: icmp_seq=1 ttl=64 time=0.3 ms
64 bytes from 192.168.0.21: icmp_seq=2 ttl=64 time=0.3 ms


is there a setting in u-boot that could mean that the network is turned
off?

following are the environment variables of u-boot

U-Boot> printenv
bootcmd=nand read 0x22000000 0x1A0000 0x200000; bootm 0x22000000
bootdelay=3
baudrate=115200
ethaddr=DE:AD:BE:EF:01:01
ipaddr=192.192.192.200
serverip=192.192.192.105
gatewayip=192.192.192.101
netmask=255.255.255.0
splashimage=0x21000000
bootlogo=0 
lcdtype=480x272
bootargs=console=ttyS0,115200 tft=480x272 root=/dev/mtdblock6
mtdparts=at91_nand:128k(bootstrap)ro,256k(uboot)ro,128k(env1)ro,128k(env2)ro,1M(logo)ro,2M(linux),-(root) rw rootfstype=yaffs2

Environment size: 455/131067 bytes

im using u-boot 1.3.4.



Any help with this would be great!

Regards

Mark

[U-Boot] U-boot networking not working

[Wolfgang Denk]

Dear Mark Underwood,

In message <1291273748.31320.3.camel@bertha> you wrote:
> 
> I've got an sbc6000x from www.armkits.com. I've been working through how
> to put debian onto this board and was making some progress (im just a
> beginner), but now I
> dont have network access when at the U-boot prompt. The Board is
> connected to the network as the link light is on on the interface. As
> soon as I try to ping the board itself ie ping 192.192.192.200 (the
> default ip address) the link light goes out. this is from the command
> line

Well, I guess you did not read the FAQ...

> U-Boot> printenv
> bootcmd=nand read 0x22000000 0x1A0000 0x200000; bootm 0x22000000
> bootdelay=3
> baudrate=115200
> ethaddr=DE:AD:BE:EF:01:01

Ouch.

See FAQ 14.2.13. Ethernet Does Not Work

See also 14.2.14. Where Can I Get a Valid MAC Address from?

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
"What if" is a trademark of Hewlett Packard, so stop using it in your
sentences without permission, or risk being sued.

[U-Boot] U-boot networking not working

[Mark Underwood]

Hi!

thanks for your quick replys. More helpful than the manufacturer thats 
for sure.

I totally admit that im a newbie at all this, so sorry if I dont 
understand things.

I was under the impression that the MAC address was supplied by the 
hardware supplier. (at least this seems to be the can in the PC world). 
Is this not the case in the embedded world?

Cheers

Mark

Wolfgang Denk wrote:
> Dear Mark Underwood,
>
> In message<1291273748.31320.3.camel@bertha>  you wrote:
>> I've got an sbc6000x from www.armkits.com. I've been working through how
>> to put debian onto this board and was making some progress (im just a
>> beginner), but now I
>> dont have network access when at the U-boot prompt. The Board is
>> connected to the network as the link light is on on the interface. As
>> soon as I try to ping the board itself ie ping 192.192.192.200 (the
>> default ip address) the link light goes out. this is from the command
>> line
>
> Well, I guess you did not read the FAQ...
>
>> U-Boot>  printenv
>> bootcmd=nand read 0x22000000 0x1A0000 0x200000; bootm 0x22000000
>> bootdelay=3
>> baudrate=115200
>> ethaddr=DE:AD:BE:EF:01:01
>
> Ouch.
>
> See FAQ 14.2.13. Ethernet Does Not Work
>
> See also 14.2.14. Where Can I Get a Valid MAC Address from?
>
> Best regards,
>
> Wolfgang Denk
>

[U-Boot] U-boot networking not working

[Albert ARIBAUD]

Mark,

Please do not write your answers above the text you answer to (i.e., do 
not top-post)

Le 02/12/2010 10:48, Mark Underwood a ?crit :
> Hi!
>
> thanks for your quick replys. More helpful than the manufacturer thats
> for sure.
>
> I totally admit that im a newbie at all this, so sorry if I dont
> understand things.

No problem -- we all learn something new every day. :)

> I was under the impression that the MAC address was supplied by the
> hardware supplier. (at least this seems to be the can in the PC world).
> Is this not the case in the embedded world?

Yes, it is; but while the supplier provides a unique MAC address for 
each MAC they send out, they don't necessarily burn it in the HW: it is 
often configurable.

Here, the MAC is configured from a u-boot env variable; but obviously, 
the MAC address specified in your u-boot environment is not a valid one 
(I needed a second look and a step backward to read it as "DEAD BEEF 01 
01").

I suggest looking for your MAC address on a sticker or marking on the 
board, or a printed leaflet, or on the box.

> Cheers
>
> Mark

Amicalement,
-- 
Albert.