This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Int Vectors and Build Problem
- From: Nick Garnett <nickg at ecoscentric dot com>
- To: LeoM at 3rdRootDSP dot Com
- Cc: Ecos EcosList <ecos-discuss at sources dot redhat dot com>
- Date: 26 Mar 2004 13:47:42 +0000
- Subject: Re: [ECOS] Int Vectors and Build Problem
- References: <20040326123110.86517.qmail@web40807.mail.yahoo.com>
Leo McManus <leomcmanusir@yahoo.com> writes:
> ARM720T on ARM Integrator board.
>
> After building my eCos executable, I can see in my Srecord and with my GDB,
> that the int vectors, which are loaded at download time to address 0x40000 and
> later copied to address 0x0, point to address 0xE59FF018, which holds no
> memory. This is worked out at compilation time.
Those are not interrupt routine addresses, they are instructions. The
CPU executes the instruction at the vector location when an exception
occurs. In eCos the instructions we use just pick up an address from
[PC+32] and jump to it. So the interrupt vector addresses are in the
32 bytes following the hardware vectors.
--
Nick Garnett eCos Kernel Architect
http://www.ecoscentric.com The eCos and RedBoot experts
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss