This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
memory layout and vector location
- To: ecos-discuss at sourceware dot cygnus dot com
- Subject: [ECOS] memory layout and vector location
- From: Arnaud Mouiche <arnaud dot mouiche at inventel dot fr>
- Date: Mon, 06 Aug 2001 17:24:24 +0200
Hi!
I'm looking at vector.S file for arm processor. Section layout isn't so
clear for me ...
- How is define the startup section. Is it the 'rom_vectors' section ? but
we don't find 'rom_vectors' section in vector.s , we just have a section
named '.vectors' which, indeed, call reset_vector (that what we want)
- What is the real aim of '.fixed vectors'. As I understand, it's a way to
told the ROM monitor (for ROM startup) what kind of call do when an
exception rise. Most part of the time, it seems that '.fixed_vectors'
address is the same that 'vectors' address (i.e. 0x20 of ram). But what
happened if the starting point of our program is not 0x00 of the RAM but
something else, as in this case, there is no relation between
'.fixed_vectors' address and 'vectors' address ?
- during startup (between LED 5 and LED 4), we copy the
'exception_handlers' table from '__exception_handlers' address to address
0x0. But If address 0x00 is map to ROM and if we don't have MMU to make RAM
start at address 0x0, how could it work ?
Do I have to change 'vector.S' file to avoid this problems ?
Thanks
Arnaud MOUICHE