gnupic: Re: [gnupic] Re: [orders] Re: [gnupic] gpasm hex files, compatibility with odyssey
Subject:
Re: [gnupic] Re: [orders] Re: [gnupic] gpasm hex files, compatibility with odyssey
From:
Ian Jackson ####@####.####
Date:
31 May 2007 18:23:36 +0100
Message-Id: <18015.1172.995755.335687@chiark.greenend.org.uk>
Tim Allen writes ("Re: [gnupic] Re: [orders] Re: [gnupic] gpasm hex files, compatibility with odyssey"):
> It appears that no one else uses this programmer software- can anyone
> suggest a better one. We only use Linux / Unix in the labs and I
> would prefer one that is configurable and uses the parallel port.
I use odyssey to program 16F458s (with hex files produced by gpasm and
gplink). I did find that .hex files aren't as straightforward and
unambiguous as might be hoped.
I don't know what's wrong with your setup but if you want to test
whether the problem is (a) odyssey can't write to your chip somehow or
(b) the hex file format is not right, here's a suggestion: edit your
tim.hex file to have some different data in it (and you might want to
shorten it too). You'll have to adjust the checksum(s) according to
the intel hex file spec (which I don't seem to have a reference to
right now).
Ian.
