🚀 go-pugleaf

In article <14451@teda.UUCP> ardai@teda.UUCP (Mike Ardai) writes:
>I am looking for information on the extended Intel Hex format.
>Specifically, how does it handle addresses larger than 20 bits?

   The coding of the extended intel hex format is as follows (working in
hex)
:10030000ffffffffffffffffffff00
:10031000ffffffffffffffffffff00

This decodes to (logically) :10 0300 00 data....  00
The first set :10 is the number of data points. (i.e. 10)
   This value may be anything between 00 & FF but is generally like 20 or so.
The second set is the offset address (0300 for example)
   On the second line, the offset increments an amount equal to the number or
   previous data point +10 in this case (0300).
The set 00 is the non end set.  At the end of the file this becomes 01.
The next 20 characters in this case fffffffffffffffffff  are example hex data.
The last set is in this case 00 the checksum for the data line.
   Now the argument can start--  depending on what manufacturers interpretation
of the intel 'standard' is used the following may be true (from my experience,
others are also possible I suppose and just as arbitrary....).
The check sum should (in my opinion) be the hex value required to max the sum
total of the entire line (ignoring the : of course) to the next even multiple
of 100 hex.  Some mfg's do not inlcude the non-data information, and this case
that is 10030000.  The other common change is to use something other than 100
as the divisor.

Hope this helps
al


--
Al. Michielsen, Mechanical & Aerospace Engineering, Syracuse University
 InterNet: amichiel@rodan.acs.syr.edu  amichiel@sunrise.acs.syr.edu
 Bitnet: AMICHIEL@SUNRISE