From: "Ali Sina" <replay688@hotmail.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Porting eCos / Redboot / Memory map modifications / E7T
Date: Wed, 28 Sep 2005 10:52:00 -0000 [thread overview]
Message-ID: <BAY108-F2194CA1F8237F3D0D70D3FEA8D0@phx.gbl> (raw)
Hello,
we are trying to get our code to run on our own hardware, which for all
practical reasons can be described as an E7T platform with double the RAM.
The setup is as follows:
Redboot (ROM startup mode) is resident on the board and upon power on loads
the image of the code (RAM startup) from FLASH into RAM, where the code then
gets executed.
As a control and starting point, the same Redboot and the compiled code run
fine on both E7T and our HW, of course not using the extra RAM.
From this list, Massa's book and other sources I understand that what is
needed in order to use the extra RAM is to modify the memory layout,
specified in the mlt_arm_e7t_rom/mlt_arm_e7t_ram.h and .ldi files.
Particularly, I have changed the RAM size to double (from 0x80000 to
0x100000) and modified the heap size accordingly.
Is this sufficient? The code will compile but does not work when using the
extra RAM (for now I use a static array to control the RAM requirement of
the code)
I can provide more detail if necessary, but possibly I am missing something
even more basic.
Thanks for any help,
Ali
_________________________________________________________________
DonÂt just search. Find. Check out the new MSN Search!
http://search.msn.click-url.com/go/onm00200636ave/direct/01/
--
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 reply other threads:[~2005-09-28 8:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-28 10:52 Ali Sina [this message]
2005-09-28 11:17 ` Andrew Lunn
2005-10-16 20:46 ` Ali Sina
2005-10-16 21:21 ` Andrew Lunn
2005-10-23 10:10 ` Ali Sina
2005-10-23 11:10 ` Andrew Lunn
2005-10-24 7:49 ` Andrew Lunn
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=BAY108-F2194CA1F8237F3D0D70D3FEA8D0@phx.gbl \
--to=replay688@hotmail.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).