Dear Rikard,

     in which business are you in that you use a different controller
     everyday - and even finish a project everyday ?

     I can tell from my experiences that with my exprogrammer, a quick
     and dirty one, 16f628 worked but 16f628a did not. There was a
     verification error aswell. I found that no data was written to it
     at all.

     Having assembled and soldered my new programmer, it worked
     immediately.

     And normally, the pics are not damaged. Buy a programmer suitable
     for this special controller and the problem is gone.

     Or

     Develop your own. I finally gave this approach up and bought one.
     I prefer to focus on programming and the final device instead of
     programming a program that runs a programmer to program my
     program which might be programmed indirectly by a remote control
     program ...

     TK

> There seems to be an error in MPLAB v7.52 regarding the configuration
> bits. Yesterday for another project, I programmed 16F886-devices
> without problem, but today in a new project, programming 16F628A is
> weird.

> I'm using ICD2, compile my assembler-code without problems, select
> ICD2 from the programmer menu, then "connect". The result:

> Connecting to MPLAB ICD 2
> ...Connected
> Setting Vdd source to MPLAB ICD 2
> Target Device PIC16F628A found, revision = Rev 0x8
> ...Reading ICD Product ID
> Running ICD Self Test
> ...Passed

> The device is found. I program the device, and get this result:

> Programming Target...
> ...Validating configuration fields
> ...Erasing Part
> ...Programming Program Memory (0x0 - 0x8F)
> Verifying...
> ...Program Memory
> ...Verify Succeeded
> Programming Configuration Bits
> .. Config Memory
> Verifying configuration memory...
> ...Verify Failed (and stopped)
> ICD0161: Verify failed (MemType = Config, Address = 0x2007, Expected
> Val = 0x3F38, Val Read = 0x3FFF)
> ICD0275: Programming failed.

> Then, I try programmer->connect (as I did above), and get this:

> Connecting to MPLAB ICD 2
> ...Connected
> Setting Vdd source to MPLAB ICD 2
> ICDWarn0020: Invalid target device id (expected=0x83, read=0x1FF)
> ...Reading ICD Product ID
> Running ICD Self Test
> ...Passed

> I thought the chip in question was bad, so I tried another 16F628A.
> Same behaviour, ICD2 find the chip, goes error when programming and
> cannot find the chip afterwards. It looks like it's been code
> protected in some way, despite I have _CP_OFF & _CP_DATA_OFF in my
> __CONFIG.

> Are the chips really code protected (and wasted), or what is happening here?

> I tried again with a new chip, same result. I have eight 16F628A
> total, but after seven chips I gave up, leaving me only one left. I
> don't dare trying it as well, because this problem looks like a real
> money waster. I've contacted Microchip for help but no response yet.


> -- 
> - Rikard - http://bos.hack.org/cv/

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist