From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4285 invoked by alias); 2 Sep 2009 09:01:54 -0000 Received: (qmail 3374 invoked by uid 22791); 2 Sep 2009 09:01:52 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from nw-ex-010.asplogon.com (HELO NW-EX-010.asplogon.com) (193.19.65.29) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 02 Sep 2009 09:01:44 +0000 Received: from nw-ex-004.asplogon.com ([172.30.128.211]) by NW-EX-010.asplogon.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 2 Sep 2009 11:01:41 +0200 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Date: Wed, 02 Sep 2009 09:01:00 -0000 Message-ID: <97F68B92952DDA40A6494655C887603BB79C6D@nw-ex-004.asplogon.com> In-reply-to: References: <97F68B92952DDA40A6494655C887603BB79B1F@nw-ex-004.asplogon.com> <97F68B92952DDA40A6494655C887603BB79BD9@nw-ex-004.asplogon.com> <4A9D3CBF.6010305@mlbassoc.com> <97F68B92952DDA40A6494655C887603B4EB580@nw-ex-004.asplogon.com> From: "Alex Lindeijer" To: "Christophe Coutand" Cc: Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: RE: [ECOS] Ethernet traffic causing loss of bytes on UART X-SW-Source: 2009-09/txt/msg00035.txt.bz2 Yes in case og an interrupt from the PIC it doing only that. In case of a CPM interupt it for acknowledges it in the CPM and then the PIC(EOI) /Alex -----Original Message----- From: Christophe Coutand [mailto:ccoutand@stmi.com]=20 Sent: 1. september 2009 21:02 To: Alex Lindeijer Cc: ecos-discuss@sourceware.org Subject: RE: [ECOS] Ethernet traffic causing loss of bytes on UART Hi Alex, I'm curious, what does the acknowledge routine do? Is it just writing to the End Of Interrupt (EOI) register?=20 Christophe -----Original Message----- From: ecos-discuss-owner@ecos.sourceware.org [mailto:ecos-discuss-owner@ecos.sourceware.org] On Behalf Of Alex Lindeijer Sent: Tuesday, September 01, 2009 6:30 PM To: Gary Thomas Cc: ecos-discuss@sourceware.org Subject: SV: [ECOS] Ethernet traffic causing loss of bytes on UART Hi When we were missing bytes on the serial port and we pulled the ethernet cable out, we received all bytes on the serial port. First we tried increasing the serial port interrupt priority since it actually tolerates less interupt latency than the ethernet port. I'll have to study the MPC8541 reference guide more later but as we understand it: The interupt controller in the MPC8541 needs to have the interrupt acknowledge before it handles any new interrupts(like from the UART). So, in the ISR of the ethernet driver we mask the ethernet interrupt and acknowledge the interrupt which allows the interrupt controller to process new interupts /call ISRs. In the DSR of the ethernet driver we service the ethernet interrupt and unmask it when done. If we acknowledge the interrupt before leaving the DSR, no other interrupt given by the interrupt controller whilst processing the ethernet frames. That is why we lost bytes on the serial port. At least that is our theory, which I have to confirm by checking the documentation closer. In pratice we are now receiving/sending traffic on both ethernet and serial port undisturbed.=20 This also the we I have seen it done in other drivers (also an alternative tsec driver). This is we think it works. But I appreciate any comments and tips. Interupt handling and driver software is certainly not my strongest point. Cheers Alex ________________________________ Fra: Gary Thomas [mailto:gary@mlbassoc.com] Sendt: ti 01.09.2009 17:24 Til: Alex Lindeijer Kopi: ecos-discuss@sourceware.org Emne: Re: [ECOS] Ethernet traffic causing loss of bytes on UART On 09/01/2009 08:36 AM, Alex Lindeijer wrote: > Hi All > This problem is fixed. The drivers that came with our Python MPC8541 > eval board, acknowledged the ethernet interrput in the DSR (after > processing!) and not in the ISR. > It seems to work fine now. How does that have anything to do with losing bytes on the UART? BTW, IMO it's not safe/proper to acknowledge the interrupt in the ISR. The ISR masks the interrupt and only after the network stack has fully processed the data is it acknowledged and unmasked. Acking the interrupt in the ISR could lead to missing some interrupts. > -----Original Message----- > From: ecos-discuss-owner@ecos.sourceware.org > [mailto:ecos-discuss-owner@ecos.sourceware.org] On Behalf Of Alex > Lindeijer > Sent: 1. september 2009 08:24 > To: ecos-discuss@sourceware.org > Subject: [ECOS] Ethernet traffic causing loss of bytes on UART > > Hi > We are running a serial port on 38400 baud and are seeing loss of Rx > bytes. When unplugging the ethernet cable we have no problems. > We are using a MPC8541, it has a PC16550D programming model for the > UART. I see that the driver uses the FIFO and reads until the FIFO is > empty. > The Ethernet driver is a tsec driver . > We encountered similar problems when writing to flash. We got some > verification/write errors with Ethernet traffic going. In that case we > masked the interrupts while writing to flash. But we don't want to do > that when receiving bytes on the serial port of course. > > Has anybody else encounter such problems? Any hints in were to look? We > have been looking into this now for some time and are getting a bit > desperate.....;-( > > Cheers > Alex Lindeijer > -- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------ --=20 Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss