From: annamaya <annamaya@yahoo.com>
To: Dan Malek <dan@embeddededge.com>
Cc: Sam Song <samlinuxppc@yahoo.com.cn>, linuxppc-embedded@ozlabs.org
Subject: Re: Booting Linux using a PlanetCore BootLoader
Date: Thu, 14 Oct 2004 08:53:25 -0700 (PDT) [thread overview]
Message-ID: <20041014155325.57264.qmail@web53808.mail.yahoo.com> (raw)
In-Reply-To: <D0DCDC9C-1D69-11D9-88FA-003065F9B7DC@embeddededge.com>
I cant believe I was stupid enough to beleive that the
user's manual of an eval board was giving me the
correct information.
The problem turned out to be that the FCC controllers
were not assigned to the ports that the manual stated.
They were switched. I was configuring the wrong FCC
controllers. Doh!
By manually looking at the FCC registers during tftp
transfers from the bootloader, I was able to figure
out that the controller in use for the port was
different from the one that the manual was telling me.
I appreciate all the help that I got in solving my
weird problems. Special thanks to Dan. I think I am
almost done supporting the EP8280 in the Linux Kernel
from denx.
--- Dan Malek <dan@embeddededge.com> wrote:
>
> On Oct 13, 2004, at 5:23 PM, annamaya wrote:
>
> > I verified that the TX and RX clock signals are
> > correct and the CMXFCR route register is
> programmed
> > correctly for FCC2. I still see TX timeout errors.
> I
> > am stumped. :-(
>
> Do you have the FCC MAC set up properly for
> full or half duplex? If you don't have MDIO
> working,
> you are going to have to force this to the proper
> setting for your switch. I mentioned this in a
> previous message.
>
> If that doesn't work, take a look at the CPM
> memory map and ensure the "special" FCC
> area is mapped properly. I don't remember
> if the 8280 has the "big" CPM like the 8260,
> or the small one like the 8272. There is
> a configuration option that moves this memory
> address for the FCC fifos and special buffers.
>
>
> -- Dan
>
>
_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com
next prev parent reply other threads:[~2004-10-14 16:01 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20041012003339.B1EB92BDDA@ozlabs.org>
2004-10-12 1:12 ` Booting Linux using a PlanetCore BootLoader Sam Song
2004-10-12 21:02 ` annamaya
2004-10-12 21:26 ` Dan Malek
2004-10-13 14:49 ` annamaya
2004-10-13 16:07 ` Dan Malek
2004-10-13 18:06 ` annamaya
2004-10-13 19:21 ` annamaya
2004-10-13 21:19 ` Dan Malek
2004-10-13 21:23 ` annamaya
2004-10-13 22:47 ` Dan Malek
2004-10-14 15:53 ` annamaya [this message]
2004-10-14 16:45 ` Dan Malek
2004-10-14 18:10 ` annamaya
2004-10-14 20:54 ` Wolfgang Denk
2004-10-16 0:16 ` Sam Song
2004-10-12 1:36 ` linux 2.4.27 for 8xx? Sam Song
2004-10-11 16:04 Booting Linux using a PlanetCore BootLoader annamaya
2004-10-11 16:38 ` Dan Malek
2004-10-11 17:33 ` annamaya
2004-10-11 18:52 ` Dan Malek
2004-10-11 17:50 ` annamaya
2004-10-11 18:15 ` Tom Rini
2004-10-11 18:38 ` annamaya
2004-10-11 18:47 ` Tom Rini
2004-10-11 21:18 ` annamaya
2004-10-11 21:44 ` Tom Rini
2004-10-11 22:52 ` annamaya
2004-10-11 18:55 ` Dan Malek
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=20041014155325.57264.qmail@web53808.mail.yahoo.com \
--to=annamaya@yahoo.com \
--cc=dan@embeddededge.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=samlinuxppc@yahoo.com.cn \
/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).