public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Laurie Gellatly" <laurie.gellatly@netic.com>
To: "Gary Thomas" <gary@mlbassoc.com>
Cc: "Øyvind Harboe" <oyvind.harboe@zylin.com>,
	"eCos Discussion" <ecos-discuss@ecos.sourceware.org>
Subject: RE: [ECOS] Placing data at an absolute address
Date: Sun, 01 Apr 2007 21:42:00 -0000	[thread overview]
Message-ID: <OBEELMDOHGDFDEMJCJCJGEPILLAA.laurie.gellatly@netic.com> (raw)
In-Reply-To: <460FF1E7.9090104@mlbassoc.com>

Hi Gary,
Thanks for the response.
I did try using the "attribute" method but the allocated size for the
segment was always wrong (0).

I looked in the archives but without any success.

			...Laurie:{)

-----Original Message-----
From: Gary Thomas [mailto:gary@mlbassoc.com]
Sent: Monday, 2 April 2007 3:55 AM
To: Laurie Gellatly
Cc: Øyvind Harboe; eCos Discussion
Subject: Re: [ECOS] Placing data at an absolute address


Laurie Gellatly wrote:
> Hi All,
> For our eCos application, I'd like to place the MAC address at a
particular
> address in flash
> and have it loaded as part of storing Redboot into the flash.
> At production time, a script would be run that finds that address section
in
> redboot.elf and
> updates it before it is stored into the next unit.
> Finding the section in the elf is not the hard bit.
> I've tried adding a new section on the gcc command line and adding a
> variable into the
> C source which almost works except the section size is of length 0.
> How can I make the section 6 bytes long or is there a better way to do
this
> whole thing?

The best way would be to assign this data to a particular
section of its own, using "attribute".  Then in the linker
file, put that section at the desired physical address.

There was some discussion of this many years ago.  Some
trawling through the archives might find more clues.

--
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  parent reply	other threads:[~2007-04-01 21:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-26 18:55 [ECOS] ANNOUNCEMENT: www.ecosforge.net - a home for eCos packages and modules Øyvind Harboe
2007-04-01  7:52 ` [ECOS] Placing data at an absolute address Laurie Gellatly
2007-04-01 15:25   ` [ECOS] " Grant Edwards
2007-04-01 17:55   ` [ECOS] " Gary Thomas
2007-04-01 18:52     ` [ECOS] " Grant Edwards
2007-04-01 23:04       ` Laurie Gellatly
2007-04-01 21:42     ` Laurie Gellatly [this message]
2007-06-01 10:32 ` [ECOS] Dropped characters Laurie Gellatly
2007-06-01 10:56   ` Sergei Gavrikov
2007-06-01 11:56     ` Laurie Gellatly
2007-06-02 12:28       ` Laurie Gellatly
2007-06-01 11:58 ` [ECOS] Eclipse unable to debug threads Laurie Gellatly

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=OBEELMDOHGDFDEMJCJCJGEPILLAA.laurie.gellatly@netic.com \
    --to=laurie.gellatly@netic.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=gary@mlbassoc.com \
    --cc=oyvind.harboe@zylin.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).