This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: removing all interrupts code and data from RedBoot image
- From: Gary Thomas <gary at mlbassoc dot com>
- To: Elad Yosef <elad dot yosef at gmail dot com>
- Cc: ecos-discuss at ecos dot sourceware dot org
- Date: Thu, 05 Jan 2012 14:55:27 -0700
- Subject: Re: [ECOS] removing all interrupts code and data from RedBoot image
- References: <CAOFa9c3JqNyohwoHm7zP8RaqXBkznN2Q3L_9Azhm=W=xODm6EA@mail.gmail.com>
On 2012-01-05 14:03, Elad Yosef wrote:
Hi all,
I'm short in RAM& ROM for my Redboot run
What I want to do is to eliminate all the interrupts code and data.
In the hal_mon_init I'll register the exception handler to handle
interrupts (it will halt CPU since no interrupt is expected...)
Can someone give me points where to start?
Since RedBoot doesn't use interrupts, you may not find much to save.
What's your target architecture?
Have you looked at a load map to see what might be cut, etc?
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss