Windows CE Binary Image Data Format

Platform builder for Microsoft Windows CE 5.0 Windows CE Binary Image Data Format

Send feedback

The binary image (. Bin) File Format organizes data by sections. Each section contains a section header that specifies the starting address, length, and checksum for that section.

Romimage.exe writes data organized by logical sections, such as an application's text or. data region, to. BIN file. the run-time image terminates with a run-time image record header with the physical address and checksum set to zero.

A configuration file formatted as. BIN file is small and fast. a. BIN file is about half the size of. sre file. this smaller size allows. BIN file to download faster. sre file.

The following table shows the. BIN file format.

Field	Length (bytes)	Description
Sync bytes (optional)	7	Byte 0 is B, Indicating a. BIN file format. Bytes 1-6 are reserved and set to 0, 0, 0, F, F,/n.
Run-time image header, consisting of the following:
Run-Time Image address	4	Physical starting address of the run-time image.
Run-Time Image Length	4	Physical length, in bytes, of the run-time image.
One or more records, consisting of the following:
Record address	4	Physical starting address of data record. If this value is zero, the record address is the end of the file, andRecord LengthContains the starting address of the run-time image.
Record Length	4	LengthRecord Data, In bytes.
Record checksum	4	Signed 32-bit sumRecord DataBytes.
Record Data	Record Length	Record data.

The following code example shows a. BIN file format definition.

Copy code

 
Image Header 15 bytes: 42303046460a-7 byte sync record000000a0-4 byte starting physical address of imageaudio 4000-4 byte physical length of imageimage record header 12 Bytes: 4 byte physical address of record4 byte length of record4 byte checksum of recordimage record data-Length Specified in length of record
 

------------------------------------------------------
 

 
 

  
  
 
  
I have doubts about the binfile format: What is the physical address of the run-time image address? I really don't understand what kind of format can be run in memory.
 
  

  
  
 
  
In Pb help
 
  

  
  
At the end of the boot loader development process described in the topic how to develop a boot loader, you will have two different binary images for the Boot Loader:. BIN file and. nb0 file. the Microsoft Windows & reg; Ce Binary Image Data Format (. BIN) file is the most common format for Windows CE binary images. it is a binary file that consists of a number of individual records with associated per-record bookkeeping data. the format is convenient for minimizing the amount of data to be downloaded to the target device by removing the need to pad between records. for more information about. BIN file format, see Windows CE Binary Image Data Format (. BIN ).

The. nb0 file format is a raw binary image of the boot loader. the image is as it appears in the memory on the target device and does not contain the header information that. BIN file except des. the. nb0 file is typically larger than. BIN file. the. nb0 file is useful for placing the initial Boot Loader image on the target device. this is usually done with a built-in monitor program provided by the board manufacturer. you can also place the initial Boot Loader image on the target device through a JTAG connection using a JTAG probe. once. nb0 image is stored on the device, it shoshould be able to download and update itself using. BIN file format from then on.
  
  

  
I am using the bootloader developed by analyticdb. There is no segment problem with this binfile. It should be different from Microsoft. Where is the problem of global variables? But why does it occasionally fail to start? Finally, it is found that the origin is returned. It seems that the binfile format in ads must be clear.