This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: interrupt/virtual vectors confusion
- From: Andrew Lunn <andrew at lunn dot ch>
- To: Matt Sartori <msartori at hanoverdisplays dot com>
- Cc: eCos Disuss <ecos-discuss at ecos dot sourceware dot org>
- Date: Tue, 16 Aug 2005 17:21:00 +0200
- Subject: Re: [ECOS] interrupt/virtual vectors confusion
- References: <F9885E669725F248A1F6DB9109FDD67905E4D7@Molly.hanover.local>
> >You probably need to change this so that it runs in user flash boot
> >mode. If you don't have RAM at 0x0 there is no way to change the
> >vectors. I expect if you run the eCos tests which test interrupts they
> >will fail.
> >
>
> And booting in RAM mode Redboot would still work because the first thing
> it does is copy itself into RAM? My current Redboot setup is running in
> ROM mode (CYG_HAL_STARTUP == ROM). Presumably that would need changing
> to ROMRAM then?
It should still be able to run in ROM. It just need to take care when
the ROM is remapped out from 0x0 that it is already running from the
mapping at the higher address space. You will find the existing ARM
platforms do this. What is actually quite common is that the reset
vector jumps straight into the high address mapping.
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