Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!bloom-beacon!oberon!cit-vax!ucla-cs!zen!ucbvax!UHHEPG.BITNET!RALPH
From: RALPH@UHHEPG.BITNET
Newsgroups: comp.os.cpm
Subject: Details of Intel Hex Format
Message-ID: <8709250902.AA06771@ucbvax.Berkeley.EDU>
Date: Fri, 25-Sep-87 05:02:55 EDT
Article-I.D.: ucbvax.8709250902.AA06771
Posted: Fri Sep 25 05:02:55 1987
Date-Received: Sat, 26-Sep-87 18:43:44 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 31

Date: 24-SEP-1987 22:47:39.34
From: Ralph Becker-Szendy RALPH AT UHHEPG
To:   BITNET::"info-cpm@simtel20.arpa",RALPH
Subj: Details of Intel Hex Format
Hi

i have a very stupid problem: for the first time in my life, i have to create
an Intel hex-file by hand (or rather by a program i wrote, and not by an
assembler or suchlike) to download it ionto an EPROM programmer.
Unfortunately, so far the EPROM programmer refused all my attempts, presumably
due to a format or checksum error in the hex file (it works fine otherwise);
it does beautifully work with other hex files.

Let my explain how one record in the hex-file i write looks like:
each byte is in hexadecimal, written as two (uppercase) ASCII characters.
- a colon ":"
- one byte # of data bytes, in my case "10"
- two bytes load adress, first high, then low byte
- one byte record type (always "00")
- 16 bytes of data
- one byte checksum.
- CR and LF
The checksum is calculated such that the sum of all bytes (including the
"10" and the two adress bytes) is a multiple of 256.

Is there anything wrong with this format ? If yes, what ??

Signed: confused

Ralph Becker-Szendy
University of Hawaii / High Energy Physics Group