Re: Bootloader build problem while porting from CE 5.0 to CE 6.0.

Any chance you don't have enough memory allocated in the bootloader for
either RAM or RAMIMAGE? The different OS versions have different libraries
that can result in different footprints. While it shouldn't crash, stranger
things have happened.

Show the actual romimage output, which might tell you if you're getting
close to the limit.
--
Dean Ramsier - eMVP
BSQUARE Corporation


"sri" <sresindhu@xxxxxxxxx> wrote in message
news:b62e5f98-2974-455c-ba45-7697d1ec70ab@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi All,

I'm porting a BSP from WinCE 5.0 to WinCE 6.0. I have been able to
successfully perform all the migration steps necessary. However when
the bootloader is being built (see the build log snippet from VS2005)
BUILD: [00:0000000183:PROGC ] Building LINK Pass in D:
\WINCE600\PLATFORM\...\src\bootloader\eboot\standard\ directory.
BUILD: [01:0000000196:PROGC ] Linking D:\WINCE600\platform\...\target
\ARMV4I\debug\eboot.exe
i get the following error dialog at this point:
"Platform Builder OS ROM Image Builder has encountered a problem and
needs to close. We are sorry for the inconvenience."
When i cancel the dialog, the build proceeds but the eboot.nb0 is not
formed in the release directory. Even the eboot.bin file is of only
1kb, the length as obtained by using viewbin command shows 0. My
nk.bin is generated successfully though.
The same bootloader in CE 500 forms eboot.bin and eboot.nb0 properly.
The contents of my eboot.bib are as follows:

MEMORY

; Name Start Size Type
; ------- -------- -------- --------
IF IMGFLASH
EBOOT 00001000 00056000 RAMIMAGE
IPLRAMIMAGE 00057000 0002D000 RESERVED
ELSE
EBOOT 11F7D000 00056000 RAMIMAGE
IPLRAMIMAGE 11FD3000 0002D000 RESERVED
ENDIF

RAM 00084000 0004B000 RAM
STACK 000CF000 00030000 RESERVED
ARGS 000FF000 00001000 RESERVED

CONFIG
AUTOSIZE=OFF
COMPRESSION=OFF
PROFILE=OFF
KERNELFIXUPS=ON

IF IMGFLASH
ROMSTART=00000000
ELSE
ROMSTART=11F7D000
ENDIF
ROMWIDTH=32
ROMSIZE=00056000

Note: IMGFLASH is set.

Any help on this will greatly help my progress.
Thanks in advance!


.

Relevant Pages

  • Bootloader build problem while porting from CE 5.0 to CE 6.0.
    ... I'm porting a BSP from WinCE 5.0 to WinCE 6.0. ... "Platform Builder OS ROM Image Builder has encountered a problem and ... The same bootloader in CE 500 forms eboot.bin and eboot.nb0 properly. ... IF IMGFLASH ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Bootloader build problem while porting from CE 5.0 to CE 6.0.
    ... I'm porting a BSP from WinCE 5.0 to WinCE 6.0. ... "Platform Builder OS ROM Image Builder has encountered a problem and ... The same bootloader in CE 500 forms eboot.bin and eboot.nb0 properly. ... IF IMGFLASH ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Writing nk.bin to flash
    ... which bootloader do you use? ... is the IMGFLASH = 1 variable set? ... (Platform settings, build options) ...
    (microsoft.public.windowsce.platbuilder)
  • Re: How to import winCE 5.0 bootloader to winCE6.0
    ... convert to winCE 6.0 bootloader. ... I am trying to port Wince 5.0 BSP to Wince 6.0 on PXA320 Development ... I have used Wince 5.0 bootloader to download Wince 6.0 NK image. ... Desktop losing ACK, block number = 349, Ack again ...
    (microsoft.public.windowsce.platbuilder)
  • Re: loadcepc for linux
    ... our bootloader needs to know about CAN because we need a WINCE ... But as you said it's not that easy to jump from linux to ce, ... I'll try it with the WinCE and the file replacing method. ... Wouldn't you just have a Windows CE driver for those things and, ...
    (microsoft.public.windowsce.embedded)
Loading