From: "Tales Toledo" <toledo.tales@gmail.com>
To: "Gary Thomas" <gary@mlbassoc.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Re: PowerPC FEC doesn't ping
Date: Tue, 31 Jul 2007 20:50:00 -0000 [thread overview]
Message-ID: <2308fb0f0707311350q1a32d649m894e98473b0f16f3@mail.gmail.com> (raw)
In-Reply-To: <46AB49B7.1070105@mlbassoc.com>
On 7/28/07, Gary Thomas <gary@mlbassoc.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Tales Toledo wrote:
> > On 7/27/07, Tales Toledo <toledo.tales@gmail.com> wrote:
> >> Hi,
> >>
> >> is there some additional special cdl_option for FEC?
> >>
> >> I can get ** FEC Info: PHY LINK already UP \n message from redboot
> >> boot, configure ip_addresses, but I can get a reply from host or even
> >> reply its requests because FEC can't send packages (I have checked
> >> with wireshark).
> >
> > I also check TXD0 close to phy with an oscilloscope and seems that
> > PowerPC FEC (hw is fine because it works with another sw) doesn't
> > transmit any package.
> >
> > I can see the debug messages at redboot console
> >
> > RedBoot> ping -h 192.168.1.100
> > Ethernet send:
> > 0000545C: FF FF FF FF FF FF 7C 71 43 A6 7C 92 08 06 |......|qC.|... |
> > Ethernet send:
> > 0000545C: FF FF FF FF FF FF 7C 71 43 A6 7C 92 08 06 |......|qC.|... |
> > Ethernet send:
> > 0000545C: FF FF FF FF FF FF 7C 71 43 A6 7C 92 08 06 |......|qC.|... |
> >
> > Is there some low level debug for FEC driver to address this issue?
>
> Check your I/O port configuration - this is different
> for every processor (852 vs 87x vs ...). If it's not
> right, the FEC will not be connected to the outside
> world!
You're right. I'm using MPC880 and FEC pins are spread over all ports.
At this moment I can't contribute with a patch because I'm working in
a proprietary hardware. I will try to get Adder885 board and ask them
if we can add their eCos port to cvs and I can also add any changes I
made.
Anyway, just for close this subject and register here in other to help
others, here is a brief description of changes:
@ppc8xx.h
Add description for port E
/* Port E */
volatile unsigned long pio_pedir; /* port e data direction reg */
volatile unsigned long pio_pepar; /* port e pin assignment reg */
volatile unsigned long pio_peso; /* port e special options reg */
volatile unsigned long pio_peodr; /* port e open drain reg */
volatile unsigned long pio_pedat; /* port e data reg */
/* CP Timing Register */
volatile unsigned long cp_cptr; /* RMII timing register */
@ if_fec.h
Add port configuration
#if defined (CYGHWR_HAL_POWERPC_MPC8XX_880)
// MII1: TXD0, TXER, TXD1, RXER, RXDV, RXD0, RXD1
eppc->pio_papar |= 0xF830;
eppc->pio_padir &= ~0xF000;
eppc->pio_padir |= 0x0830;
// MII1: TXCLK, RXD3
eppc->pip_pbpar |= 0x00001001;
eppc->pip_pbdir &= ~0x00001001;
// MII1: TXD3, TXD2
eppc->pio_pcpar |= 0x000C;
eppc->pio_pcdir &= ~0x000C;
// MII1: MDC
eppc->pio_pdpar |= 0x0080;
eppc->pio_pddir &= ~0x0080;
// MII1: RXCLK, RXD2
eppc->pio_pepar |= 0x00000003;
eppc->pio_pedir |= 0x00000003;
eppc->pio_peso &= ~0x00000003;
#else
eppc->pio_pdpar = 0x1FFF;
CYGARC_MFSPR( CYGARC_REG_PVR, proc_rev );
#define PROC_REVB 0x0020
if ((proc_rev & 0x0000FFFF) == PROC_REVB) {
eppc->pio_pddir = 0x1C58;
} else {
eppc->pio_pddir = 0x1FFF;
}
#endif // CYGHWR_HAL_POWERPC_MPC8XX_880
Thx,
TT.
>
> - --
> - ------------------------------------------------------------
> Gary Thomas | Consulting for the
> MLB Associates | Embedded world
> - ------------------------------------------------------------
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
>
> iD8DBQFGq0m3maKbSsQGV8ARAvT4AJ903J0ueUeWPDgcrbF9EOaT+tUCRQCggLww
> yREAzE8vPtpGPpgcNskl2zY=
> =nP25
> -----END PGP SIGNATURE-----
>
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2007-07-31 20:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-27 15:07 [ECOS] " Tales Toledo
2007-07-27 20:00 ` [ECOS] " Tales Toledo
2007-07-28 13:07 ` Andrew Lunn
2007-07-28 13:50 ` Gary Thomas
2007-07-29 15:33 ` Rick Davis
2007-07-31 20:50 ` Tales Toledo [this message]
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=2308fb0f0707311350q1a32d649m894e98473b0f16f3@mail.gmail.com \
--to=toledo.tales@gmail.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=gary@mlbassoc.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).