cleeland@rex.cs.tulane.edu (Chris Cleeland) (02/14/90)
This is actually posted for a friend, and you may reach him by mail
at:
deister@udcps3.cps.udayton.edu
or you can simply reply to me and I will forward.
The subject pretty much sums things up, but I will provide some
background information also.
He has a group of very primitive 68000 boards (manufacturer unknown)
which he would like to use for a class. He also has a cross-compiler
(maybe assembler?) on a PC. What he would like to be able to do is
download object code from the PC directly to the board. I thought
that S-records would be the most intelligent means to use, as then
if they later found a language compiler that they would like to use
(assuming it produced S-records also), no modification to the receiving
end would need to be made.
So, the real question is, where can he or I get specs for the S-record
format?
Thanks!
--
--------------------------------------+--------------------------------------
Chris Cleeland | BELL: (504) 866-8186
INET: cleeland@rex.cs.tulane.edu | USnail: 1320 Lowerline, Apt. E
UUCP: cleeland@rex.UUCP | New Orleans, LA 70118
Disclaimer: "I'm a student -- I can't afford one!"
Newsgroups: comp.sys.68k
Subject: Where can I get info on Motorola S-Record format?
Reply-To: cleeland@rex.cs.tulane.edu (Chris Cleeland)
Distribution: usa
Organization: Computer Science Dept., Tulane Univ., New Orleans, LA
Keywords:
This is actually posted for a friend, and you may reach him by mail
at:
deister@udcps3.cps.udayton.edu
or you can simply reply to me and I will forward.
The subject pretty much sums things up, but I will provide some
background information also.
He has a group of very primitive 68000 boards (manufacturer unknown)
which he would like to use for a class. He also has a cross-compiler
(maybe assembler?) on a PC. What he would like to be able to do is
download object code from the PC directly to the board. I thought
that S-records would be the most intelligent means to use, as then
if they later found a language compiler that they would like to use
(assuming it produced S-records also), no modification to the receiving
end would need to be made.
So, the real question is, where can he or I get specs for the S-record
format?
Thanks!
--
--------------------------------------+--------------------------------------
Chris Cleeland | BELL: (504) 866-8186
INET: cleeland@rex.cs.tulane.edu | USnail: 1320 Lowerline, Apt. E
UUCP: cleeland@rex.UUCP | New Orleans, LA 70118
Disclaimer: "I'm a student -- I can't afford one!"mwjester@wsucsa.uucp (02/15/90)
In article <2207@rex.cs.tulane.edu>, cleeland@rex.cs.tulane.edu (Chris Cleeland) writes: > ...preamble to question deleted... > So, the real question is, where can he or I get specs for the S-record > format? One section of Motorola's manual for their ECB (a 68000 Educational Computer Board) describes S-record format, if I recall. I don't have it with me, but I can dig it up and get you the info if you don't hear from someone else in the meantime. That probably means before next week. > > Thanks! You're welcome. Max J.
ron@motmpl.UUCP (Ron Widell) (02/17/90)
In article <2207@rex.cs.tulane.edu> cleeland@rex.cs.tulane.edu (Chris Cleeland) writes: > >This is actually posted for a friend, and you may reach him by mail > [deleted] >So, the real question is, where can he or I get specs for the S-record >format? > This is asked (of me) often enough that I thought that one posting would possibly result in an eventual savings of net.bandwidth. SREC(4) UNIX 5.0 (03/21/84) SREC(4) NAME srec - S-record file and record format DESCRIPTION An S-record file consists of a sequence of specially formatted ASCII character strings. An S-record will be less than or equal to 78 bytes in length. The order of S-records within a file is of no significance and no particular order may be assumed. The general format of an S-record follows: +-------------------//------------------//-----------------------+ | type | count | address | data | checksum | +-------------------//------------------//-----------------------+ type A char[2] field. These characters describe the type of record (S0, S1, S2, S3, S5, S7, S8, or S9). count A char[2] field. These characters when paired and interpreted as a hexadecimal value, display the count of remaining character pairs in the record. address A char[4,6, or 8] field. These characters grouped and interpreted as a hexadecimal value, display the address at which the data field is to be loaded into memory. The length of the field depends on the number of bytes necessary to hold the address. A 2-byte address uses 4 characters, a 3-byte address uses 6 characters, and a 4-byte address uses 8 characters. data A char [0-64] field. These characters when paired and interpreted as hexadecimal values represent the memory loadable data or descriptive information. checksum A char[2] field. These characters when paired and interpreted as a hexadecimal value display the least significant byte of the ones complement of the sum of the byte values represented by the pairs of characters making up the count, the address, and the data fields. Each record is terminated with a line feed. If any additional or different record terminator(s) or delay characters are needed during transmission to the target system it is the responsibility of the transmitting program to provide them. S0 Record The type of record is 'S0' (0x5330). The address Page 1 (last mod. 8/15/84) SREC(4) UNIX 5.0 (03/21/84) SREC(4) field is unused and will be filled with zeros (0x0000). The header information within the data field is divided into the following subfields. mname is char[20] and is the module name. ver is char[2] and is the version number. rev is char[2] and is the revision number. description is char[0-36] and is a text comment. Each of the subfields is composed of ASCII bytes whose associated characters, when paired, represent one byte hexadecimal values in the case of the version and revision numbers, or represent the hexadecimal values of the ASCII characters comprising the module name and description. S1 Record The type of record field is 'S1' (0x5331). The address field is intrepreted as a 2-byte address. The data field is composed of memory loadable data. S2 Record The type of record field is 'S2' (0x5332). The address field is intrepreted as a 3-byte address. The data field is composed of memory loadable data. S3 Record The type of record field is 'S3' (0x5333). The address field is intrepreted as a 4-byte address. The data field is composed of memory loadable data. S5 Record The type of record field is 'S5' (0x5335). The address field is intrepreted as a 2-byte value and contains the count of S1, S2, and S3 records previously transmitted. There is no data field. S7 Record The type of record field is 'S7' (0x5337). The address field contains the starting execution address and is intrepreted as 4-byte address. There is no data field. S8 Record The type of record field is 'S8' (0x5338). The address field contains the starting execution address and is intrepreted as 3-byte address. There is no data field. S9 Record The type of record field is 'S9' (0x5339). The address field contains the starting execution address and is intrepreted as 2-byte address. There is no data field. Page 2 (last mod. 8/15/84) SREC(4) UNIX 5.0 (03/21/84) SREC(4) EXAMPLE Shown below is a typical S-record format file. S00600004844521B S1130000285F245F2212226A000424290008237C2A S11300100002000800082629001853812341001813 S113002041E900084E42234300182342000824A952 S107003000144ED492 S5030004F8 S9030000FC The file consists of one S0 record, four S1 records, one S5 record and an S9 record. The S0 record is comprised as follows: S0 S-record type S0, indicating it is a header record. 06 Hexadecimal 06 (decimal 6), indicating that six character pairs (or ASCII bytes) follow. 00 00 Four character 2-byte address field, zeroes in this example. 48 ASCII H, D, and R - "HDR". 1B The checksum. The first S1 record is comprised as follows: S1 S-record type S1, indicating it is a data record to be loaded at a 2-byte address. 13 Hexadecimal 13 (decimal 19), indicating that nineteen character pairs, representing a 2 byte address, 16 bytes of binary data, and a 1 byte checksum, follow. 00 00 Four character 2-byte address field; hexidecimal address 0x0000, where the data which follows is to be loaded. 28 5F 24 5F 22 12 22 6A 00 04 24 29 00 08 23 7C Sixteen character pairs representing the actual binary data. 2A The checksum. The second and third S1 records each contain 0x13 (19) character pairs and are ended with checksums of 13 and 52, respectively. The fourth S1 record contains 07 character pairs and has a checksum of 92. The S5 record is comprised as follows: S5 S-record type S5, indicating it is a count record indicating the number of S1 records. Page 3 (last mod. 8/15/84) SREC(4) UNIX 5.0 (03/21/84) SREC(4) 03 Hexadecimal 03 (decimal 3), indicating that three character pairs follow. 00 04 Hexadecimal 0004 (decimal 4), indicating that there are four data records previous to this record. F8 The checksum. The S9 record is comprised as follows: S9 S-record type S9, indicating it is a termination record. 03 Hexadecimal 03 (decimal 3), indicating that three character pairs follow. 00 00 The address field, hexadecimal 0 (decimal 0) indicating the starting execution address. FC The checksum. Page 4 (last mod. 8/15/84) A note (or minor nit)- This is the first time that *I* have ever seen the 78-byte limit on total record length or 64-byte limit on data length. I wouldn't trust those values. Note also that the count field can have values in the range of 0x3-0xff (2 bytes of address + 1 byte checksum = 3, a not very useful record), and that this is the count of remaining character *PAIRS*, including checksum. Whenever I write code to convert S-Records, I always assume that a record can be as long as 514(decimal) characters in length (255 * 2 = 510, plus 4 characters for the type and count fields), plus any terminating character(s). That is, in establishing an input buffer in C, I would declare it to be an array of 515 chars, and leave room for the terminating null character. That should cover it :-) -- Ron Widell, Field Applications Eng. |UUCP: {...}mcdchg!motmpl!ron Motorola Semiconductor Products, Inc., |Voice:(612)941-6800 9600 W. 76th St., Suite G | I'm from Silicon Tundra, Eden Prairie, Mn. 55344 -3718 | what could I know?
cleeland@rex.cs.tulane.edu (Chris Cleeland) (02/19/90)
As the original poster of this request, I must thank everyone who posted and mailed both the information that I requested, along with possible better or more elegant solutions to the problem. What was most astounding was that I posted at about 11 pm one night, and the next morning had my mailbox filled with messages. For the next two days I had to 'biff n' because I couldn't get any work done :-) I have not received any requests for summaries, but if anyone is interested in hearing about what was suggested, drop me a note. I'll either e-mail or post depending on volume (either way I'll let ya'll know where to look). The summary won't go out before next weekend as I have *too many* midterms this week to even be writing this post. Thanks to all! -cj -- --------------------------------------+-------------------------------------- Chris Cleeland | BELL: (504) 866-8186 INET: cleeland@rex.cs.tulane.edu | USnail: 1320 Lowerline, Apt. E UUCP: cleeland@rex.UUCP | New Orleans, LA 70118 Disclaimer: "I'm a student -- I can't afford one!"
aaron@cbnewsh.ATT.COM (aaron.michael.chesir) (02/20/90)
If you have a DATA I/O prom burner manual, the details are in the appendix. Aaron Michael Chesir AT&T Bell Laboratories Room HO3C206 ..att!twitch!aaron