From: Gary Thomas <gthomas@redhat.com>
To: "Simpkins, Andy" <Andy.Simpkins@Transcomm.uk.com>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: RE: [ECOS] memory map question
Date: Fri, 24 Aug 2001 07:08:00 -0000 [thread overview]
Message-ID: <XFMail.20010824081628.gthomas@redhat.com> (raw)
In-Reply-To: <919A3A7F776FD311AFD600508B44A7F3017959A7@ramhqlon.transcomm.uk.com>
On 24-Aug-2001 Simpkins, Andy wrote:
> Hi there,
>
> I am trying to map some data to a specific address in FLASH on my custom
> target board (ARM7TDMI core)
>
> The data is defined as
>
> unsigned char globalArchive[] __attribute__ ((section (".ivoryDataStore")))
> =
> {0x04, 0x18, 0x00, 0x00, 0x81);
>
>
> I have added the following to arm.ld
>
>#define SECTION_ivoryDataStore(_region_, _vma_, _lma_) \
> .ivoryDataStore _vma_ : _lma_ \
> { FORCE_OUTPUT; *(.ivoryDataStore) } \
> > _region_
>
> And have attempted to define ivoryDataStore in my memory map of the config
> tool (1.3.1)
> I kind of hoped that the name would have shown up in the drop down box for
> Linker-defined, as it didn't I had to specify it as user defined...
>
> i.e.
> Name - User-defined: ivoryDataStore
> - Known Size: 0x2000
> Final Location (VMA) - Absolute: 0xe0000
>
> however when I compile my code I get the following :
>
>
> arm-elf-gcc *.o ../../API/*/*.o -L /i/eCOSbuilds/a166_install/lib/
> -Ttarget.ld -nostdlib -Xlinker -Map -Xlinker mapfile.txt
> /tools/H-i686-pc-cygwin/arm-elf/bin/ld: warning: no memory region specified
> for
> section `.ivoryDataStore'
Does .ivoryDataStore end up in your "target.ld" file (the linker script)? If
not, it's a problem with the macros & sections.
next prev parent reply other threads:[~2001-08-24 7:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-24 2:35 Simpkins, Andy
2001-08-24 7:08 ` Gary Thomas [this message]
[not found] <919A3A7F776FD311AFD600508B44A7F3017959DB@ramhqlon.transcomm.uk.com>
2001-08-24 8:12 ` Gary Thomas
[not found] <XFMail.20010824092104.gthomas@redhat.com>
2001-08-24 8:40 ` John Dallaway
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=XFMail.20010824081628.gthomas@redhat.com \
--to=gthomas@redhat.com \
--cc=Andy.Simpkins@Transcomm.uk.com \
--cc=ecos-discuss@sourceware.cygnus.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).