home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: sci.electronics
- Path: sparky!uunet!keinstr!chaplin
- From: chaplin@keinstr.uucp (Roger Chaplin)
- Subject: Re: Motorola S19 ==> S2 record. How?
- Message-ID: <1992Nov13.141225.26488@keinstr.uucp>
- Organization: Keithley Instruments, Cleveland, Ohio
- X-Newsreader: TIN [version 1.1 PL6]
- References: <4772@wet.UUCP>
- Distribution: usa
- Date: Fri, 13 Nov 1992 14:12:25 GMT
- Lines: 54
-
- Gil Nardo (mcs@wet.UUCP) wrote:
- : U40348@uicvm.uic.edu (Jay Lorenzana) writes:
- : > Our school is ill-equipped. We have an old eprom burners
- : > that will only program Motorola S1 and S2 record files. How
- : > can I convert my S19 record file to S1 and S2?
- : > Are there any complications in modifying hex files?
- : > And what is a hex to obj file converter?
- : > Thanks for any help you can give,
- : > Jay
- : > A piece of my s19 rec:
- : > S123C00000000000000000BDC048BDC09ABDC063BDC0A5BDC0BA7FC0037DC0002605BDC0E0
- : > S123C020CE20F30F7DC002261A1A8300FF2B02200DCE10001F2E40FC962ED72F20D5BDC2F2
- : > S123C0408120D0BDC28B20CBCE10008EDFFF862F97EECCD000DDEFC60CE73F86100686016F
- : > ......
- : > lines deleted
- : > ......
- : > S123C3E02A2A204552524F52202A2A202020202020202020202020202020202055702020A2
- : > S121C40020202020202020202020446F776E204A4F59535449434B204D4F444520202D
- : > S123D0008600BDC285FEC001140301BDC156432607BDC110BDC0BA3B432607BDC237BDC0C4
- : > S123D020BA3B432607BDC1CFBDC0BA3B4326158C000026013BBDC1D01400017DC00427038E
- : > S121D040BDC0BA3B8C00002603BDC110BDC0FDBDC14F8C00112706BDC0BABDC3313BE5
- : > S9030000FC
- :
- : The sample you have shown appear to be the usual S-records,
- : where S1 lines refer to 2 byte address references, and the
- : S9 line terminates the S1 block.
- : I'm not sure what exactly it is you are trying to do. The
- : two possibilities are that you are trying to decipher what
- : each line means, and/or you are trying to convert S1 records
- : to S2 records, i.e., your eprom burner only accepts 3 byte
- : address references.
-
- Another possibility is that the EPROM burner was designed with the
- assumption that all S1S9 records are `short' - that is, containing
- only 16 encoded bytes. It is unusual (in my experience, anyway) to
- see S1S9 records which are this long.
-
- Perhaps something to try is converting these `long' records to short
- ones. E.g. this record:
- S123D0008600BDC285FEC001140301BDC156432607BDC110BDC0BA3B432607BDC237BDC0C4
-
- would become these two:
- S113D0008600BDC285FEC001140301BDC1564326??
- S113D01007BDC110BDC0BA3B432607BDC237BDC0??
-
- (I was too lazy to calculate the proper checksums, so I just put in
- `??' instead.) Notice that `S123' (16-bit address, 35 bytes to follow)
- changes to `S113' (16-bit address, 19 bytes to follow).
-
- --
- Roger Chaplin / Instruments Division Engineering / "This land is your land,
- chaplin@keinstr.uucp / CI$: 76307,3506 / This land is my land,
- #include <disclaimer.h> / One of us has a bogus deed
- #include "disclaimer.h" /* cover all bases */ / to this land." - George Carlin
-