Boot Loader Image Builder File (Windows Embedded CE 6.0)
1/5/2010
The Boot.bib file specifies the size, type, and location of the memory on the target device where you load the boot loader. Because the boot loader executes from ROM or flash memory, the writeable data sections in the boot loader should be relocated to RAM before using the data sections, which are global variables. This is done by BLCOMMON. The boot loader also uses some RAM for the stack. The boot loader can also copy itself from ROM to RAM during startup. In this case, the boot loader should only perform relative jumps until the image is copied to RAM and the image is should be adjusted based on the destination address in RAM.
The RAM statement in the .bib file controls the RAM area that is used for data sections that are writeable by the boot loader. The OEM in the boot loader startup code initializes the stack.
The start address entries in the MEMORY section of Boot.bib must be either RAM or ROM. In the MEMORY section, modify the boot and RAM entries for the target device. In the MODULES section, the name entry must be Nk.exe for the ROM image builder to correctly relocate the data section.
The following code example shows the MODULES section of the Boot.bib file where you specify Eboot.exe.
MODULES
; Name Path Memory Type
; ------ ------------ -----------
nk.exe Eboot.exe EBOOT
The following table shows the boot loader–specific entries that you can include in the CONFIG section of Boot.bib.
| Boot loader entry | Description |
|---|---|
ROMOFFSET |
Specifies the offset of the image address records. BIN file records, which are .abx files, are unaffected. |
BOOTJUMP |
Specifies the address to which the boot loader jumps on startup. |
X86BOOT |
Specifies an initial jump operation code for an x86 boot loader. The jump instruction is applied at x86 reset vector address. The x86 boot loader entry applies only to the startup code in the system. |