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 20:06:50 +0200 [thread overview]
Message-ID: <20090622180650.21910@gmx.net> (raw)
In-Reply-To: <73173D32E9439E4ABB5151606C3E19E201D8E62D09@SC-VEXCH1.marvell.com>
-------- Original-Nachricht --------
> Datum: Mon, 22 Jun 2009 10:10:20 -0700
> Von: Prafulla Wadaskar <prafulla@marvell.com>
> An: "dk-arm-linux at gmx.de" <dk-arm-linux@gmx.de>, "Andr? Schwarz" <andre.schwarz@matrix-vision.de>
> CC: "u-boot at lists.denx.de" <u-boot@lists.denx.de>
> Betreff: RE: [U-Boot] Kirkwood (Sheevaplug) ping crashes(?) U-Boot
>
>
> > -----Original Message-----
> > From: u-boot-bounces at lists.denx.de
> > [mailto:u-boot-bounces at lists.denx.de] On Behalf Of Dieter Kiermaier
> > Sent: Monday, June 22, 2009 9:21 PM
> > To: Andr? Schwarz
> > Cc: u-boot at lists.denx.de
> > Subject: Re: [U-Boot] Kirkwood (Sheevaplug) ping crashes(?) U-Boot
> >
> > Am Montag 22 Juni 2009 17:34:35 schrieb Andr? Schwarz:
> > Andr?,
> >
> > > Dieter,
> > >
> > > On Mon, 2009-06-22 at 17:01 +0200, Dieter Kiermaier wrote:
> > > > Am Montag 22 Juni 2009 15:08:20 schrieb Dieter Kiermaier:
> > > >
> > > > This seems to be an issue regarding Gigabit / 100MBits
> > uplink with
> > > > current marvell git u-boot.
> > >
> > > this gives lots of things worth looking at them :
> > >
> > > - are you running on a custom board, i.e. is MDIO known to work
> > > properly
> > > -> PHY adressing ?
> > > - Does your chips require different clocks for 100M/1000M ?
> > > - What about mis-strapped link advertisement of the PHY ? Maybe
> > > 100M-FD disabled ?
> > >
> > > Have you tried mii diagnostics ?
> > > Have a look at common/cmd_mii.c -> "mii info" and "mii
> > dump" should be
> > > your friends.
> > >
> >
> > I don't think it's a hardware problem.
> > An older u-boot version provided from marvell works without
> > any problems.
> Yes, this is not h/w problem, auto-speed negociation was disabled, hence
> it was not working with 100baseT, now this problem is resolved,
> Please use attached patches to resolve this for current u-boot.git
>
> The improved version of this driver is already mainlined you can find it
> here
> http://lists.denx.de/pipermail/u-boot/2009-June/054314.html
>
> I am sorry I could not update the thread, niether u-boot.git on
> git.marvell.com :-(,
> I am facing some problem at my end, hopefully I will update everything by
> tomorrow.
>
> > > > > > > >
> > > > > > > > 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?
> Yes Marvell u-boot and u-boot.git are different uses different address to
> save environment variables, so if you altered any of u-boot, environment
> will be resetted.
>
> And they are not same on these both u-boot. u-boot.git are simple and
> minimal but enough to boot from nand.
Thanks for clarifying these, too.
>
> > > > > > > > >
> > > > > > > > > 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),13
> > > > > > > > >m at 5m (roo tf s) 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)
> > > > > >
> > > > > > Did you try "bootp" or "dhcp" to set up the I/F ?
> > > > >
> > > > > Yes, but everytimes the same:
> > > > > Marvell>> dhcp
> > > > > BOOTP broadcast 1
> > > > >
> > > > > ... machine hangs and only a reset helps...
> Even this problem is resolved in new driver/attached patches.
>
Many thanks for the quick response!
Dieter
> Regards.
> Prafulla . .
--
GRATIS f?r alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
next parent reply other threads:[~2009-06-22 18:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <73173D32E9439E4ABB5151606C3E19E201D8E62D09@SC-VEXCH1.marvell.com>
2009-06-22 18:06 ` Dieter Kiermaier [this message]
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
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
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=20090622180650.21910@gmx.net \
--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.