srec_emon52(5) File Formats Manual srec_emon52(5)NAME
srec_emon52 - Elektor Monitor (EMON52) file format
DESCRIPTION
This format is used by the monitor EMON52, developed by the European electronics magazine Elektor (Elektuur in Holland). Elektor wouldn't
be Elektor if they didn't try to reinvent the wheel. It's a mystery why they didn't use an existing format for the project. Only the
Elektor Assembler will produce this file format, reducing the choice of development tools dramatically.
Records
All data lines are called records, and each record contains the following four fields:
+---+------+---+-----------+------+
|cc | aaaa | : | dd ... dd | ssss |
The field are defined as follows: +---+------+---+-----------+------+
cc The byte count. A two digit hex value (1 byte), counting the actual data bytes in the record. The byte count is separated from
the next field by a space.
aaaa The address field. A four hex digit (2 byte) number representing the first address to be used by this record.
: The address field and the data field are separated by a colon.
dd The actual data of this record. There can be 1 to 255 data bytes per record (see cc) All bytes in the record are separated from
each other (and the checksum) by a space.
ssss Data Checksum, adding all bytes of the data line together, forming a 16 bit checksum. Covers only all the data bytes of this
record.
Please note that there is no End Of File record defined.
Byte Count
The byte count cc counts the actual data bytes in the current record. Usually records have 16 data bytes. I don't know what the maximum
number of data bytes is. It depends on the size of the data buffer in the EMON52.
Address Field
This is the address where the first data byte of the record should be stored. After storing that data byte, the address is incremented by
1 to point to the address for the next data byte of the record. And so on, until all data bytes are stored.
The address is represented by a 4 digit hex number (2 bytes), with the MSD first.
Data Field
The payload of the record is formed by the Data field. The number of data bytes expected is given by the Byte Count field.
Checksum
The checksum is a 16 bit result from adding all data bytes of the record together.
Size Multiplier
In general, binary data will expand in sized by approximately 3.8 times when represented with this format.
EXAMPLE
Here is an example of an EMON52 file:
10 0000:57 6F 77 21 20 44 69 64 20 79 6F 75 20 72 65 61 0564
10 0010:6C 6C 79 20 67 6F 20 74 68 72 6F 75 67 68 20 61 05E9
10 0020:6C 6C 20 74 68 69 73 20 74 72 6F 75 62 6C 65 20 05ED
10 0030:74 6F 20 72 65 61 64 20 74 68 69 73 20 73 74 72 05F0
04 0040:69 6E 67 21 015F
SEE ALSO
http://sbprojects.fol.nl/knowledge/fileformats/emon52.htm
AUTHOR
This man page was taken from the above Web page. It was written by San Bergmans <sanmail@bigfoot.com>
Reference Manual SRecord srec_emon52(5)
Check Out this Related Man Page
srec_stewie(5) File Formats Manual srec_stewie(5)NAME
srec_stewie - Stewie's binary file format
DESCRIPTION
If you have a URL for documentation of this format, please let me know.
Any resemblance to the Motorola S-Record is superficial, and extends only to the data records. The header records and termination records
are completely different. None of the other Motorola S-Records record type are available.
The Records
All records start with an ASCII capital S character, value 0x53, followed by a type specifier byte. All records consist of binary bytes.
The Header Record
Each file starts with a fixed four byte header record.
+-----+------+------+------+
|0x53 | 0x30 | 0x30 | 0x33 |
+-----+------+------+------+
The Data Records
Each data record consists of 5 fields. These are the type field, length field, address field, data field, and the checksum. The lines
always start with a capital S character.
+-----+------+---------------+---------+------+----------+
|0x53 | Type | Record Length | Address | Data | Checksum |
+-----+------+---------------+---------+------+----------+
Type The type field is a one byte field that specifies whether the record has a two-byte address field (0x31), a three-byte address
field (0x32) or a four-byte address field (0x33). The address is big-endian.
Record Length
The record length field is a one byte field that specifies the number of bytes in the record following this byte.
Address This is a 2-, 3- or 4-byte address that specifies where the data in the record is to be loaded into memory.
Data The data field contains the executable code, memory-loadable data or descriptive information to be transferred.
Checksum
The checksum is a one byte field that represents the least significant byte of the one's complement of the sum of the values repre-
sented by the bytes making up the record's length, address, and data fields.
The Termination Record
Each file ends with a fixed two byte termination record.
+-----+------+
|0x53 | 0x38 |
+-----+------+
Size Multiplier
In general, binary data will expand in sized by approximately 1.2 times when represented with this format.
EXAMPLE
Here is an hex-dump example file. It contains the data "Hello, World[rq] to be loaded at address 0.
0000: 53 30 30 33 53 31 10 00 00 48 65 6C 6C 6F 2C 20 S003S1...Hello,
0010: 57 6F 72 6C 64 0A 9D 53 38 World..S8
COPYRIGHT
srec_cat version 1.58
Copyright (C) 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011 Peter Miller
The srec_cat program comes with ABSOLUTELY NO WARRANTY; for details use the 'srec_cat -VERSion License' command. This is free software and
you are welcome to redistribute it under certain conditions; for details use the 'srec_cat -VERSion License' command.
AUTHOR
Peter Miller E-Mail: pmiller@opensource.org.au
//* WWW: http://miller.emu.id.au/pmiller/
Reference Manual SRecord srec_stewie(5)