This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re-use RedBoot exceptions code in release eCos application
- From: Elad Yosef <elad dot yosef at gmail dot com>
- To: ecos-discuss at ecos dot sourceware dot org
- Date: Wed, 25 Jan 2012 16:29:53 +0200
- Subject: [ECOS] Re-use RedBoot exceptions code in release eCos application
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