From: Andrew Lunn <andrew@lunn.ch>
To: "oliver munz @ s p e a g" <munz@speag.ch>
Cc: Fabian Scheler <fabian.scheler@gmail.com>,
Andrew Lunn <andrew@lunn.ch>,
ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Timecritical interrupt-debuging ... printf in DSR's ... Cyg_Scheduler_Implementation::rem_thread() ... cyg_assert_fail()
Date: Tue, 05 Jul 2005 11:23:00 -0000 [thread overview]
Message-ID: <20050705112329.GD30398@lunn.ch> (raw)
In-Reply-To: <00ae01c58145$fae9ccc0$5e188481@cadpad>
On Tue, Jul 05, 2005 at 11:43:20AM +0200, oliver munz @ s p e a g wrote:
>
> ----- Original Message -----
> From: "Andrew Lunn" <andrew@lunn.ch>
> To: "Fabian Scheler" <fabian.scheler@gmail.com>
> Cc: "Oliver Munz" <oli@snr.ch>; <ecos-discuss@sources.redhat.com>
> 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
next prev parent reply other threads:[~2005-07-05 11:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-04 21:46 Oliver Munz
2005-07-05 7:17 ` Fabian Scheler
2005-07-05 7:28 ` Andrew Lunn
2005-07-05 9:43 ` oliver munz @ s p e a g
2005-07-05 11:23 ` Andrew Lunn [this message]
2005-07-06 7:31 ` Frank Pagliughi
2005-07-08 11:08 ` oliver munz @ s p e a g
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=20050705112329.GD30398@lunn.ch \
--to=andrew@lunn.ch \
--cc=ecos-discuss@sources.redhat.com \
--cc=fabian.scheler@gmail.com \
--cc=munz@speag.ch \
/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).