linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Willy Jacobs <wn.jacobs@net.hcc.nl>
To: linuxppc-embedded@lists.linuxppc.org
Subject: FEC on MPC862P freezes CPM
Date: Mon, 12 May 2003 19:45:56 +0200	[thread overview]
Message-ID: <3EBFDDD4.5010707@net.hcc.nl> (raw)


We are using a MPC862P (XPC862PCZP80B, 2K26A silicon) in a system with
UTOPIA (master) and FEC simultaneously in UTOPIA muxed bus mode. The
processor runs at 50 MHz (CPM and bus). For references in the MPC862
Users' Manual, see figure 35-1 (page 35-4), table 41-6 (page 41-7), and
figure 42-3 (page 42-7). The FEC MII signals are mapped on PCMCIA port A.

For testing we are using Linux. The Linux console is mapped onto SCC3,
and SCC1 is used for ethernet. Initialization for SCC3 is done first,
followed by the initialization of the FEC (as described on paragraph
41.3 (page 41-8)): ECNTRL[FEC_PINMUX]=1; setup the buffer descriptors;
UTMODE[SPLIT]=0, PDPAR[UT]=1; PDPAR[8]=1 (MDII_MDC). A printk to SCC3 in
above situation will "freeze" the CPM in the transmit of the SCC3
buffers. More concrete it will never pass this while loop:
	while (bdp->cbd_sc & BD_SC_READY) ;
The UTIOPIA initialization will be done later.

With PDPAR[UT]=0 SCC3 and UTOPIA works without any problem.
Note that above CPM "freeze" problem also occurs using another RTOS
(VRTX) and a similar use of SCCs, FEC, and UTOPIA.

Is this problem known?
Is there another initialization sequence needed?
--
willy


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2003-05-12 17:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-12 17:45 Willy Jacobs [this message]
2003-05-13  8:55 ` FEC on MPC862P freezes CPM Alex Zeffertt
  -- strict thread matches above, loose matches on Subject: below --
2003-05-13 11:24 Eli Brin

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=3EBFDDD4.5010707@net.hcc.nl \
    --to=wn.jacobs@net.hcc.nl \
    --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).