This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
RE: interrupt/virtual vectors confusion
- From: Gary Thomas <gary at mlbassoc dot com>
- To: Matt Sartori <msartori at hanoverdisplays dot com>
- Cc: Andrew Lunn <andrew at lunn dot ch>,eCos Discussion <ecos-discuss at ecos dot sourceware dot org>
- Date: Tue, 16 Aug 2005 08:17:48 -0600
- Subject: RE: [ECOS] interrupt/virtual vectors confusion
- References: <F9885E669725F248A1F6DB9109FDD67905E4D2@Molly.hanover.local>
On Tue, 2005-08-16 at 15:06 +0100, Matt Sartori wrote:
> >Is Blinky an eCos RAM program? If so it should of taken over the
> >interrupt vectors from Redboot. Redboot should no longer be active
> >unless blinky actually calls into Redboot via the virtual vectors.
>
> Blinky is just a standalone program I decided to use as a test. The only
> change I've made to it to make it run is to link it directly into free
> ram so that I can run it after having loaded it from Redboot (with a
> load -r -m ymodem -b 0x20005b68).
> The reason I know that Redboot is handling (or at least that Redboot
> code is being called) the IRQ is that I put while(1){flash an led every
> second} at the top of hal_IRQ_handler and that it gets stuck there when
> I run Blinky.
Then, this is just as it should be :-) Unless you make Blinky into an
eCos program, which uses the HAL interrupt mechanisms, RedBoot is quite
happily going to try and handle the interrupt, 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