Not all HEX files created equally - XWISP fails on CCS HEX files.

Started by holopoint.rm June 18, 2003
Hey guys.
I have been playing with my PICs for a few weeks now,
and now I have a problem. I have a few HEX files from several
origins. One that I wrote in JAL, and one that I found on some
newsgroup that were compiled with a CCS C compiler.
The two HEX files have a different structure.
The CCS HEX has a weird ";PIC16F628" as the last line, a remark ?
The XWISP refuses to program the HEX claiming that the last line is
bad. After I removed the last line the WISP still refuses to program
the HEX, but his time offers no explanation.

Is there a standard structure for HEX files ?
Thanks,
Shachar Weis.




There are several popular formats for .hex files. MOST programmers
want what is known as Intel Hex Record Format or, as it is called in
MPLAB, INHX8M.

Check the WISP documentation - seems I recall a requirement for Intel
Hex but I just glanced briefly.

Look at http://www.cs.net/lucid/intel.htm for a description of the
format. --- In , "holopoint.rm" <holopoint@r...> wrote:
> Hey guys.
> I have been playing with my PICs for a few weeks now,
> and now I have a problem. I have a few HEX files from several
> origins. One that I wrote in JAL, and one that I found on some
> newsgroup that were compiled with a CCS C compiler.
> The two HEX files have a different structure.
> The CCS HEX has a weird ";PIC16F628" as the last line, a remark ?
> The XWISP refuses to program the HEX claiming that the last line is
> bad. After I removed the last line the WISP still refuses to
program
> the HEX, but his time offers no explanation.
>
> Is there a standard structure for HEX files ?
> Thanks,
> Shachar Weis.




> Hey guys.
> I have been playing with my PICs for a few weeks now,
> and now I have a problem. I have a few HEX files from several
> origins. One that I wrote in JAL, and one that I found on some
> newsgroup that were compiled with a CCS C compiler.
> The two HEX files have a different structure.
> The CCS HEX has a weird ";PIC16F628" as the last line, a remark ?
> The XWISP refuses to program the HEX claiming that the last line is
> bad. After I removed the last line the WISP still refuses to program
> the HEX, but his time offers no explanation.
>
> Is there a standard structure for HEX files ?

Writing XWisp I used Microchips definition, which does not mention a ';'
- comment. line. But I recently added 'ignore ;-lines', but this is not
on the webpage yet. I think that change solves your other problem as
well.

Wouter van Ooijen

-- -------
Van Ooijen Technische Informatica: www.voti.nl
consultancy, development, PICmicro products



Attachment (not stored)
xwisp.zip
Type: application/x-zip-compressed