This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: Porting eCos / Redboot / Memory map modifications / E7T
- From: Andrew Lunn <andrew at lunn dot ch>
- To: Ali Sina <replay688 at hotmail dot com>
- Cc: ecos-discuss at ecos dot sourceware dot org
- Date: Wed, 28 Sep 2005 10:58:27 +0200
- Subject: Re: [ECOS] Porting eCos / Redboot / Memory map modifications / E7T
- References: <BAY108-F2194CA1F8237F3D0D70D3FEA8D0@phx.gbl>
On Wed, Sep 28, 2005 at 08:15:10AM +0000, Ali Sina wrote:
> 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?
IT might be worth reading the data sheet about the memory
controller. Does it need setting up differently when there is double
the amount of RAM.
packages/hal/arm/e7t/current/include/hal_platform_setup.h looks
to be doing something with a memory controller and timings.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss