gnupic: Re: [gnupic] Cannot get 18f252 to blink
Subject:
Re: [gnupic] Cannot get 18f252 to blink
From:
Jeff ####@####.####
Date:
25 Oct 2006 04:09:48 +0100
Message-Id: <200610242006.44430.j_post@pacbell.net>
On Tue October 24 2006 11:17, David Froseth wrote:
>
> The .hex file is :
> :020000040000FA
> :040000000CEF00F011
> :08001800060EC16EFE0E926E91
> :10002000FF0E936E000E946E010E801A1AEC00F013
> :1000300014EF00F0FF0E206EFF0E216E212E1EEF3A
> :0A00400000F0202E1CEF00F012006B
> :020000040030CA
> :08000000FF210E0EFF0181FF3C
> :00000001FF
>
> When I read the program memory out of the chip, I get:
>
> $ picp /dev/tty.KeySerial1 18f252 -rp
>
> :020000040000FA
> :10000000040E0060000E926E9200000E000E0000C2
> :10001000010C0000000000000000000000000000D3
> :10002000000000000000000E000000000020006042
> :100030000000000000000000020E016C0020046EB1
> :100040000000000E004000000000012E250E0020E0
> :10005000002023EF00F0020026EF00F0082E24EF2E
> :1000600000F0052E22EF00F0120037EF00F00150F3
> :10007000806E1200FFFFFFFFFFFFFFFFFFFFFFFF8C
> :10070000F9263F0C060C5B0C4F0C660C6D0C7D0C37
> :10071000070C7F0C6F0C400CFFFFFFFFFFFFFFFF7C
> :00000001FF
>
> This obviously does not look the same. Is this normal? Other chips
> that are working show program memory reads that are different than the
> .hex file, also. I know nothing about how .hex files work.
>
The hex files won't have the same format, but the data should be the same. The
data in these two files is not the same. Either the code was not programmed
correctly or it's not being read back correctly. I assume you also used picp
to program the chip.
I have virtually zero free time until mid to late December, so development on
both picp and pk2 has come to a screeching halt, but I'll try to find time
this weekend to at least duplicate the problem if not fix it, assuming that
it is a picp problem. In the meantime, try programming other 18F252s and see
if you get the same results.
Jeff
