public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: ken king <kknhuntsville@yahoo.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] PowerPC FEC problems
Date: Fri, 06 May 2005 08:42:00 -0000	[thread overview]
Message-ID: <20050506084211.GA31557@lunn.ch> (raw)
In-Reply-To: <20050506020233.87607.qmail@web60224.mail.yahoo.com>

On Thu, May 05, 2005 at 07:02:33PM -0700, ken king wrote:
> I have a custom MPC852T board. (note:
> Custom means porting RedBoot/eCOS and checking board
> out at same time!) I've gotten RedBoot up and
> almost everything works except ethernet. I
> started with if_fec.c. The MII interface seems to
> be working correctly, MDC clock is correct
> frequency, reasionable data back and forth, etc.
> 
> When running gdb and a BDM I get a
> "Trace/breakpoint" when there is no break point
> set -- generally a bad thing! I tracked it down
> to:
> 
> fec_eth_send()
> {
> ...........
> 	/* comment out next line --
> 	** no bad trace/breakpoint*/
> 	qi->fec->TxUpdate=0x10000;
> ......
> 	}
> 
> I've written some code to look at the FEC regs
> before and after the offending line of code.
> Before, everything looks good. After;
> 
> 1-- I_EVENT reg has EB_ERR set -- FEC encountered
> a bus error.
> 
> 2-- Eth Control Reg has eth disabled.
> 
> If I #define for buffer descriptors to be in
> external memory, then the Transfure Error Status
> Reg (TESR) has IEXT set indicating a /TEA signal
> was present during a external instruction fetch.
> /TEA is just connected to a pull-up resistor, I've
> looked at it with a scope - doesn't look shorted
> to anything.
> 
> So, Long-story-short I think I getting a bus error
> when the FEC DMA kicks off. Anybody seen this
> before? Any ideas? What else to look for?

Check the addresses you are using from receive and transmit buffers.
Do you remember to map the virtual addresses into bus addresses before
programming them into the ethernet device? Does memory realy exist at
the address? 

        Andrew

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2005-05-06  8:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-06  2:02 ken king
2005-05-06  8:42 ` Andrew Lunn [this message]
2005-05-06 11:44 ken king
2005-05-06 11:49 ` Andrew Lunn
2005-05-06 15:26 ken king
2005-05-06 15:49 ` Gary Thomas
2005-05-06 23:21 ken king
2005-05-07  0:10 ` Gary Thomas
2005-05-09 21:04 ken king

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=20050506084211.GA31557@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=kknhuntsville@yahoo.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).