gnupic: Re: [gnupic] gpasm hex files, compatibility with odyssey
Subject:
Re: [gnupic] gpasm hex files, compatibility with odyssey
From:
"Tamas Rudnai" ####@####.####
Date:
29 May 2007 17:34:35 +0100
Message-Id: <492f1420705290934y6c29cbc7w1bfa1806808d2106@mail.gmail.com>
Just wondering: could it be possible that the end-of-line character is
different than your programmer accept? For example CRLF expected but only LF
are there or vica versa?
Tamas
On 5/29/07, David Barnett ####@####.#### wrote:
>
> Have you verified that the generated HEX file looks normal (not extremely
> short/empty, etc.)? I don't know anything about odyssey, but there's not
> much to the HEX files that could be "incompatible" with anything...they're
> just bytes and checksums. Is it possible you enabled code protect on your
> chip? The HEX file you read could also be empty if you haven't already
> checked that.
>
> David Barnett
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
>
>
