From: "Christophe Coutand" <ccoutand@stmi.com>
To: "Martin Rösch" <martin.roesch@neratec.com>,
"discuss, eCos" <ecos-discuss@ecos.sourceware.org>
Subject: RE: [ECOS] Different section placement for kernel and application
Date: Thu, 27 Jan 2011 18:24:00 -0000 [thread overview]
Message-ID: <D6050C555CC56940A7AF326522830276039A40F8@mail2.STMIRV01.COM> (raw)
In-Reply-To: <917898.171.1296149053545.JavaMail.neratec@martin-lucid32>
If you only have a couple of functions to place in RAM, you can use the section attribute:
void my_function( void ) __attribute__ ((section (".2ram.my_function")));
Christophe
-----Original Message-----
From: ecos-discuss-owner@ecos.sourceware.org [mailto:ecos-discuss-owner@ecos.sourceware.org] On Behalf Of Martin Rösch
Sent: 27. januar 2011 18:24
To: discuss, eCos
Subject: [ECOS] Different section placement for kernel and application
Hi,
I'm trying to figure out how to run the eCos kernel from ROM and run the application (the main() function) from RAM on the STM32 Eval Board.
Is it possible to place the text, data and rodata sections from the target library to a different memory address (i.e. flash)
than the sections of the application in the image?
Thank you for your help,
Martin
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2011-01-27 17:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2815371.163.1296147619546.JavaMail.neratec@martin-lucid32>
2011-01-27 17:56 ` Martin Rösch
2011-01-27 18:24 ` Christophe Coutand [this message]
2011-01-27 22:01 ` [ECOS] " Grant Edwards
2011-01-28 16:19 ` Martin Rösch
2011-01-28 16:25 ` Grant Edwards
2011-01-28 17:07 ` Grant Edwards
2011-01-30 9:31 ` Martin Rösch
[not found] ` <2029563421.8440.1296480614291.JavaMail.root@idefix>
2014-05-19 9:45 ` Badreddine
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=D6050C555CC56940A7AF326522830276039A40F8@mail2.STMIRV01.COM \
--to=ccoutand@stmi.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=martin.roesch@neratec.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).