From: Andrew Lunn <andrew@lunn.ch>
To: "Alois Z." <alois@gmx.at>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] RAM Images on AT91SAM7s256
Date: Mon, 28 Jan 2008 16:47:00 -0000 [thread overview]
Message-ID: <20080128164654.GC10795@lunn.ch> (raw)
In-Reply-To: <20080128160738.64350@gmx.net>
On Mon, Jan 28, 2008 at 05:07:38PM +0100, Alois Z. wrote:
> Hi,
>
> I currently working with a AT91SAM7s256 based board. For debugging
> and testing I like to devlop RAM only images.
With only 64Kbytes of RAM, you will be very limited to what you can
do. I strongly suggest you get a JTAG debugger which can set hardware
breakpoints. You can then run your application from ROM and single
step, set a couple of breakpoints etc.
> As the existing eCos
> support for this platform has only definitions for rom images I
> tried to use the existing files for ram linker file
> definitions. After looking through several ldi files and googling
> around I'm not quite shure if made the right placement for the
> 'SECTION_rom_vectors' and the 'SECTION_fixed_vectors' sections.
>
> Currently my ram.ldi looks like:
>
> MEMORY
> {
> ram : ORIGIN = 0x00200000, LENGTH = 0x10000
> }
>
> SECTIONS
> {
> SECTIONS_BEGIN
> SECTION_rom_vectors (ram, 0x00200000, LMA_EQ_VMA)
> SECTION_fixed_vectors (ram, ALIGN (0x1), LMA_EQ_VMA)
> SECTION_text (ram, ALIGN (0x1), LMA_EQ_VMA)
> SECTION_fini (ram, ALIGN (0x4), LMA_EQ_VMA)
> SECTION_rodata (ram, ALIGN (0x4), LMA_EQ_VMA)
> SECTION_rodata1 (ram, ALIGN (0x4), LMA_EQ_VMA)
> SECTION_fixup (ram, ALIGN (0x4), LMA_EQ_VMA)
> SECTION_gcc_except_table (ram, ALIGN (0x4), LMA_EQ_VMA)
> SECTION_data (ram, ALIGN (0x4), FOLLOWING (.gcc_except_table))
> SECTION_bss (ram, ALIGN (0x4), LMA_EQ_VMA)
> CYG_LABEL_DEFN(__heap1) = ALIGN (0x8);
> SECTIONS_END
> }
This looks reasonable.
How are you going to get this image into RAM?
You also need to make sure that RAM is mapped to address 0x0 as well
as 0x00200000. I know ROM startup does this, but i think RAM startup
probably does not.
--
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:[~2008-01-28 16:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 16:08 Alois Z.
2008-01-28 16:47 ` Andrew Lunn [this message]
2008-01-28 17:06 ` Alois Z.
2008-01-28 17:10 ` Alois Z.
2008-01-28 17:19 ` Andrew Lunn
2008-01-28 18:36 ` Alois Z.
2008-01-29 12:19 ` Tom Deconinck
2008-04-02 1:48 ` airdelroy
2008-04-02 6:12 ` Tom Deconinck
2008-04-05 0:14 ` airdelroy
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=20080128164654.GC10795@lunn.ch \
--to=andrew@lunn.ch \
--cc=alois@gmx.at \
--cc=ecos-discuss@sources.redhat.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).