This is the mail archive of the ecos-discuss@sourceware.org mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Porting eCos / Redboot / Memory map modifications / E7T


Andrew, thanks again- both problems solved, following your advice below:
- took the redoobot repository code and worked from there
- disabled the init of UART0 in hal_diag.c

Now one small thing is left regarding the redboot start address modification:

- I have noticed that upon hardware reset everything works fine.
However, when calling "reset" from within redboot, it seems that the
flash is somehow not properly seen. See output below:

----
RedBoot> reset
... Resetting.
+FLASH: driver init failed: Driver does not support device
Sorry, FLASH config exceeds available space in FIS directory

RedBoot(tm) bootstrap and debug environment [ROM]
---

Subsequent hardware reset will not show any issues with the flash.

This is currently not a major issue, but what I am afraid of
is that this wants to tell me that something else will break
later on down the road.

Am I to worry about this?

Cheers,

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: Sun, 16 Oct 2005 23:17:51 +0200

On Sun, Oct 16, 2005 at 08:46:53PM +0000, Ali Sina wrote:
> 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?


The code for the eCos E7T in the repository has RedBoot as the only
boot loader. So you might want to compare your code with the E7T code
and see what is different....


> 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?


If you look in packages/hal/arm/e7t/current/src/hal_diag.c you will
see it defines two e7t_ser_channels. One is for UART0 and the other is
for UART1. Try disabling UART0.

Andrew

_________________________________________________________________
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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]