1srec_emon52(5) File Formats Manual srec_emon52(5)
2
6 srec_emon52 - Elektor Monitor (EMON52) file format
7
9 This format is used by the monitor EMON52, developed by the European
10 electronics magazine Elektor (Elektuur in Holland). Elektor wouldn't
11 be Elektor if they didn't try to reinvent the wheel. It's a mystery
12 why they didn't use an existing format for the project. Only the Elek‐
13 tor Assembler will produce this file format, reducing the choice of
14 development tools dramatically.
15 Records
17 All data lines are called records, and each record contains the follow‐
18 ing four fields:
19 ┌───┬──────┬───┬───────────┬──────┐
21 │cc │ aaaa │ : │ dd ... dd │ ssss │
22 The field are defi└n─e─d─┴a─s──f─o─l─l┴o─w─s─:┴───────────┴──────┘
23 cc The byte count. A two digit hex value (1 byte), counting the
25 actual data bytes in the record. The byte count is separated
26 from the next field by a space.
27 aaaa The address field. A four hex digit (2 byte) number represent‐
29 ing the first address to be used by this record.
30 : The address field and the data field are separated by a colon.
32 dd The actual data of this record. There can be 1 to 255 data
34 bytes per record (see cc) All bytes in the record are separated
35 from each other (and the checksum) by a space.
36 ssss Data Checksum, adding all bytes of the data line together,
38 forming a 16 bit checksum. Covers only all the data bytes of
39 this record.
40 Please note that there is no End Of File record defined.
42 Byte Count
44 The byte count cc counts the actual data bytes in the current record.
45 Usually records have 16 data bytes. I don't know what the maximum num‐
46 ber of data bytes is. It depends on the size of the data buffer in the
47 EMON52.
48 Address Field
50 This is the address where the first data byte of the record should be
51 stored. After storing that data byte, the address is incremented by 1
52 to point to the address for the next data byte of the record. And so
53 on, until all data bytes are stored.
54 The address is represented by a 4 digit hex number (2 bytes), with the
56 MSD first.
57 Data Field
59 The payload of the record is formed by the Data field. The number of
60 data bytes expected is given by the Byte Count field.
61 Checksum
63 The checksum is a 16 bit result from adding all data bytes of the
64 record together.
65 Size Multiplier
67 In general, binary data will expand in sized by approximately 3.8 times
68 when represented with this format.
69
71 Here is an example of an EMON52 file:
72 10 0000:57 6F 77 21 20 44 69 64 20 79 6F 75 20 72 65 61 0564
73 10 0010:6C 6C 79 20 67 6F 20 74 68 72 6F 75 67 68 20 61 05E9
74 10 0020:6C 6C 20 74 68 69 73 20 74 72 6F 75 62 6C 65 20 05ED
75 10 0030:74 6F 20 72 65 61 64 20 74 68 69 73 20 73 74 72 05F0
76 04 0040:69 6E 67 21 015F
77
79 http://sbprojects.fol.nl/knowledge/fileformats/emon52.htm
80
82 This man page was taken from the above Web page. It was written by San
83 Bergmans <sanmail@bigfoot.com>
84Reference Manual SRecord srec_emon52(5)