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: Leo McManus <leomcmanusir at yahoo dot com>
- To: ecos-discuss at sources dot redhat dot com
- Date: Mon, 29 Mar 2004 15:06:40 +0100 (BST)
- Subject: Re: [ECOS] Int Vectors and Build Problem
- Reply-to: LeoM at 3rdRootDSP dot Com
You ijeet, McManus,
0xe59ff018 disassembles to ldr pc,[pc, #24]
Sorry!
Thanks
Leo
>>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
=====
Mobile Belgium: +32 (0)495 89 59 65
Contact in France: +33 (0)476 275661
Registered Linux User Number 205935.
http://counter.li.org.
___________________________________________________________
WIN FREE WORLDWIDE FLIGHTS - nominate a cafe in the Yahoo! Mail Internet Cafe Awards www.yahoo.co.uk/internetcafes
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss