* [ECOS] Re-use RedBoot exceptions code in release eCos application
@ 2012-01-25 14:30 Elad Yosef
0 siblings, 0 replies; only message in thread
From: Elad Yosef @ 2012-01-25 14:30 UTC (permalink / raw)
To: ecos-discuss
Hi all,
I want to keep the RedBoot exception code to run also in the release
version of my eCos app.
I went over the code and linked all the exceptions handling parameters
into separate RAM segment apart from the RedBoot RAM segment.
The RedBoot RAM segment is later over-written by HW DMA during the
application execution.
My questions are regarding the comm channels.
- Does my application must inherit the comm channels in order the
keep the GDB functionality?
- I'm also curious about the prints coming out from my exception code
by using "diag_printf" will they work as normal?
(the _putc (print handler)- is linked in to the new RAM segment)
Thanks
Elad.
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2012-01-25 14:30 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-01-25 14:30 [ECOS] Re-use RedBoot exceptions code in release eCos application Elad Yosef
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).