gnupic: Re: [gnupic] gpasm hex files, compatibility with odyssey
Subject:
Re: [gnupic] gpasm hex files, compatibility with odyssey
From:
Tim Allen ####@####.####
Date:
29 May 2007 17:47:26 +0100
Message-Id: <E9E75750-8DF9-45DC-B186-21DAB659CC8C@integsys.biz>
hexdump indicates they both end in 0x0a46
On May 29, 2007, at 12:34 PM, Tamas Rudnai wrote:
> 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: ####@####.####
>>
>>
