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: "Ali Sina" <replay688 at hotmail dot com>
- To: andrew at lunn dot ch
- Cc: ecos-discuss at ecos dot sourceware dot org
- Date: Sun, 16 Oct 2005 20:46:53 +0000
- Subject: Re: [ECOS] Porting eCos / Redboot / Memory map modifications / E7T
- Bcc:
Thanks Andrew,
we finally got the memory recognized by properly modifying the 3 files.
Indeed, modification of hal_platform_setup.h was necessary.
Now the next two questions arise:
1. I would like to make Redboot the only bootloader on the system and get
rid of the ARM BSL. Can this be done reasonably easy on the E7T?
I understand that Redboot needs to be told to start at 0x01800000 instead of
0x01820000. I have proceeded along the instructions provided here->
http://www.kozio.com/technology/tech_briefs/ChangingRedBootsStartingAddress/
and put the RB binary in the flash via Wiggler, but the image will not boot.
Am I missing something?
2. It seems that upon start Redboot is doing _something_ on UART0 of the E7T
platform - which is the user UART, while UART1 is used for console
communication /debug. This is a problem because the application assumes
external equipment to be attached to UART0 and whatever is send out of UART0
by Redboot causes the external equipment (which we cannot change or control)
to crash.
Also, UART1 is assumed to be used for communication purposes, and the roles
cannot be switched because of the way our hardware is built.
After some investigation I concluded that this _something_ might be Redboot
trying to find a channel to use for console communication. Looking briefly
at the RB source I did not see anything right away. Any ideas of how to fix
this?
Regards,
Ali
From: Andrew Lunn <andrew@lunn.ch>
To: Ali Sina <replay688@hotmail.com>
CC: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Porting eCos / Redboot / Memory map modifications / E7T
Date: Wed, 28 Sep 2005 10:58:27 +0200
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
_________________________________________________________________
Is your PC infected? Get a FREE online computer virus scan from McAfee®
Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss