From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32617 invoked by alias); 24 May 2005 17:15:03 -0000 Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Received: (qmail 32518 invoked by uid 22791); 24 May 2005 17:14:57 -0000 Received: from smtp1.gestion.ulpgc.es (HELO smtp1.gestion.ulpgc.es) (193.145.138.5) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Tue, 24 May 2005 17:14:57 +0000 Received: by smtp1.gestion.ulpgc.es (Postfix, from userid 43062) id 223E1C0382; Tue, 24 May 2005 18:14:54 +0100 (WEST) Received: from newint.iuma.ulpgc.es (newint.iuma.ulpgc.es [10.13.22.5]) by smtp1.gestion.ulpgc.es (Postfix) with ESMTP id F1DCBC0362 for ; Tue, 24 May 2005 18:14:53 +0100 (WEST) Received: from svext.iuma.ulpgc.es (svint.iuma.ulpgc.es [10.13.22.17]) by newint.iuma.ulpgc.es (Postfix) with ESMTP id E654E4E518 for ; Tue, 24 May 2005 18:20:37 +0100 (WEST) Received: from svext.iuma.ulpgc.es (localhost.localdomain [127.0.0.1]) by svext.iuma.ulpgc.es (Postfix) with ESMTP id 16774B63C0 for ; Tue, 24 May 2005 18:16:08 +0100 (WEST) Received: (from apache@localhost) by svext.iuma.ulpgc.es (8.13.1/8.13.1/Submit) id j4OHG7K8011603 for ecos-discuss@ecos.sourceware.org; Tue, 24 May 2005 18:16:07 +0100 X-Authentication-Warning: svext.iuma.ulpgc.es: apache set sender to yrodguez@iuma.ulpgc.es using -f Received: from philone.iuma.ulpgc.es (philone.iuma.ulpgc.es [10.13.22.81]) by webmail.iuma.ulpgc.es (Horde) with HTTP for ; Tue, 24 May 2005 18:16:07 +0100 Message-ID: <20050524181607.1tzi826684gws8oo@webmail.iuma.ulpgc.es> Date: Wed, 25 May 2005 06:57:00 -0000 From: yrodguez@iuma.ulpgc.es To: ecos-discuss@ecos.sourceware.org References: <20050524174110.zvo62etf4skoccg4@webmail.iuma.ulpgc.es> <1116953376.19176.45.camel@hermes> <20050524175806.gj72jy7dy8kw0ck4@webmail.iuma.ulpgc.es> <1116954112.19176.49.camel@hermes> In-Reply-To: <1116954112.19176.49.camel@hermes> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.0.2) Subject: Re: [ECOS] redboot startup mode X-SW-Source: 2005-05/txt/msg00322.txt.bz2 Quoting Gary Thomas : > Please reply to the eCos mailing list so that all may benefit. Private > support is available under contract (from MLB Associates or others) I'm Sorry. > > On Tue, 2005-05-24 at 17:58 +0100, yrodguez@iuma.ulpgc.es wrote: >> But, who exactly have to copy redboot code from flash to ram?, I'm > > Look in the platform startup code: > /packages/arm/arm9/excalibur/current/include/hal_platform_setup.h > My question is: do i need another startup code, different to redboot, to use this mode or is enough with redboot? thanks, and, I'm sorry again. >> sorry, maybe >> i don't understand it due to my bad level in english >> >> thanks. >> >> Quoting Gary Thomas : >> >> > On Tue, 2005-05-24 at 17:41 +0100, yrodguez@iuma.ulpgc.es wrote: >> >> hi, >> >> i have a doubt/question? >> >> >> >> i'm trying to compile a redboot in romram mode. >> >> >> >> >> >> At http://sources.redhat.com/ecos/docs-latest/redboot/excaliburarm9.html >> >> >> >> say that romram mode runs redboot from ram with redboot in flash. >> I supossed >> >> that redboot is stored in flash memory and then it is copied from >> >> flash to ram. >> >> But when i desassemble the file i get the code is mapped on ram (0x8000): >> >> >> > >> > Correct. It has to be that way - the linker produces an image suitable >> > for running from RAM. That said, the image will be stored in FLASH >> > (typically this is all that's accessible immediately after RESET). The >> > program [RedBoot or whatever] then does some minimal hardware >> > initialization, e.g. turning on the SDRAM controller, setting up mapping >> > registers, etc. The code is then copied from FLASH to its ultimate RAM >> > destination and control is then passed there. Now you are running from >> > RAM only. It's up to the startup code to understand all of this and >> > it must contain [normally position-independent] code that performs these >> > steps at startup. >> > >> > Note: this mode is only suitable for *the* initial "ROM" monitor code, >> > like RedBoot. This is not how you would write a generic program which >> > runs in RAM but whose image was stored in FLASH. For that, you use >> > RedBoot's FIS commands (create, load) >> > >> > -- >> > ------------------------------------------------------------ >> > Gary Thomas | Consulting for the >> > MLB Associates | Embedded world >> > ------------------------------------------------------------ >> > >> > >> >> > -- > ------------------------------------------------------------ > Gary Thomas | Consulting for the > MLB Associates | Embedded world > ------------------------------------------------------------ > > -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss