Sign in
Search piclist
Subscribe to piclist
piclist by Keywords
12F675 | 16F628 | 16F84 | 16f877 | 16F877A | 16F88 | 18F458 | ADC | AVR | Bootloader | CAN | CCS | CRC | EAGLE | EEPROM | ICD | ICSP | IDE | JDM | LED | Macros | Microchip | MPLAB | PCB-CAD | PIC10F | Pic12f675 | PIC16F84 | PIC16F84A | PIC16F877 | PIC18 | PIC18F452 | PicBasic | PICC | PICSTART | PWM | RS-485 | RS232 | SMT | SPI | UART | USART | USB | Wireless | Wisp628 | Xilinx
Discussion Groups
Discussion Groups | Piclist | RE: 12F6XX programming problems
A discussion group for the PICMicro microcontroller. Also called the Microchip PIC, this list is dedicated to the use and abuse of this fine, simple, microcontroller. Close to topic posts are welcome, ie. general electronics.
12F6XX programming problems - jrem123 - May 27 9:23:00 2003
|
Hey to all: I have been recently working with 12F629's and 12F675's and have encountered a bit of a problem. My setup is MPLAB, IC-PROG, and the Olimex PG2B serial programmer. Everything has been working good with the 16F684A and 16F628's, then I moved on to the 12F629's. After a few writes, the chip won't take a write any longer (verified failed at 0000h). So I move on to the next chip, and after a few (say 6 or so) burns, it won't take another write. Same with the 675's. I know the chips still have the smoke in them as I programmed them with the internal oscillator, and set the clock out on GP4, and the clock is alive (I put a scope on it). Also, with one of the chips the program allows me to 'step through' a 7 segment LED (driven by a 595). But I can't read (it reads as blank) and can't write. So I'm a bit confused . . . apparently these chips are less forgiving than the 16F6's to program? Maybe I'm doing something stupid to lock the chip from accepting a new burn? Any ideas would be appreciated . . . I've tried to search the archives here, at piclist.com, and at arch.embedded.piclist, to no avail. Maybe I'll post there too. Thanks, John. |
|
|
(You need to be a member of piclist -- send a blank email to piclist-subscribe@yahoogroups.com )
RE: 12F6XX programming problems - Wouter van Ooijen - May 27 9:35:00 2003
|
> I have been recently working with 12F629's and 12F675's and have > encountered a bit of a problem. I can't be sure because I don't know your programmer, but some PICs officially require an enter-programmer sequence that applies Vpp (13 Volt) *before* Vdd (5 Volt). The 12F's, 16F630/676 and 16F628 are among these chips. In my expercience the 16F628 never actually needs this sequence, and the other chips can often be programmed with the 'normal' sequence (power first, then Vpp) *if* you configure the MCLR pin as MCLR. Wouter van Ooijen -- ------------------------------------------- Van Ooijen Technische Informatica: www.voti.nl consultancy, development, PICmicro products |
|
|
(You need to be a member of piclist -- send a blank email to piclist-subscribe@yahoogroups.com )
RE: 12F6XX programming problems - John Remington - May 27 9:57:00 2003
|
maybe there is the problem . . . I'm got the chips configured for the MCLR to be tied internally to VDD, freeing up that pin for I/O. I will try that, thanks. --- Wouter van Ooijen <> wrote: > > I have been recently working with 12F629's and 12F675's and have > > encountered a bit of a problem. > > I can't be sure because I don't know your programmer, but some PICs > officially require an enter-programmer sequence that applies Vpp (13 > Volt) *before* Vdd (5 Volt). The 12F's, 16F630/676 and 16F628 are > among > these chips. In my expercience the 16F628 never actually needs this > sequence, and the other chips can often be programmed with the > 'normal' > sequence (power first, then Vpp) *if* you configure the MCLR pin as > MCLR. > > Wouter van Ooijen > > -- ------------------------------------------- > Van Ooijen Technische Informatica: www.voti.nl > consultancy, development, PICmicro products __________________________________ |
(You need to be a member of piclist -- send a blank email to piclist-subscribe@yahoogroups.com )