RTEMS

[Fered]

Let me ask my question in another way: I'm running an ELF file on PHYCORE 
LPC3250. The board has 64 MB of SRAM. This is while the ELF file has a .Work 
section with a size around 63 MB:
Clearing .work @ 0x80101d60( 66036384 bytes)

What does it mean!? RTEMS is clearing almost whole space of SRAM for use?

> Le 12/09/12 17:16, Fered a écrit :
> > Hello All.
> > 
> > 
> > 
> > I am unable to boot RTEMS 10.2 elf examples with u-boot for Phycore LPC
> > 3250 board.
> > 
> > 
> > 
> > I followed this procedure:
> > 
> > 1. load and execute u-boot binary in ram from address 0x83fc0000
> > 
> > 2. load RTEMS10.2 hello.exe example into ram at address 0x81000000
> > 
> > 3. then I tried to boot it using bootelf command
> 
> I don't have such a board but why using U-Boot as it's not in flash?
> 
> Can't you load hello.bin directly ? (produced from hello.exe with RTEMS
> objcopy)
> 
> Regarding U-Boot, I use objcopy + mkimage to create a U-Boot compatible
> image.
> 
> regards
> 
> > After this u-boot got stuck. Here is the last message produced.
> > 
> > 
> > 
> > Loading .start @ 0x80000000 (1120 bytes)
> > 
> > Clearing .vector @ 0x80000000 (5952 bytes)
> > 
> > Loading .text @ 0x80000460 (68576 bytes)
> > 
> > Loading .rodata @ 0x80011040 (6208 bytes)
> > 
> > Clearing .robarrier @ 0x800012880 (972672 bytes)
> > 
> > Loading .data @ 0x80100000 (2016 bytes)
> > 
> > Clearing .bss @ 0x801007e0 (5504 bytes)
> > 
> > Clearing .work @ 0x80101d60( 66036384 bytes)
> 
> --
> Pierre FICHEUX -/- CTO OW/OWI, France -\- pierre.ficheux at openwide.fr
>                                          http://ingenierie.openwide.fr
>                                          http://www.ficheux.org
> I would love to change the world, but they won't give me the source code
> 
> _______________________________________________
> rtems-users mailing list
> rtems-users at rtems.org
> http://www.rtems.org/mailman/listinfo/rtems-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20120917/36b2bc0f/attachment.html>