From: Ruedi.Hofer@ascom.ch
To: pohland@snom.de, linuxppc-embedded@lists.linuxppc.org
Cc: kernel@linux01.hasler.ascom.ch
Subject: Antwort: Re: Antwort: Re: FEC on the MPC860T
Date: Tue, 02 May 2000 16:08:58 +0100 (CED) [thread overview]
Message-ID: <0FTX0022ORB1NU@pmdf-it.hasler.ascom.ch> (raw)
[-- Attachment #1: Type: TEXT/PLAIN, Size: 2046 bytes --]
Hi
Well, both led's are working. When I ping from my host to the target,
I can only see the RX led blink. However, after some time I see
the host's MAC address in the arp table on the target.
When I ping from the target to the host, both RX and TX leds blink.
It seems as if the target only accepts broadcast MAC frames....
Any further idea?
What kind of kernel are you using? 2.2.13? Montavista?
Ruedi
pohland@snom.de on 02.05.2000 14:35:34
An: Ruedi.Hofer@ascom.ch @ MailGate
Kopie:
Thema: Re: Antwort: Re: MPC860T
Ruedi.Hofer@ascom.ch wrote:
>
> Hi Nicolas
Looks like you are progressing ...
Do not enable DEBUG messages - I believe that they f... things up.
Do you see the RX and TX leds working ?
Cheers,
Nicolas
>
> Thanx for the file. It gets me a bit further...
>
> When I output the event register in case of an interrupt, I get:
>
> while booting:
>
> eth0: CPM ENET Version 0.2, 08:00:3e:26:15:59
> disabling IRQ7.
> FEC int: 0x00a00000
> eth1: FEC ENET Version 0.1, FEC int: 0x00a00000
> FEC int: 0x00a00000
> FEC int: 0x00a00000
> FEC int: 0x00a00000
> fec: link up
> 08:FEC int: 0x00a00000
> FEC int: 0x00a00000
> fec: 10 Mbps, Half-Duplex
> FEC int: 0x00a00000
> 00:3e:26:15:5a
> Sending BOOTP and RARP requests....
>
> -> U-Bus error ?!? Somehow a cache problem? Which kernel are you using?
>
> and afterwards:
>
> sh-2.03# ping 10.1.30.1
> PING 10.1.30.1 (10.1.30.1): 56 data bytes
> FEC int: 0x0c200000
> FEC int: 0x0c200000
> FEC int: 0x0c200000
> FEC int: 0x0c200000
> FEC int: 0x0c200000
> FEC int: 0x0c200000
>
> 0x0c...: Data sent ok
> 0x002..: Does NOT exist in my databook!!!!
>
> It seems that I'm able to send data, but can't receive any.
>
> Ideas?
>
> Ruedi
>
> pohland@snom.de on 28.04.2000 18:03:39
> An: Ruedi.Hofer@ascom.ch @ MailGate
> Kopie:
> Thema: Re: MPC860T
>
> This is what I came up with when I fixed the bugs ... only 10 MBit/s. If
> you improve it
> please send it back. My BCSR regs are manipulated in a different area.
> You might have to add
> this code.
>
> Cheers,
> Nicolas
reply other threads:[~2000-05-02 15:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=0FTX0022ORB1NU@pmdf-it.hasler.ascom.ch \
--to=ruedi.hofer@ascom.ch \
--cc=kernel@linux01.hasler.ascom.ch \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=pohland@snom.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 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).