From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dieter Kiermaier Date: Mon, 22 Jun 2009 20:06:50 +0200 Subject: [U-Boot] Kirkwood (Sheevaplug) ping crashes(?) U-Boot In-Reply-To: <73173D32E9439E4ABB5151606C3E19E201D8E62D09@SC-VEXCH1.marvell.com> References: <73173D32E9439E4ABB5151606C3E19E201D8E62D09@SC-VEXCH1.marvell.com> Message-ID: <20090622180650.21910@gmx.net> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de -------- Original-Nachricht -------- > Datum: Mon, 22 Jun 2009 10:10:20 -0700 > Von: Prafulla Wadaskar > An: "dk-arm-linux at gmx.de" , "Andr? Schwarz" > CC: "u-boot at 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