romimage problem

I'm building the bootloader for my ARM-based board using romimage
and a bib file.
This is the output of viewbin -t on my eboot.bin:

ViewBin... EBOOT.bin
Image Start = 0x00070000, length = 0x0001634C
Start address = 0x00071000
Checking record #5 for potential TOC (ROMOFFSET = 0x00000000)
Found pTOC = 0x000848fc
ROMOFFSET = 0x00000000

ROMHDR ----------------------------------------
DLL First : 0x4001C001
DLL Last : 0x4001C001
Physical First : 0x00070000
Physical Last : 0x0008634C
RAM Start : 0x000B0000
RAM Free : 0x000B2000
RAM End : 0x000C0000
Kernel flags : 0x00000000
Prof Symbol Offset : 0x000B0000
Num Copy Entries : 3
Copy Entries Offset : 0x00084970
Num Modules : 1
Num Files : 0
MiscFlags : 0x00000002
CPU : 0x01c2 (Thumb)
Extensions : 0x00000000

COPY Sections ---------------------------------
Src: 0x000845C0 Dest: 0x00084000 CLen: 0x225 DLen:
Src: 0x000847E8 Dest: 0x00098000 CLen: 0x39 DLen: 0x48
Src: 0x00085000 Dest: 0x000B0000 CLen: 0x658 DLen:

MODULES ---------------------------------------
10/13/2008 16:46:11 80896 nk.exe

FILES ----------------------------------------

As you can see the first of the COPY sections overlaps the others.
I debug my bootloader using a jtag emulator and I see that when
KernelRelocate is invoked it parses the TOC, finds the copy entries
but as soon as it parses the first entry it fills the others with
zeros (DLEN is 121A0) and so it does not perform the remaining copy
operations and I fond some structures uninitialized inside my code.

In my map file address 0x98000 is g_oalAddressTable but I have no
entries for the other copy section elements (I suppose they should
re-map some static global variables in some modules).

It seems that romimage generates the wrong entry for the copy table.
There is a way to have "verbose" output from romimage?

I'll try to remove the static from all the global variables
declarations to be able to understand what's going to be mapped at

Thank you for any suggestion or hint you can provide.

Valter Minute
Training, support and development for Windows CE
(the reply address of this message is invalid)

Relevant Pages

  • Possible bug: ROMIMAGE does not process ROMWIDTH correctly, PB 4.2
    ... I seem to have run across a possible bug with using the ROMIMAGE tool in PB ... I have been upgrading our "bootloader" which gets programmed into EPROMs, ... from WinCE 2.12 to WinCE 4.2. ...
  • Re: Bootloader - pTOC again
    ... The tool romimage fills the right address into this variable when it locates the the bootloader. ... If the make image step or an explict call to the romimage tool is missing the pTOC is initialized with the default value of 0xFFFFFFFF. ... George H. schrieb: ... Linker does not assign right address to a pTOC variable - there still is 0xFFFFFFFF. ...
  • Re: not to be able to run .exe files on wince 5
    ... Time for you to do some research into makefile, romimage and bib files. ... Where you put the file will depend on what you put in the bib file. ... beitman AT applieddata DOT net ... But clearly where i copy the exe files first?In VIABSP_x86_Release ...
  • Re: What is the equivalent of linker script in ARM assembler ?
    ... These are not needed in Windows CE as ROMIMAGE takes care of the link and ... The BIB file directs the system as to where in memory ...
  • nk
    ... i am building a bootloader using wince 5.0,whwn i do romimage an ... Prev by Date: ...