This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Timecritical interrupt-debuging ... printf in DSR's ... Cyg_Scheduler_Implementation::rem_thread() ... cyg_assert_fail()
- From: Andrew Lunn <andrew at lunn dot ch>
- To: Fabian Scheler <fabian dot scheler at gmail dot com>
- Cc: Oliver Munz <oli at snr dot ch>, ecos-discuss at sources dot redhat dot com
- Date: Tue, 5 Jul 2005 09:27:46 +0200
- Subject: Re: [ECOS] Timecritical interrupt-debuging ... printf in DSR's ... Cyg_Scheduler_Implementation::rem_thread() ... cyg_assert_fail()
- References: <006101c580e1$b3a48df0$5e188481@cadpad> <69dd805e05070500163304862@mail.gmail.com>
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
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss