Re: [ECOS] Can I assign the offset of code start in redboot.bin when using startup from ROM

[Gary Thomas <gary@mlbassoc.com>]

On Thu, 2005-07-07 at 17:35 +0800, Steven_cheng wrote:
> Hi All,
> 
> Environment:
>     arch: MPC8245
>     package: RedBoot
>     startup type: ROM
> 
> After building the code, I burn the the redboot.bin into my rom flash, but
> it
> seems not to be executed. Then I found that the code offset starts in 0x0,
> not
> in 0x100,  in the redboot.bin.  The MPC8245 can not start from offset 0x100
> to execute the rom code. So the rom code is failed.
> 
> Questions:
>     1) The MPC8245 rom code should start from 0x100 in redboot.bin for
> burning.(???)
>     2) Does anybody know how I can move the code offset start from 0x0 to
> 0x100 ??
>     3) Does the code start from the _start in the vector.S  for startup type
> "ROM" ??
> 
> It was as following:
> 
> 0x00000000  rom_code  _start    # map to _start in vectors.S
> 0x00000010  rom_code
> 0x00000020  rom_code ......
> ...
> 0x00000100  rom_code ......
> ......
> 
> 
> But I think it should be as following:
> 
> 0x00000000  Vector
> 0x00000010  empty
> 0x00000020  empty
> ...
> 0x00000100  rom_code _start ......# map to _start in vectors.S
> ......
> 
> 4) Is it  correct ??
> 

How did you configure eCos?  (i.e. what commands/steps did you use?)
You can see how the image is laid out in memory using this command:
  powerpc-eabi-objdump -h install/bin/redboot.elf
What do you see from it?

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