This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: ROMRAM .. kind of
- From: Elad Yosef <elad dot yosef at gmail dot com>
- To: Stanislav Meduna <stano at meduna dot org>
- Cc: ecos-discuss at ecos dot sourceware dot org
- Date: Wed, 22 Feb 2012 07:33:55 +0200
- Subject: [ECOS] Re: ROMRAM .. kind of
- Authentication-results: mr.google.com; spf=pass (google.com: domain of elad.yosef@gmail.com designates 10.68.233.74 as permitted sender) smtp.mail=elad.yosef@gmail.com; dkim=pass header.i=elad.yosef@gmail.com
- References: <4F4407A2.1030706@meduna.org>
Hi,
You can look at the ecos tables.
The Tables macros assigned section attribute and the linker script
keeps them all in the section.
Elad
On Tue, Feb 21, 2012 at 11:07 PM, Stanislav Meduna <stano@meduna.org> wrote:
> Hi,
>
> I want to be able to update the RedBoot from RedBoot. So
> I need to copy a short code from RedBoot away into RAM,
> disable interrupts and run it to flash the new RedBoot,
> then do a verify and reboot to the new one.
>
> That code has to be linked with offsets in RAM, but needs
> to be stored in flash.
>
> Unfortunately I am not really a guru in GNU ld and its scripts.
> Is there any example on how to link a code for one address
> and direct the section somewhere else in the final image?
>
> I've looked up some ROMRAM setups but they look such that
> the code up to the RAM copy is position independent and initially
> simply runs from an 'incorrect' address, which does not
> really help me much.
>
> In the case it matters I need to do this for a Cortex-M3.
>
> Maybe my flash code can be made position independent too
> and I can also think of some script magic to assemble the
> flash image, but I would of course prefer to do this in
> the ld script way if possible.
>
> Thanks
> --
> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?Stano
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss