gnupic: Gpasm / Mpasm hex file compatibility


Previous by date: 1 Mar 2004 20:34:22 -0000 Gpasm / Mpasm hex file compatibility, Pete Harlow
Next by date: 1 Mar 2004 20:34:22 -0000 Compiling gpasm, Franz Holzinger
Previous in thread: 1 Mar 2004 20:34:22 -0000 Gpasm / Mpasm hex file compatibility, Pete Harlow
Next in thread: 1 Mar 2004 20:34:22 -0000 Re: Gpasm / Mpasm hex file compatibility, Pete Harlow

Subject: Re: Gpasm / Mpasm hex file compatibility
From: Scott Dattalo ####@####.####
Date: 1 Mar 2004 20:34:22 -0000
Message-Id: <Pine.LNX.4.44.0403011159220.19163-100000@ruckus.brouhaha.com>

On Mon, 1 Mar 2004, Pete Harlow wrote:

> I've just assembled up a new version of some code for a client and sent 
> the hex file to him. The gpasm hex file worked fine with picp and my 
> Picstart Plus here to produce a working chip.
> However my client has used his Picstart with Mplab and this complains 
> that the hex file has a bad checksum.
> 
> Are the checksum formats different?

The problem is most probably an end-of-line issue. Try converting your 
.hex files to "dos" before sending them to your client. e.g.:

$ unix2dos hexfile.hex

Another thing I found is that some mail readers like to reformat files 
when they're saved. So the other thing I do is package the .hex file into 
a .zip file too.

Scott


Previous by date: 1 Mar 2004 20:34:22 -0000 Gpasm / Mpasm hex file compatibility, Pete Harlow
Next by date: 1 Mar 2004 20:34:22 -0000 Compiling gpasm, Franz Holzinger
Previous in thread: 1 Mar 2004 20:34:22 -0000 Gpasm / Mpasm hex file compatibility, Pete Harlow
Next in thread: 1 Mar 2004 20:34:22 -0000 Re: Gpasm / Mpasm hex file compatibility, Pete Harlow


Powered by ezmlm-browse 0.20.