From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30774 invoked by alias); 5 Jul 2005 11:23:46 -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 30753 invoked by uid 22791); 5 Jul 2005 11:23:39 -0000 Received: from londo.lunn.ch (HELO londo.lunn.ch) (80.238.139.98) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Tue, 05 Jul 2005 11:23:39 +0000 Received: from lunn by londo.lunn.ch with local (Exim 3.36 #1 (Debian)) id 1DplWT-0002tF-00; Tue, 05 Jul 2005 13:23:29 +0200 Date: Tue, 05 Jul 2005 11:23:00 -0000 To: "oliver munz @ s p e a g" Cc: Fabian Scheler , Andrew Lunn , ecos-discuss@sources.redhat.com Message-ID: <20050705112329.GD30398@lunn.ch> Mail-Followup-To: "oliver munz @ s p e a g" , Fabian Scheler , Andrew Lunn , ecos-discuss@sources.redhat.com References: <006101c580e1$b3a48df0$5e188481@cadpad> <69dd805e05070500163304862@mail.gmail.com> <20050705072746.GC30398@lunn.ch> <00ae01c58145$fae9ccc0$5e188481@cadpad> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <00ae01c58145$fae9ccc0$5e188481@cadpad> User-Agent: Mutt/1.5.9i From: Andrew Lunn Subject: Re: [ECOS] Timecritical interrupt-debuging ... printf in DSR's ... Cyg_Scheduler_Implementation::rem_thread() ... cyg_assert_fail() X-SW-Source: 2005-07/txt/msg00045.txt.bz2 On Tue, Jul 05, 2005 at 11:43:20AM +0200, oliver munz @ s p e a g wrote: > > ----- Original Message ----- > From: "Andrew Lunn" > To: "Fabian Scheler" > Cc: "Oliver Munz" ; > Sent: Tuesday, July 05, 2005 9:27 AM > Subject: Re: [ECOS] Timecritical interrupt-debuging ... printf in DSR's ... > Cyg_Scheduler_Implementation::rem_thread() ... cyg_assert_fail() > > > >On Tue, Jul 05, 2005 at 09:16:44AM +0200, Fabian Scheler wrote: > >>Hi, > >> > >>> I don't know if it's allowed to use the buffered IO from ISR and DSR's. > >>> If > >>> everybody know's if it should work or not in threory, let me know.... > >>> Im > >>> also intressted in other hints how to debug driveres... > >> > >>well, I don't know the exact implementation of buffered IO in eCos, > >>but buffered IO always is blocking (if you want to ensure that no data > >>gets lost), and blokcing operations are never allowed within an ISR or > >>a DSR. > > > >Correct. > > > >You can use the infrastructure trace functions and instramentation > >functions which are safe when writting to a buffer. Or you can > >implement your own buffering which is ISR/DSR safe. > > > > Andrew > > Thanks a lot... > > Then I can try the option "CYGOPT_IO_SERIAL_SUPPORT_NONBLOCKING" (and hope > there rise no other problems)... Nope, this will not help. Thats a different meaning of none blocking. > If I use the "CYG_TRACE0(bool, msg)" function family, then I have to use > "CYG_TRACE_PRINT()" if I want control over the timing, because > "CYG_TRACE_PRINT()" blocks until the hole trace-buffer ist written to > diag_write(). Right? Correct. 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