gnupic: Re: [gnupic] gpasm hex files, compatibility with odyssey
Subject:
Re: [gnupic] gpasm hex files, compatibility with odyssey
From:
"David Barnett" ####@####.####
Date:
29 May 2007 18:45:07 +0100
Message-Id: <00d401c7a219$11e74600$0301a8c0@barnett2>
----- Original Message -----
From: "Tim Allen" ####@####.####
To: ####@####.####
Sent: Tuesday, May 29, 2007 11:43 AM
Subject: Re: [gnupic] gpasm hex files, compatibility with odyssey
>I would expect my HelloWorld hex file to be short as there not much to it;
>however, a read of the entire chip I would expect to be much larger- I
>assume zero padding is not necessary as no one has mentioned it. I have
>pasted the respective hex files... As for the write protect, it's a new
>chip and I am able to write back the hex that I read from the chip using
>odyssey.
>
> tim.hex (the file read via odyssey from the chip):
>
> :10000000FF3FFF3FFF3FFF3FFF3FFF3FFF3FFF3F00
> ...
> :10420000FF00FF00FF00FF00FF00FF00FF00FF00B6
> ...
I think those are just the default memory values when you blank out the
chip. At any rate, since you're writing exactly what you read, the verify
will pass whether the write worked or not. I think chips with code protect
active will still do this.
I'm not sure what memory range they're in offhand, but I think the read
includes the config bits, so you can check for sure whether code protect is
enabled or not if you look them up and check their values. FYI, the HEX
format is something like: address, length, data, checksum on each line. I
think 3FFF is the default and translates to a nop instruction.
It might be something else entirely, but that's the best I could tell you.
David Barnett
