There are only 5 GPIO lines on the 12F675, so subtract 2 and that leaves 3.= =20 -- James Newton 1-970-462-7764=20 -----Original Message----- From: piclist-bounces@mit.edu [mailto:piclist-bounces@mit.edu] On Behalf Of Dwayne Reid Sent: Wednesday, November 17, 2010 09:24 To: Microcontroller discussion list - Public. Subject: RE: [PIC] pickit2 unreliable debug 12F675 At 11:38 PM 11/16/2010, Steve Smith wrote: >I have to say the last app I wrote for a 675 / 629 I did entirely on an f877 >and wrote the IO conditionally so there were two compile methods and found >that was the best way of working with an 8 pin... Its quite restrictive >having only 3 I/O available whilst debugging and the F877 solution was >reasonably simple in terms of a work around that ICD2 could handle I'm not sure why you say "having only 3 i/o available while=20 debugging". You need to have the 12f675 debug header if you are=20 going to use the debug feature and that header brings out all 6 i/o lines. There are caveats: gpio3 cannot be used as an input and one pin=20 (gpio2?) must be in a particular logic state in order to send the=20 program into the flash memory but other than that, you do have access=20 to all 5 i/o lines. As mentioned: the 6th (input) line must be used as !MCLR. dwayne --=20 Dwayne Reid Trinity Electronics Systems Ltd Edmonton, AB, CANADA (780) 489-3199 voice (780) 487-6397 fax www.trinity-electronics.com Custom Electronics Design and Manufacturing --=20 http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist --=20 http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .