Talk:SREC (file format)

message: Need to add more to the SREC file format description here
anyone have any comments?
JBadger169 (talk) 14:23, 29 November 2007 (UTC)
replies: text: I added some more content, axed the duplicate S19 page, and rewrote some stuff. Also, I removed the link to Altera. This article could have a list of embedded software packages that offer S-record support, but it would be a long list. I think this is turning into a nice little article on an arcane subject. There are some remaining issues with this article that I haven't addressed yet. Both the record description and the example are copied directly from the man page. I think those need to be replaced with original content, but I am not an expert on licensing. -Wronkiew (talk) 06:45, 18 December 2007 (UTC)
thread_title: Need to add more

message: There should be notes on the new banked s-record format.  This is where A S2 record the upper 8 bits has the PPAGE address and the lower 16 bits has the word address.--JBadger169 (talk) 14:04, 24 March 2008 (UTC)
replies: text: Please list which companies support it and point to a specification or documentation.  • Sbmeirow • Talk • 12:05, 30 June 2014 (UTC)
thread_title:  ‘banked’ S-Record format. 

message: :"[SREC] is used by software development tools to encode binary data, especially executable code, for embedded processors."
Exactly where in the development process is SREC used? The embedded systems I came in contact with yet work on "true" binary files. --Abdull (talk) 19:44, 9 March 2010 (UTC)
replies: text: E.g. for the real time operating system QNX, boot images can be built in the SREC format.  —Preceding unsigned comment added by 71.246.14.17 (talk) 19:28, 14 December 2010 (UTC)
replies: text: In my present job (automotive industry), we're also using Intel Hex and Motorola SREC files for all kinds of controllers. --Antred (talk) 10:54, 30 November 2016 (UTC)
thread_title:  Usage of SREC? 

message: The picture titled "Motorola SREC Chart.png" seems to have an error. The graphics claims that the checksum is 2 bytes when in fact it's only 1 byte. --Antred (talk) 16:57, 29 November 2016 (UTC)
replies: text: The graphic is correct, but the author of that graphic should have described it differently.  The checksum is one binary byte, which requires 2 ASCII characters to represent it, each ASCII character is 1 byte, thus 2 bytes is correct.  • Sbmeirow • Talk • 02:58, 30 November 2016 (UTC)
replies: text: I see. You're right; I hadn't realized that he basically meant the characters needed to represent the checksum byte. --Antred (talk) 10:14, 30 November 2016 (UTC)
thread_title: Small error in the explanatory graphic

message: I've found a very early reference to this format, perhaps among the earliest, in Motorola's M6800 Microprocessor Applications Manual, published in early 1975, on page 5-57 and following, in a description of an example of a teletype-based communications link for a Motorola 6800 system. The paper-tape-based format there is not called "SREC", but its description matches the SREC format. (Incidentally, this description also mentions a length limit of 70 characters—paper tape frames—for each record.) Just noting this as a possible historical reference. --Colin Douglas Howell (talk) 07:20, 27 March 2022 (UTC)
thread_title:  Early reference to this format in a 1975 Motorola 6800 manual