From: "Agarwal, Lomesh" <lomesh.agarwal@intel.com>
To: "'Jonathan Larmour'" <jlarmour@redhat.com>
Cc: eCos Discuss <ecos-discuss@sources.redhat.com>
Subject: RE: [ECOS] Memory layout
Date: Wed, 10 Apr 2002 15:31:00 -0000 [thread overview]
Message-ID: <01BDB7EEF8D4D3119D95009027AE999512F65F2E@FMSMSX33> (raw)
During startup my flash is at 0 then I unalias it. After unaliasing flash
sits at 0xc4000000 and RAM sits at 0.
What about this:
MEMORY
{
ram : ORIGIN = 0x00000000, LENGTH = 0x10000000
rom : ORIGIN = 0xc4000000, LENGTH = 0x01000000
}
SECTIONS
{
SECTIONS_BEGIN
SECTION_rom_vectors (ram, 0x00000000, LMA_EQ_VMA) // vector page gets
remapped from ROM to RAM
SECTION_text (ram, 0x00002000, LMA_EQ_VMA)
SECTION_fini (rom, ALIGN (0x4), LMA_EQ_VMA)
SECTION_rodata (rom, ALIGN (0x4), LMA_EQ_VMA)
SECTION_rodata1 (rom, ALIGN (0x4), LMA_EQ_VMA)
SECTION_fixup (rom, ALIGN (0x4), LMA_EQ_VMA)
SECTION_gcc_except_table (rom, ALIGN (0x4), LMA_EQ_VMA)
SECTION_fixed_vectors (rom, 0x20, LMA_EQ_VMA)
SECTION_data (ram, 0xA000, FOLLOWING (.gcc_except_table))
SECTION_bss (ram, ALIGN (0x4), LMA_EQ_VMA)
CYG_LABEL_DEFN(__heap1) = ALIGN (0x8);
// CYG_LABEL_DEFN(__pci_window) = 0xf00000; . =
CYG_LABEL_DEFN(__pci_window) + 0x100000;
SECTIONS_END
}
-----Original Message-----
From: Jonathan Larmour [mailto:jlarmour@redhat.com]
Sent: Wednesday, April 10, 2002 3:22 PM
To: Agarwal, Lomesh
Cc: eCos Discuss
Subject: Re: [ECOS] Memory layout
"Agarwal, Lomesh" wrote:
>
> Actually I copied and pasted the wrong file.
> My rom.ldi file is as follows:
> MEMORY
> {
> ram : ORIGIN = 0x00000000, LENGTH = 0x10000000
> rom : ORIGIN = 0x00000000, LENGTH = 0x01000000
> }
These shouldn't overlap. The comments I wrote before about using the
unaliased addresses still holds, so almost certainly your ROM address above
should be different and your platform start up code needs to be
appropriately written to do the unaliasing/remapping.
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || 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
next reply other threads:[~2002-04-10 22:31 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-10 15:31 Agarwal, Lomesh [this message]
2002-04-10 17:39 ` Jonathan Larmour
-- strict thread matches above, loose matches on Subject: below --
2008-04-10 21:35 Syed Ismail
2007-10-29 14:13 [ECOS] memory layout Syed Ismail
2007-10-29 14:18 ` Andrew Lunn
2003-10-08 14:29 [ECOS] Memory Layout James Yates
2003-09-18 7:31 [ECOS] Memory layout Matthieu.GIRARDIN
2002-11-18 19:44 [ECOS] memory layout AL Chane
2002-10-30 9:55 Schumacher, Gordon
2002-11-04 20:37 ` Jonathan Larmour
2002-10-30 1:09 AL Chane
2002-10-30 4:52 ` Chris Garry
2002-04-10 18:23 [ECOS] Memory layout Agarwal, Lomesh
2002-04-10 18:18 Agarwal, Lomesh
2002-04-11 18:03 ` Jonathan Larmour
2002-04-10 14:01 Agarwal, Lomesh
2002-04-10 15:22 ` Jonathan Larmour
2002-04-07 16:14 Agarwal, Lomesh
2002-04-10 13:51 ` Jonathan Larmour
2001-04-18 2:01 [ECOS] Memory Layout james chen
2001-04-18 5:24 ` Gary Thomas
2001-04-18 18:05 ` james chen
2001-04-19 5:12 ` Gary Thomas
2001-04-19 17:37 ` james chen
2001-04-19 17:48 ` Gary Thomas
2001-01-23 22:51 [ECOS] memory layout Natarajan, Mekala (CTS)
2001-01-23 23:46 ` Jesper Skov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=01BDB7EEF8D4D3119D95009027AE999512F65F2E@FMSMSX33 \
--to=lomesh.agarwal@intel.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=jlarmour@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).