>
>Most of the Hex formats have information type record types in their format
>what has been missing is universal consensus over the format of an
>identification type record.
>
>I am all in favor of putting identifying information in the HEX file.
>The MPC compiler has processor and configuration information
>internally and it is easy to bring this information out.
>
>We believed that processor identification was important and when we
>developed the .COD file format included it in Byte Craft's .COD file.
>
>
>Walter Banks
>http://www.bytecraft.com
>

I believe Parallax implemented some of the earliest HEX file encodings of
PIC device types.  This is probably the nearest thing to a standard.  It is
compatible with the last Parallax tools (SPASM and SPEP) and all current
TechTools tools (CVASM, PICWriter and TDE).  I believe there are also a
number of 3rd party programmers, assemblers and compilers that adopted this
encoding as well.

This format is accepted by many, but the device code selections may have
diverged recently.  We added about 40 new devices to our assembler and
programmer recently and,of course, made up new device codes for these new
devices.

I would be willing to document the Parallax encoding and the TechTools
extent ions and open it for comments, if there is enough interest.


Jerry Merrill

jerrym@tech-tools.com
http://www.tech-tools.com
FAX: (972) 494-5814
VOICE:(972) 272-9392
TechTools
PO Box 462101
Garland,  TX  75046-2101