PDA

View Full Version : programmer compatability, 16f88



cphillips82
- 22nd July 2008, 04:54
Could somebody please give me an idea as to why my programmer won't program 16f88 pic's.
I'm trying to load a simple program


CMCON = 7 ' Disable Comparators
ansel = 0

start:
portb.0 = 1
pause 1000
portb.0 = 0
pause 1000
goto start

through my pic programer and checker board which I have programmed 16f84 and 16f628's many times before and still do, Ive included a picture of the schematic. I am using icprog with direct I/O invert mclear and invert vcc checked.cheers in advanced

Raflex
- 22nd July 2008, 08:04
Hello, Is software problem or hardware proble?

If its in software, you need to use TRIS command to select input or output on a pin and config directives like internal or external osc, mclr, etc.

However, if you cant read/write your pic, probably it is not supported by your programmer.

cphillips82
- 22nd July 2008, 11:27
i cannot get the program on to the pic, I just want to know what is the electrical programming difference between the 16f628 , 84 to the 88??? I wouldnt think there would be any?

eggman
- 22nd July 2008, 12:19
Does your programmer support this PIC?

skimask
- 22nd July 2008, 13:49
i cannot get the program on to the pic, I just want to know what is the electrical programming difference between the 16f628 , 84 to the 88??? I wouldnt think there would be any?

www.microchip.com has all the programming specifications for the various PICs in various PDFs. And yes, there is a difference between the programming methods used from the 16f628 (old school) and the 16f88 (newer-ish school). Just because a programmer supports the 16f628/16f84 (old school), doesn't mean it supports the 16f88 (much newer in comparison).
From the date on those pictures, it looks like 2001. I'm fairly sure that the 16F88 came out after much later.

cphillips82
- 22nd July 2008, 14:00
yes, this was made well before the 16f88 was out and even before the 16f628 yet that still works. seems a shame. I LOVE THIS BOARD!!

skimask
- 22nd July 2008, 14:11
yes, this was made well before the 16f88 was out and even before the 16f628 yet that still works. seems a shame. I LOVE THIS BOARD!!
In most cases, it's not the programmer hardware that makes or breaks it for a specific PIC, it's the firmware/software that's driving it.

cphillips82
- 22nd July 2008, 14:22
icprog has seems like it should be able to handle it. it does com up with some other options when the 16f88 is selected which i'm not sure of, eg write enable, ccpmx?? i may try winpic

cphillips82
- 22nd July 2008, 15:07
absolutely fluked it!!! winpic set as tait 7407 + pnp didnt work so played around abit and hit the "raise Vdd before MCLR = Vpp " ????? Bingo. think I may give myself a beer or 10 for that. it was the software letting her down like you said. she still got a few years left in her!!

mvs_sarma
- 24th July 2008, 20:48
Are you not expected to indicate the chip and full configuration data while writing programs in BASIC?

Bruce
- 24th July 2008, 23:10
If you're using PORTB.0=1 or PORTB.0=0 you'll want to include TRISB.0=0 first to make the
pin an output, or change to HIGH 0 / LOW 0. Port pins are set as inputs by default on
power-up.

HIGH & LOW commands will automatically handle setting TRIS for you, where PORTB.0=? will
not.