From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1750 invoked by alias); 6 May 2005 02:02:38 -0000 Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Received: (qmail 721 invoked from network); 6 May 2005 02:02:33 -0000 Received: from unknown (HELO web60224.mail.yahoo.com) (209.73.178.112) by sourceware.org with SMTP; 6 May 2005 02:02:33 -0000 Received: (qmail 87609 invoked by uid 60001); 6 May 2005 02:02:33 -0000 Message-ID: <20050506020233.87607.qmail@web60224.mail.yahoo.com> Received: from [69.73.59.128] by web60224.mail.yahoo.com via HTTP; Thu, 05 May 2005 19:02:33 PDT Date: Fri, 06 May 2005 02:02:00 -0000 From: ken king To: ecos-discuss@ecos.sourceware.org In-Reply-To: 6667 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: [ECOS] PowerPC FEC problems X-SW-Source: 2005-05/txt/msg00051.txt.bz2 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? TIA, KK PS Im think of giving up on this FEC thing for a while. I have one more PHY connected to a SCC, would you recomend I start with the Adder or QUICC eth driver? Discover Yahoo! Find restaurants, movies, travel and more fun for the weekend. Check it out! http://discover.yahoo.com/weekend.html -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss