This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Question about memory management in ARM E7T with eCOS?
- From: Jonathan Larmour <jlarmour at redhat dot com>
- To: HuangQiang <jameshq at liverpool dot ac dot uk>
- Cc: eCos <ecos-discuss at sources dot redhat dot com>
- Date: Tue, 14 May 2002 22:07:01 +0100
- Subject: Re: [ECOS] Question about memory management in ARM E7T with eCOS?
- Organization: Red Hat UK Ltd.
- References: <KIEBICHBADHFCLGCKOPDMEPACLAA.jameshq@liv.ac.uk>
HuangQiang wrote:
>
> Hi all:
> While I am building the ecos library for ram startup and link with my
> program. I use arm-elf-objdump I saw the address is start from 0x00010000,
> why it is not start from the base 0x00000000? It seems the vector table is
> also start from 0x00010000, why it is not start from 0x00000000? (Isn't the
> reset vector for ARM is base on 0x00? why there is such difference?) (Is the
> address 0x00010000 specified by the linker script?)
>From 0 to 0x10000 is reserved for the ROM monitor. You can reclaim it if
you like, but then you won't be able to use the ROM monitor services for
e.g. debugging. To do that you configure your application with
CYGSEM_HAL_USE_ROM_MONITOR disabled, and then adjust your memory map to use
the memory from 0x0 (similar to how the ROM startup does).
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
--[ "You can complain because roses have thorns, or you ]--
--[ can rejoice because thorns have roses." -Lincoln ]-- Opinions==mine
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss