gnupic: Re: [orders] Re: [gnupic] gpasm hex files, compatibility with odyssey
Subject:
Re: [orders] Re: [gnupic] gpasm hex files, compatibility with odyssey
From:
Robert Pearce ####@####.####
Date:
29 May 2007 19:25:51 +0100
Message-Id: <iaAGo1HV9GXGFwfy@daniel.huneausware.local>
On Tue, 29 May 2007, Tim Allen ####@####.#### wrote :
First I will echo what David said - trying to re-program the chip with
what you've just read out of it does not actually test the ability to
write, especially when the data is all blank!
Other than that:
>HelloWorld.hex (the output from gpasm)...
>
>:020000040000FA
Note ^^^^^^
>:100000000F28FF308C0000008C0B032808008E00A6
>:10001000FF308D0001208D0B0A280E0808000030EB
>:0E00200065006600FF30860007208609142860
>:00000001FF
>
I checked your gpasm output against the file you saved from odyssey.
They use the same endianism (there are three possible representations of
the PIC's 14-bit word out there), but I note odyssey did not include
that first line I've marked above. That's an Intel HEX extension for
>16bit addressing, so it's rarely needed on PICs (never on 14-bit ones).
It's possible odyssey doesn't like it, so it would be worth deleting it
as a quick test.
That said, if an incompatibility of HEX file format produces the error
message "Couldn't write to program memory" then the author of that
application should be severely reprimanded!
--
Rob Pearce http://www.bdt-home.demon.co.uk
The contents of this | Windows NT crashed.
message are purely | I am the Blue Screen of Death.
my opinion. Don't | No one hears your screams.
believe a word. |
