From: Dieter Kiermaier <dk-arm-linux@gmx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Kirkwood (Sheevaplug) ping crashes(?) U-Boot
Date: Mon, 22 Jun 2009 14:41:29 +0200 [thread overview]
Message-ID: <200906221441.29217.dk-arm-linux@gmx.de> (raw)
In-Reply-To: <1245673398.3867.3.camel@swa-m460>
Andr??,
> Dieter,
>
> On Mon, 2009-06-22 at 14:04 +0200, Dieter Kiermaier wrote:
> > Hi all,
> >
> > I've tried the first time booting a self compiled u-boot from
> > git.marvell.com U-Boot can be downloaded and started with openocd quite
> > well.
> > Boot messages (version is dirty due to a comment in board file):
> >
> > U-Boot 2009.06-rc2-02207-g14c575a-dirty (Jun 22 2009 - 13:40:45)
> > Marvell-Sheevaplug
> >
> > SoC: Kirkwood 88F6281_A0
> > DRAM: 512 MB
> > NAND: 512 MiB
> > *** Warning - bad CRC or NAND, using default environment
>
> most propably you'll need to save the environment.
Also saving environment doesn't help.
The bad CRC message disappered as expected but that's all what happened.
>
> > In: serial
> > Out: serial
> > Err: serial
> > Net: egiga0
> > 88E1116 Initialized on egiga0
> > Hit any key to stop autoboot: 0
> > Marvell>>
>
> type "save" here and "reset".
>
> > Environment is broken only with marvell git u-boot. Preflashed u-boot
> > find environment is ok.
> > Does sheevaplug u-boot from marvell git use other environment settings
> > than preflashed u-boot?
> >
> > Marvell>> printenv
> > bootcmd=${x_bootcmd_kernel}; setenv bootargs ${x_bootargs}
> > ${x_bootargs_root}; bootm 0x6400000;
> > bootdelay=3
> > baudrate=115200
> > x_bootargs=console=ttyS0,115200
> > mtdparts=orion_nand:512k(uboot),3m at 1m(kernel),1m at 4m(psm),13m at 5m(rootfs)
> > rw x_bootcmd_kernel=nand read 0x100000 0x6400000 0x300000
> > x_bootargs_root=root=/dev/mtdblock3 rw rootfstype=jffs2
> > stdin=serial
> > stdout=serial
> > stderr=serial
> > ethaddr=00:50:43:e0:b9:d8
> > ethact=egiga0
> > ipaddr=192.168.2.75
> >
> > (ipaddr is set after bootup with setenv ipaddr 192.168.2.75)
> >
> > If I now try to ping another machine in the same network:
> > Marvell>> ping 192.168.2.251
> > Using egiga0 device
>
> maybe your MAC is missing ? environment ?
MAC is available in default (compiled in environment) as shown in env above:
> > ethaddr=00:50:43:e0:b9:d8
Also writing a new MAC to environment / savenenv / reset made no difference :(
>
> > This is all what happens - no response from board, CTRL-C doesn't work.
> > Only a hard reset will get the board up again.
> >
> > Do I have to change something in the default board configuration to
> > succesfullly use networking on the sheevaplug?
> >
> > u-boot is build with following commands:
> >
> > make ARCH=arm sheevaplug_config
> > make
> >
> > I get no errors during build.
> >
> > My gcc version is:
> > arm-none-linux-gnueabi-gcc (GCC) 4.2.0 20070413 (prerelease)
> >
> > Any help would be appreciated,
> > Dieter
>
> Regards,
>
> Andr??
>
Dieter
> > _______________________________________________
> > U-Boot mailing list
> > U-Boot at lists.denx.de
> > http://lists.denx.de/mailman/listinfo/u-boot
>
> MATRIX VISION GmbH, Talstra?e 16, DE-71570 Oppenweiler
> Registergericht: Amtsgericht Stuttgart, HRB 271090
> Gesch?ftsf?hrer: Gerhard Thullner, Werner Armingeon, Uwe Furtner,
> Hans-Joachim Reich
next prev parent reply other threads:[~2009-06-22 12:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-22 12:04 [U-Boot] Kirkwood (Sheevaplug) ping crashes(?) U-Boot Dieter Kiermaier
2009-06-22 12:23 ` André Schwarz
2009-06-22 12:41 ` Dieter Kiermaier [this message]
2009-06-22 12:53 ` André Schwarz
2009-06-22 13:08 ` Dieter Kiermaier
2009-06-22 15:01 ` Dieter Kiermaier
2009-06-22 15:34 ` André Schwarz
2009-06-22 15:50 ` Dieter Kiermaier
[not found] <73173D32E9439E4ABB5151606C3E19E201D8E62D09@SC-VEXCH1.marvell.com>
2009-06-22 18:06 ` Dieter Kiermaier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200906221441.29217.dk-arm-linux@gmx.de \
--to=dk-arm-linux@gmx.de \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.