From mboxrd@z Thu Jan  1 00:00:00 1970
From: Gary Thomas <gthomas@redhat.com>
To: Christoph Csebits <christoph.csebits@frequentis.com>
Cc: ecos-discuss@sources.redhat.com
Subject: RE: [ECOS] RedBoot ROM version
Date: Thu, 12 Jul 2001 07:13:00 -0000
Message-id: <XFMail.20010712081304.gthomas@redhat.com>
References: <20010712160021.A11053@frequentis.com>
X-SW-Source: 2001-07/msg00367.html

On 12-Jul-2001 Christoph Csebits wrote:
> hi
> 
> i have ported RedBoot to my custom MPC860
> board (based on MBX) to run in RAM.
> 
> Now i started to generate a ROM version
> and burned it into flash.
> 
> After powerup, the board hangs somewhere in
> cyg_hal_invoke_constructors (called in vectors.S)
> 
> I have adjusted the ROM bounds
> I have added 
> 
> cdl_option CYGSEM_HAL_ROM_MONITOR {
>     user_value 1
> };
> 
> to my .ecm file.
> 
> Thats all I have changed from RAM version
> Is there some vital thing missing?

HAL_STARRTUP == ROM ?

> 
> Can anybody show me a working way how to copy
> (powerpc-eabi-objcopy) the necessary
> things out of the elf binary?

You really shouldn't try to short circuit things like this.  The best
way to create a ROM based application is to use the configuration
tools to set ROM startup mode.

For example, here's how to build ROM based RedBoot for the PowerPC mbx860:

  % ecosconfig new mbx redboot
  % ecosconfig import startup_ROM
  % ecosconfig tree
  % make

where the file 'startup_ROM' looks like this (without the --- lines):
-----------------------------------------------------------
cdl_component CYG_HAL_STARTUP {
    user_value ROM
};
-----------------------------------------------------------

Look at other platforms to see how to make use of objcopy for what
you want.  The MBX is a good choice as it makes use of them when
building RedBoot.