BIB files
ROMIMAGE uses Binary Image Builder (BIB) files to configure how it should configure the ROM. BIB files are just plain text files with keywords defining four different sections.
The modules section is identified with the keyword MODULES on a line of its own. In the modules section, executable modules are listed for code that will execute in place (XIP). The files section (keyword FILES) lists other files to place in the image (bitmaps, data files, HTML pages, and so on). It can also specify executable modules not intended for XIP. Rarely used diagnostic applications are a good candidate for that. The items in the files section are compressed by default to reduce the size.
modules and files
The syntax is pretty straightforward for the entries of the modules and files sections:
[target] [whitespace] [workstation][memory][flags][target]
is the name of the file as it will appear in the ROM. is the path ROMIMAGE will use to find the actual file (normally based on $(_FLATRELEASEDIR)). The memory section will be "NK" with few exceptions. (Boot loaders are a common exception).
The flags are summarized in the following table:
Flag--Purpose
C--Compressed (default for files section)
U--Uncompressed (default for modules section)
R--Compress resources only
H--Hidden file
S--System file
The remaining two sections of BIB files are normally placed in the Config.bib file (merged with the other BIB files in the makeimg phase to generate ce.bib). These are:
Memory
The memory section, which describes the memory layout for your system. It's syntax is as follows:
[name] [virtual] [size] [type]
where TYPE is one of the following:
RAM --
Specifies a region of RAM available to running processes and the RAM-based Windows CE file system. The region must be contiguous.
RAMIMAGE--
Specifies that the region should be treated like ROM. The kernel copies all writeable sections for an application into RAM and fixes the memory addresses prior to starting the application process.
RESERVED--
Specifies that a region of RAM is reserved. Currently, Romimage.exe ignores this field, so it functions only as a comment. This memory might be a video frame buffer or a direct memory access (DMA) buffer. Do not overlap reserved regions with other memory regions. Windows CE .NET provides a means of allocating such buffers programmatically, so the use of reserved is now effectively obsolete.
The config section specifies a number of miscellaneous settings, including the size and width of ROM if you are using the raw binary image format (ABX=ON).
ROMIMAGE uses Binary Image Builder (BIB) files to configure how it should configure the ROM. BIB files are just plain text files with keywords defining four different sections.
The modules section is identified with the keyword MODULES on a line of its own. In the modules section, executable modules are listed for code that will execute in place (XIP). The files section (keyword FILES) lists other files to place in the image (bitmaps, data files, HTML pages, and so on). It can also specify executable modules not intended for XIP. Rarely used diagnostic applications are a good candidate for that. The items in the files section are compressed by default to reduce the size.
modules and files
The syntax is pretty straightforward for the entries of the modules and files sections:
[target] [whitespace] [workstation][memory][flags][target]
is the name of the file as it will appear in the ROM.
The flags are summarized in the following table:
Flag--Purpose
C--Compressed (default for files section)
U--Uncompressed (default for modules section)
R--Compress resources only
H--Hidden file
S--System file
The remaining two sections of BIB files are normally placed in the Config.bib file (merged with the other BIB files in the makeimg phase to generate ce.bib). These are:
[name] [virtual] [size] [type]
where TYPE is one of the following:
RAM --
Specifies a region of RAM available to running processes and the RAM-based Windows CE file system. The region must be contiguous.
RAMIMAGE--
Specifies that the region should be treated like ROM. The kernel copies all writeable sections for an application into RAM and fixes the memory addresses prior to starting the application process.
RESERVED--
Specifies that a region of RAM is reserved. Currently, Romimage.exe ignores this field, so it functions only as a comment. This memory might be a video frame buffer or a direct memory access (DMA) buffer. Do not overlap reserved regions with other memory regions. Windows CE .NET provides a means of allocating such buffers programmatically, so the use of reserved is now effectively obsolete.
The config section specifies a number of miscellaneous settings, including the size and width of ROM if you are using the raw binary image format (ABX=ON).
留言