On Tuesday 26 August 2003 15:33, Wouter van Ooijen scribbled:
> (still not asleep but going to do so soon)

Noooooooooooooooo..............    :-)


> > PIC 16F627A
>
> I'm not sure I ever tested that one but at least it should report some
> reasonable ID value.

Ding!  We have a winner.  Based on this statement, I just dug up a new 16=
F628=20
and tried it...
"python xwisp.py target 16f628" says "Ok"
"python xwisp.py target 16f628 erase" says "Ok" but then says it cannot=20
identify the device ID.

However, "python xwisp.py target 16f628 go b628i-1.hex" works now (it bli=
nks=20
the LED.


> Double-check all solder work, continuity from your target's pins up to
> the corresponding pins of the 16f628 in the programmer, and absense of
> shorts. How do you connect to the target chip? Double check your
> connections to that chip too. /MCLR pull up resistor is ~33k?

Say what!?  You doubt the quality of my work!? :-)

I did actually go thru and verify as much as I could prior to reporting,=20
including exhaustively testing the cable from the Wisp to the chip, and I=
'm=20
eliminated the serial cable for now (plugged directly into the laptop).


But now it works (mostly) with the 16F628, so I need to figure out why it=
=20
cannot identify the 16F628 and then figure out how to get it recognize th=
e=20
16F627A.  Hints appreciated.

BTW, the whole reason I finally got off my butt and finally decided to se=
tup=20
Wisp is because the Tait parallel programmer was having issues programmin=
g=20
(pre-setting) the 16F627A EEPROM.  I'm not nervous that there may be some=
=20
issue with 16F627A's, so I'll go hit the datasheets.

Much thanks,
-Neil.


---
[This E-mail scanned for viruses]

--
http://www.piclist.com hint: The list server can filter out subtopics
(like ads or off topics) for you. See http://www.piclist.com/#topics