Windows CE Binary Image Data Format (Windows CE 5.0)

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 the .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 a .bin file is small and fast. A .bin file is about half the size of an .sre file. This smaller size allows a .bin file to download faster than an .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, and record length contains the starting address of the run-time image.

Record length
4 Length of record data, in bytes.
Record checksum
4 Signed 32-bit sum of record data bytes.
Record data
Record length Record data.

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

IMAGE HEADER 15 Bytes:
4230303046460A - 7 byte sync record
000000A0 - 4 byte starting physical address of image
00004000 - 4 byte physical length of image

IMAGE RECORD HEADER 12 Bytes:
4 byte physical address of record
4 byte length of record
4 byte checksum of record
Image Record Data - Length specified in length of record

See Also

Run-Time Image Files | Absolute Binary Data Format | Romimage | Cvrtbin Tool

Last updated on Thursday, February 02, 2006

Send Feedback on this topic to the authors

Feedback FAQs

© 2006 Microsoft Corporation. All rights reserved.