From: John Dallaway <john@dallaway.org.uk>
To: Bob.Brusa@gmail.com
Cc: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] Re: linking a program for download to at91sam7x-resident redboot
Date: Fri, 20 Mar 2009 16:01:00 -0000 [thread overview]
Message-ID: <49C3B664.6000308@dallaway.org.uk> (raw)
In-Reply-To: <op.uq3inar6keg3uf@localhost>
Hi Robert
Robert Brusa wrote:
> I have configured, linked and downloaded redboot into my at91sam7x
> board. Its a minimum redboot, supporting only ser0 and ser1 for direct
> download into flash.
>
> Then I wanted to change my little hello-program by linking it in such a
> way to go above redboot in the flash. Actually I placed it at 0x00120000
> - far above redboot - by editing the ecos-provided target.ld-file. The
> memory-statement in this file now reads like this:
>
> MEMORY
> {
> ram : ORIGIN = 0x00200000, LENGTH = 0x20000
> rom : ORIGIN = 0x00120000, LENGTH = 0x80000
> }
>
> However, when running the linker, it produces errors and reports vectors
> etc. to be out of rom range. Correct, but I think I do not need these
> vectors here. What else do I have to change in the loader file (or
> elswhere) to get a linked program to be downloadable to/with redboot
> where it will be launched by a cor. redboot command (or a script later
> on)? Thanks for help.
You should be able to specify the desired address of your eCos ROM
startup application image via the CYGNUM_HAL_ARM_AT91_IMAGE_ADDRESS
option which appears to have been implemented for exactly the purpose
you describe.
John Dallaway
--
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:[~2009-03-20 15:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-20 15:30 [ECOS] " Robert Brusa
2009-03-20 15:41 ` Chris Zimman
2009-03-23 9:21 ` Robert Brusa
2009-03-24 0:23 ` Chris Zimman
2009-03-20 16:01 ` John Dallaway [this message]
2009-03-24 9:40 ` [ECOS] " Robert Brusa
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=49C3B664.6000308@dallaway.org.uk \
--to=john@dallaway.org.uk \
--cc=Bob.Brusa@gmail.com \
--cc=ecos-discuss@ecos.sourceware.org \
/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).