Hello, Alberto,
I've built your OpenProg for PIC10/12 and used it successfully.
But now I have problems with PIC16LF88 (tried 3 of them).
I checked my boards for successful programming by ICD3, to ensure there are no other problems.
The problem with OpenProg looks like this:
un-stable results for programming / reading.
For reading of PIC with known programmed code:
One reading returns 'empty' code, unknown controller.
Next reading returns code with 0xE00 'offset' of address, that is,
"DevID: 0x0765
16F88 rev5
Configuration word: 0x2F38
Configuration word2 or calibration word 1: 0x3FFC
Code memory:
0E00: 2100 018B 3090 2812 00F0 0E03 0183 00A6 0801 00A4 0181 108B 16B0 0E26 0083 0EF0
...."
but this is exact code which starts actually at 0,
Next reading returns code with other offset:
Code memory:
0010: 3FFF 3FFF 3FFF 3FFF 3FFF 3FFF 3FFF 219F 19B0 2174 2813 1230 303C 00BF 20C7 3001
0020: 0221 1D03 282D 15B0 0008 1230 303C 00BF 20C7 1C03 0008 3000 008A 0839 0782 2841 "
Here, starting with address 0017, proceed correct code which actually begins at address 0x20.
Next reading will return some other result, it may be 'clean unknown device' or completely correct code but with some arbitrary shift in address.
It is always, if started read correct code, proceeds without any error but shift in address.
I suppose the problem is with entering programming mode
Once more, this same programmer, cables, PC, and all, does correctly work with PIC10. which I did many times.
In any case, I'm very respectful for this you project, like many others already said.
with regards,
Yuri.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello, Alberto. thanks for reply.
I have some boards with same PIC16LF88, and also one PIC-no board at all- with only prog lines (PGD,PGC,GND,MCLR, VDD) wired to prog connector. The same results for all.
Most of times it reads all zeros, as if no PIC at all.
all the boards I tried with ICD3 under MPLAB 8.83, they OK.
btw, today I used the OpenProg with PIC16LF877, it works OK.
If you ask about PGD/PGC/MCLR loaded on boards with some caps, or resistors:
no caps, 51...100k to VDD, as I always do.
With regards,
Yuri.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, Alberto. First I should say excuse for false 'problem'. OpenProg works with F88 OK.
I found the cause was burned to short PNP Q1. Don't know how it still worked with PIC16F877.
I afterwards added 100 Ohm in series to VPP output. This prevents burning Q1 even in case of dead shortage on user board.
With regards,
Yuri.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
View and moderate all "Open Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Hello, Alberto,
I've built your OpenProg for PIC10/12 and used it successfully.
But now I have problems with PIC16LF88 (tried 3 of them).
I checked my boards for successful programming by ICD3, to ensure there are no other problems.
The problem with OpenProg looks like this:
un-stable results for programming / reading.
For reading of PIC with known programmed code:
One reading returns 'empty' code, unknown controller.
Next reading returns code with 0xE00 'offset' of address, that is,
"DevID: 0x0765
16F88 rev5
Configuration word: 0x2F38
Configuration word2 or calibration word 1: 0x3FFC
Code memory:
0E00: 2100 018B 3090 2812 00F0 0E03 0183 00A6 0801 00A4 0181 108B 16B0 0E26 0083 0EF0
...."
but this is exact code which starts actually at 0,
Next reading returns code with other offset:
Code memory:
0010: 3FFF 3FFF 3FFF 3FFF 3FFF 3FFF 3FFF 219F 19B0 2174 2813 1230 303C 00BF 20C7 3001
0020: 0221 1D03 282D 15B0 0008 1230 303C 00BF 20C7 1C03 0008 3000 008A 0839 0782 2841 "
Here, starting with address 0017, proceed correct code which actually begins at address 0x20.
Next reading will return some other result, it may be 'clean unknown device' or completely correct code but with some arbitrary shift in address.
It is always, if started read correct code, proceeds without any error but shift in address.
I suppose the problem is with entering programming mode
Once more, this same programmer, cables, PC, and all, does correctly work with PIC10. which I did many times.
In any case, I'm very respectful for this you project, like many others already said.
with regards,
Yuri.
Hello, are you programming in-circuit or on-board?
View and moderate all "Open Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Hello, Alberto. thanks for reply.
I have some boards with same PIC16LF88, and also one PIC-no board at all- with only prog lines (PGD,PGC,GND,MCLR, VDD) wired to prog connector. The same results for all.
Most of times it reads all zeros, as if no PIC at all.
all the boards I tried with ICD3 under MPLAB 8.83, they OK.
btw, today I used the OpenProg with PIC16LF877, it works OK.
If you ask about PGD/PGC/MCLR loaded on boards with some caps, or resistors:
no caps, 51...100k to VDD, as I always do.
With regards,
Yuri.
If you have a chance, could you try with a device stand-alone and plug it in the programmer's own socket?
View and moderate all "Open Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Hi, Alberto. First I should say excuse for false 'problem'. OpenProg works with F88 OK.
I found the cause was burned to short PNP Q1. Don't know how it still worked with PIC16F877.
I afterwards added 100 Ohm in series to VPP output. This prevents burning Q1 even in case of dead shortage on user board.
With regards,
Yuri.
Good that you found the failure.
Some devices require lower voltage to enter into programming mode.