18 File layouts
CEF defines the layout of State files and Dump files. A State file is used to save the emulated environment's state current state in such a way that the state can be reloaded at a later time and execution continue from that point as if it had never been interrupted. A Dump file is a dump of the contents of a component for various uses, including analysis and image save/restore. Both files begin with a 256-byte header. The following defines the layouts for file version 0.0.
Dump file layout:
|
Byte(s) |
Description |
|
0 |
255 |
|
1 |
255 |
|
0 |
(CEF) |
|
3 |
File format version number times 10 (1.2=12) |
|
4 |
0 (Dump file) |
|
5-8 |
Packed date/time stamp (optional - may be 0). |
|
9-16 |
First address in file. |
|
17-255 |
Reserved (should be 0). |
|
256+ |
Dump image. |
State file layout:
|
Byte(s) |
Description |
|
0 |
255 |
|
1 |
255 |
|
2 |
0 (CEF) |
|
3 |
File format version number times 10 (1.2=12). |
|
4 |
1 (State file) |
|
5-8 |
Packed date/time stamp (optional – can be 0). |
|
9-255 |
Reserved. Should be 0. |
|
256+ |
State image. |
The state image consists of a series of variable-length records, one after another, each starting with the following:
|
Byte(s) |
Description |
|
0-3 |
Facility code of component. |
|
4-7 |
Serial number of component. |
|
8+ |
State image. |