re:Re: [ECOS] eCos Romable ? (on AT91EB55)

[Sean Christensen <seanc at internap dot com>]

Well, this looks to be a RAM version of your app.  You need to rebuild
eCos for ROM startup, and recompile / link your app. to it.

> I'm kind of lost
> Which part do I write in the flash ?
> ?
> Loading section .rom_vectors, size 0x40 lma 0x2008000
> Loading section .text, size 0x13370 lma 0x2008040
> Loading section .rodata, size 0x1184 lma 0x201b3b0
> Loading section .data, size 0x458 lma 0x201c534
> Start address 0x2008040, load size 84364
> ?

This is all part of the 'elf' file format for loading and debugging.  You
don't want this, that is why you strip it down to a raw binary image with
the arm-elf-objcopy utility.  The raw binary is what will be loaded into
the flash.

> What I'd like to do : keep Redboot on the second half of the flash write my image in the first part of the Flash is it possible ?

If you need them in this order, this can be done but they might need to
be seperate areas on the flash.  You could use the top address line (not
connected to the CPU bus) on the flash to select the image you would
boot.  Address line 'low' = boot the application, address line 'high' = Redboot.

Not sure this is what you want...

SLC


> >
> >Here is the way I do it.
> >
> >If you are not retaining Redboot, rebuild eCos lib with ROM startup.
> >Compile / link your program to the ROM eCos lib.  Strip your executible of debugging
> >/ symbols (arm-elf-objcopy).  Use a JTAG flash loader to program your
> >application to 0x10000000 (start of ROM).  Done.  Resetting the board
> >should run the program.
> >
> >If you want to retain Redboot, modify the .ldi file in HAL to a ROM
> >address just above the Redboot sectors.  Rebuild eCos with ROM
> >startup. Compile / link your program to the ROM eCos lib.  Strip your executible of debugging
> >/ symbols.  Use a JTAG flash loader to program your
> >application to the start sectors just past Redboot sectors.
> >Use the Redboot 'fconfig' script command to have Redboot to 'go' to the
> >start of the application.
> >
> >If you don't have a JTAG / loader, use redboot 'load' to temperarly put
> >the executable into some unused RAM space.  Then use 'fis write' to put the
> >program into the ROM start location.
> >
> >
> >-S
> >
> >On Fri, 6 May 2005, Gatien Gillon wrote:
> >
> >> The plateforme is AT91EB55
> >> I have my application I've debugged it using redboot sending it with GDB now I'd like to put it a the FLASH memory so that when I reset my board my app starts immediatly without having to send it using GDB
> >>
> >> >On Fri, 2005-05-06 at 14:22 +0200, Gatien Gillon wrote:
> >> >> How can I put eCos in a way it starts automatically on
> >> >> a reboot without having to send an image using GDB ?
> >> >
> >> >This is [normally] a supported way of configuring eCos programs.
> >> >
> >> >  CYG_HAL_STARTUP = ROM
> >> >
> >> >What platform/target?
> >> >
> >> >--
> >> >------------------------------------------------------------
> >> >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
> >> >
> >> >
> >>
> >>
> >>
> >> --
> >> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> >> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
> >>
> >>
> >>
> >
> >
>
>
>
>

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss