From: KISHINAMI Masaya <kishinami@cs.fujitsu.co.jp>
To: Eugene Surovegin <ebs@ebshome.net>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: 405GP Networking issue
Date: Wed, 05 Mar 2003 19:37:15 +0900 [thread overview]
Message-ID: <200303051037.AA02365@kishinami.cs.fujitsu.co.jp> (raw)
In-Reply-To: <5.1.0.14.2.20030228104732.02da48d0@mail.ebshome.net>
Hi, Eugene.
Thank you for your advice.
--- On Sat, 1 Mar 2003 04:08:33 +0900 Eugene Surovegin<ebs@ebshome.net> -san wrote:
>
>At 04:27 AM 2/28/2003, KISHINAMI Masaya wrote:
>>We are debugging a custom board designed based on the 405GP
>>(200MHz) and have a problem not being sent ECHO REPLY ping
>>packet from custom board to our PC via repeater hub on the
>>heavy traffic under 10Mbps and half duplex condition.
>>We used the latest version of ibm_ocp LAN device driver at
>>that time from kernel 2.4.21-pre3 and ported it to work on
>>the kernel 2.4.18 because it costs many time to boot our
>>custom board on the latest one. The board works fine unless
>>not be such a case.
>
>
>> - Logic analyzer captured the same ping packet which was
>> already been captured by LAN analyzer between PHY(Intel
>> LXT971A) and EMAC. It shows ECHO REQUEST was reached just
>> before the EMAC.
>
>
>If other obvious _software_ errors were eliminated (like incorrect
>duplex/speed settings etc) you can check _hardware_ related problems:
>
>Please, check the quality of the clock between PHY and EMAC (MII clock).
>We had some problems with this Intel PHY and IBM 440GP when PHY generated
>clock was _slightly_ out of spec for IBM CPU.
>
We have already been checked the quality of the clock and it
was good. However we'll check again. Today, we tried to duplicate
the ping lost case by another custom board designed based on 405GP
and no ping lost occurred on the same line loading condition what
we investigated before. The difference is hardware design (wiring
etc.) and SW(OS, LAN device driver etc.). Each custom board is
designed for another product. Therefor we'll check the difference
at the point of hardware(waveform etc.) and SW(configuration of
EMAC/PHY/MAL and so on).
>You can try to increase MII drive strength in LXT971A Digital Config
>register (26), write 0x0800 to it.
>
>Make sure that your design uses _crystal_ based oscillator for PHY
>clock, not PLL based. This is _general_ observation regarding PHY clock
>in any designs (not just 4xx based)
>
Fortunately, we have designed the same way what you've adviced.
Datasheet said don't use PLL. Before, 100Mbps transfer mode which
clock line is 25MHz was succeded. While the 10Mbps is 2.5MHz.
Therefore we think there is no matter about quality of clock.
Anyway we'll investigate again.
Regards, Kishinami
-----
KISHINAMI Masaya
Fujitsu Limited (Japan)
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-03-05 10:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-28 12:27 405GP Networking issue KISHINAMI Masaya
2003-02-28 13:59 ` AW: " Georg Klug
2003-02-28 14:54 ` KISHINAMI Masaya
2003-02-28 19:08 ` Eugene Surovegin
2003-03-05 10:37 ` KISHINAMI Masaya [this message]
2003-03-05 11:11 ` How to load vmlinux in IBM405 Redwood-6 board(Teference board) Rakesh Jagota
2003-04-14 10:44 ` 405GP Networking issue KISHINAMI Masaya
-- strict thread matches above, loose matches on Subject: below --
2003-02-28 15:41 Mark Wisner
2003-03-04 14:46 ` KISHINAMI Masaya
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=200303051037.AA02365@kishinami.cs.fujitsu.co.jp \
--to=kishinami@cs.fujitsu.co.jp \
--cc=ebs@ebshome.net \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).