This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: help- redboot build and startup
- From: Andrew Lunn <andrew at lunn dot ch>
- To: Rohit Pandita <pandi008 at umn dot edu>
- Cc: ecos-discuss at ecos dot sourceware dot org
- Date: Tue, 21 Feb 2006 21:27:13 +0100
- Subject: Re: [ECOS] help- redboot build and startup
- References: <43FB719D.1010901@umn.edu>
On Tue, Feb 21, 2006 at 02:01:33PM -0600, Rohit Pandita wrote:
> Hi,
>
> I had posted a couple of queries on the list in last few weeks, but it
> seems they were too trivial/ silly to elicit any response. In which
> case, apologies from a newbie.
>
> I've given up now on getting gdb stubs to work, instead trying to get
> redboot working. I've been able to build the redboot.elf (460+ kB), but
> unable to burn it to flash. Follwing are the observations,
>
> 1. There are 3 program headers, starting at offset 52
>
> Program Headers:
> Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align
> LOAD 0x010000 0x00000000 0x00000000 0x19ef4 0x19ef4 R E 0x10000
> LOAD 0x039b00 0x003f9b00 0x00019ef8 0x01140 0x01140 RWE 0x10000
> LOAD 0x03ac40 0x003fac40 0x003fac40 0x00000 0x03ce8 RW 0x10000
>
> Section to Segment mapping:
> Segment Sections...
> 00 .vectors .text .rodata
> 01 .data
> 02 .sbss .bss
>
> Why are segment 01 and 02 being written to 0x003f9b00 and beyond, when this
> is clearly out of my board's flash range (Phycore555)?
The first sections contain actuall code and read only data.
The second segment contains variables which are initialized at compile
time. The third segment contains variables which are uninitialized at
compile time and contain zero. Obviosly these don't belong in flash.
Your flash programmer should not be trying to program these segments.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss