<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML dir=ltr><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=unicode">
<META content="MSHTML 6.00.2900.3059" name=GENERATOR></HEAD>
<BODY>
<DIV id=idOWAReplyText97954 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>I see a similar problem on
the MPC8349E MDS (V1.1 CPUs) in that the first ping or tftpboot
command often doesn't work in u-boot 1.1.3 or (much less often) Wind River Linux
kernel 2.6.14. The problem seems least severe on a node-to-node gigabit
connection and most severe on a public 100BT network. I haven't been able to
isolate the cause, but the severity seems dependent on the driver
characteristics of the equipment that the 8349 is communicating with. In my case
I also see very erratic ping times to the NFS server (dependent on how Kudzu
configured its e1000 driver). The 8349 sometimes slows to a crawl and fills
the logs with watchdog messages when it mounts NFS partitions and hits the
INIT phase of boot-up. This is all with out-of-the box software from Motorola
and Wind River. Maybe we will have better luck with the V3.0 CPUs? I wish I
could use 2.6.18, but I'm stuck at 2.6.14.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>Regards, Gary</FONT></DIV></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B>
linuxppc-embedded-bounces+gkenaley=echelon.com@ozlabs.org on behalf of SIP COP
009<BR><B>Sent:</B> Thu 2/22/2007 9:14 PM<BR><B>To:</B>
linuxppc-embedded@ozlabs.org<BR><B>Cc:</B>
sipcop009@gmail.com<BR><B>Subject:</B> Gianfar on 8347 sometimes get stuck at
startup<BR></FONT><BR></DIV>
<DIV>
<DIV> </DIV>
<DIV>We have the our own MPC8349 based board which has 2 GigEs. It is
pretty much modelled similar to the 8349ADS EVAL boards, infact we have zero
changes.</DIV>
<DIV> </DIV>
<DIV>The issue that we are seeing - </DIV>
<DIV> </DIV>
<DIV>Sometimes at startup, we have send 2 TX packets to kind-of-kickstart the
TSEC Tranmission. If we send only packet it does not get to the other side. This
does not happen always.</DIV>
<DIV> </DIV>
<DIV>The TSEC Registers dont really show any errors nor does the Marvell PHY
show any errors.</DIV>
<DIV> </DIV>
<DIV>The kernel that we are using is 2.6.11.</DIV>
<DIV> </DIV>
<DIV>Anybody seen this before or something similar ? </DIV>
<DIV> </DIV>
<DIV>Any pointers will be appreciated. We cannot move to any other kernel
verision right now.</DIV>
<DIV> </DIV>
<DIV>Thanks!</DIV>
<DIV>ashutosh</DIV>
<DIV> </DIV></DIV></BODY></HTML>