Click to See Complete Forum and Search --> : windows ce .net eboot bootloader


Gadz
December 15th, 2003, 01:57 AM
Hi all, I have been tearing my hair out so hopefully someone has the answer. I can't seem to re-compile the Fmd.cpp file for the Lubbock bootloader.

I have a PXA250 variant dev board and am using wince 4.2 (or .net) and I am using the lubbock BSP as my starting example. I did the following:

1) copied the BSP to my own platform using the BSP copy wizard.
2) made a new project with the minimum features (practically nothing cause I am only working on the bootloader)

After heaps of registers and going crosseyed over 1's and 0's, I currently can get eboot partially started (the serial port) see the following:

======================
*******Beginning System Initialization*******

CPU ID = B2 PXA250
SDCLK[1] = MemClk
MemClk = 99.53 MHz
Run Mode = 2 * MemClk
Turbo Mode = Run Mode
Mode: RUN


Beginning SDRAM Scrub...
SDRAM Scrub Complete

******************************************************
******************************************************
******************************************************
******************************************************
******************************************************
OEMInitDebugSerial using UART1

Microsoft Windows CE Ethernet Bootloader Common Library Version 1.0 Built Mar 13
2003 23:05:42
Microsoft Windows CE Ethernet Bootloader 3.3 for the Intel DBPXA250 Development
Platform (Built Dec 15 2003)
ERROR: Flash FMD initialization failed.

==============================================

The problem occurs in the FMD_Init() function, called from main.c but I unable to see why exactly. I want to place some serial debug strings in the FMD_Init function. The DEBUGMSG and RETAILMSG don't spit anything to the serial port and if I make a change, the change doesn't get compiled into my bootloader. Even if I place some crap code in the two FMD_Init functions (see below for their locations) and do a "clean", then "regenerate platform headers" and then "rebuild" everything, there are no errors so the function is obviously not being compiled in.

The two files I found the FMD_Init function are:

1 FMD_Init - Function in Fmd.cpp (public\common\oak\drivers\block\msflashfmd\strata) at line 123 (63 lines)
2 FMD_Init - Function in Fmd.cpp (public\common\oak\drivers\block\msflashfmd\sdnpci) at line 720 (96 lines)

Not sure which one I am using (or how to specify) but does anyone know how to make a change and recompile the Fmd.cpp file?

Cheers, Gadz

rohshall
February 27th, 2009, 05:39 AM
Hi all, I have been tearing my hair out so hopefully someone has the answer. I can't seem to re-compile the Fmd.cpp file for the Lubbock bootloader.



The two files I found the FMD_Init function are:

1 FMD_Init - Function in Fmd.cpp (public\common\oak\drivers\block\msflashfmd\strata) at line 123 (63 lines)
2 FMD_Init - Function in Fmd.cpp (public\common\oak\drivers\block\msflashfmd\sdnpci) at line 720 (96 lines)

Not sure which one I am using (or how to specify) but does anyone know how to make a change and recompile the Fmd.cpp file?

Cheers, Gadz

Hi,

Windows CE build system is one hell of a complex thing. There are multitude of build options. OK, all you need to do is to clean sysgen and do sysgen again. Build and rebuild is not going to build files in the public directory.

sandeep3681
March 31st, 2009, 02:44 AM
Hi,

I have a LogicPD's ZOOM devolopment board for OMAP3530, I have BSP for the board, it contains a EBOOT folder, but LogicPD people are claiming that it is released by Microsoft and its not specific for LogicPD. So I am unable to build the BOOT folder, to create the EBOOT.bin.

Can any one suggest me how to build the EBOOT.bin.

Thanks in Advance.