![]() ![]() If you have this problem, the -data-only option can be used to suppress just about everything except the data. Just the Data, Please There are some bonehead EPROM programmers which can only cope with data records, and are unable to cope with header records or execution start address Srec_cat long.srec -o short.s19 -line-length=46 The line length option interacts with the address length option, so some tinkering to optimize for your particular situation many be necessary. The -line-length option may be used to specify the maximum line length (not including the newline) to be used on output. All EPROM programmers should have sufficiently large buffers to cope with The Motorola S-record format definition permits up to 255 bytes of payload. Line Lengths From time to time you will come across a feeble-minded EPROM programmer that can't cope with long SRecord lines, they assume that there will only ever be 16īytes of data per line, and barf when they see the default 32 byte payloads that srec_cat(1) writes. This section also applies to Intel hex files, as they, too, have the ability to select from a variety of address widths. ![]() Srec_cat short.srec -o long.srec -address-length=4 This command says to use four byte (32-bit) addresses on output. ![]() It is possible to convert from one Motorola shape to another using the -Address-Length option: ForĮxample, some compilers produce "s19" Motorola data (that is, S1 data records with S9 start records, 16 bit address fields) which would be OK except that someīlockhead EPROM programmers insist on "s37" Motorola data (that is, S3 data records with S7 start records, 32 bit address fields). Srec_cat srec-file -o intel-file -intel The default format is Motorola S-Record format, so it does not need to be specified.ĭifferent Shapes of the Same Format It is regrettably common that some addle-pated EPROM programmers only implement a portion of the specification used to represent their hex files. Motorola to Intel Converting the other way is just as simple: (Except the assembler, BASIC, C and FPGA outputs which are write Srec_cat intel-file -intel -o srec-file Pick any two formats that SRecord understands, it can convert between all of them. Intel to Motorola One of the simplest examples is converting files from Intel hex format to Motorola S-Record format: They are only broken out separately to make them easier to understand. You can do many of these things simultaneously in one command. Please keep in mind, as you read this section, that The simplest of the things srec_cat(1) can do is convert from one EPROM file format to another. Send your example in an email to the email address at the end of this manual page. Your Examples Wanted If you have a clever way of using SRecord, or have solved a difficult problem with SRecord, you could contribute to this manual page, making it more usefulįor everyone. Of course, you could always upgrade to Linux, which has been sucking less for over 21 years now. Comments start at a " #" and extend to the end of the line. Srec_cat This also has the advantage of allowing comments, allowing you to write your command line options over several lines, and even indenting to make the command ![]() You can getĪround this handicap by placing your command line in a file, say fred.txt, and then tell srec_cat(1) to read this file for the rest of its The Commands Lines Are Too Long If you are marooned on an operating system with absurdly short command line length limits, some of the commands which follow may be too long. But these are only examples, for more complete details, This manual page describes how to use the various input files, input filters and input generators. The srec_cat command is very powerful, due to the ability to combine the the input filters in almost unlimited ways. ![]()
0 Comments
Leave a Reply. |