| T O P I C R E V I E W |
| F-bone |
Posted - 10/16/2015 : 00:20:30
Hi guys,
trying to read this pic my microchip:
h**p://ww1.microchip.com/downloads/en/DeviceDoc/41364E.pdf
This device is not in the latest software list, is there a compatible chip? Or can I add it manually somehow?
I have connected the ICSP header to the PCB were the PIC is soldered using the PCBs ICSP pins.
Any help is greatly appreciated.
BR,
George |
| 11 L A T E S T R E P L I E S (Newest First) |
| F-bone |
Posted - 10/20/2015 : 23:18:17
quote:
Originally posted by zzattack
If the PIC has memory read protection on you will always read only zeroes. This prevents unauthorized copying.
I think that must be the case! At least we managed to setup GQ-4X to support this chip properly :)
thank you all for your help, it is invaluable as always. |
| zzattack |
Posted - 10/20/2015 : 07:35:43
If the PIC has memory read protection on you will always read only zeroes. This prevents unauthorized copying. |
| F-bone |
Posted - 10/19/2015 : 23:10:47
quote:
Originally posted by ZLM
You need PIC16LF1934.dev file.
Try to add this line into devices.txt:
Name="PIC16LF1934",ID="294024",Class="PIC16FXXX",Category="MCU",MFG="Microchip",CodeSize="16384",EepromSize="256",Package="DIP28",PRG_MODE="0",BEGPRG_COMMAND="8",ENDPRG_COMMAND="",ERASECHIP_COMMAND="1F",BEGERASECHIP_COMMAND="8",PAGE_WRITE_SIZE="1",CFG_PAGE_WRITE_SIZE="1",CFGByteLabel="- DEBUG FCMEN IESO BOREN1 BOREN0 CPD CP MCLRE PWRTE WDTE FOSC2 FOSC1 FOSC0";
The PIC16LF1934.dev file should be included in the latest software.
Hi ZLM, thank you for the line, I can now see the device in the list but the read procedure is still giving zeros.
here is the photograph of the interface and also the screenshot of the software.
h**ps://drive.google.com/open?id=0B80HF5zjKWc1ZHhSZ1ppa2duMmc
h**ps://drive.google.com/open?id=0B80HF5zjKWc1ei1IMlc5ck55MFk
I really need to copy this chip to try and fix the instrument which cannot boot at the moment.
Any help is greatly appreciated.
BR,
George
EDIT:
Choosing "LF" designation instead of "F" (as is my chip here) the programmer passes the ID check this time. Still the read file is empty.
|
| ZLM |
Posted - 10/19/2015 : 22:36:25
You need PIC16LF1934.dev file.
Try to add this line into devices.txt:
Name="PIC16LF1934",ID="294024",Class="PIC16FXXX",Category="MCU",MFG="Microchip",CodeSize="16384",EepromSize="256",Package="DIP28",PRG_MODE="0",BEGPRG_COMMAND="8",ENDPRG_COMMAND="",ERASECHIP_COMMAND="1F",BEGERASECHIP_COMMAND="8",PAGE_WRITE_SIZE="1",CFG_PAGE_WRITE_SIZE="1",CFGByteLabel="- DEBUG FCMEN IESO BOREN1 BOREN0 CPD CP MCLRE PWRTE WDTE FOSC2 FOSC1 FOSC0";
The PIC16LF1934.dev file should be included in the latest software.
|
| F-bone |
Posted - 10/19/2015 : 11:13:57
quote:
Originally posted by zzattack
For simply reading PIC16F747, PIC16F74, PIC16F884 will do.
thank you zz, we ll know by tomorrow :)
EDIT: Unfortunately all I am getting is an empty binary file :(... There seems to be some activity on the device where the PIC is soldered on (LEDs etc) but the read procedure gives zeros.
EDIT2: I am using the ICSP header -=inside=- the GQ-4X programmer.
|
| zzattack |
Posted - 10/19/2015 : 06:32:01
For simply reading PIC16F747, PIC16F74, PIC16F884 will do. |
| F-bone |
Posted - 10/19/2015 : 05:14:24
quote:
Originally posted by zzattack
PIC16F is always 5v part, PIC16LF is always 3.3v part.
I don't see a DIP-20 package for that PIC16.
Yes, ID check will fail if you don't use exactly the same device, but if it's compatible (enough flash) it will program.
my bad its a 40pin device... F designation. So what would you suggest I use from the list... initially to read the device and then program a new one. |
| zzattack |
Posted - 10/19/2015 : 05:01:09
PIC16F is always 5v part, PIC16LF is always 3.3v part.
I don't see a DIP-20 package for that PIC16.
Yes, ID check will fail if you don't use exactly the same device, but if it's compatible (enough flash) it will program. |
| F-bone |
Posted - 10/19/2015 : 04:10:33
quote:
Originally posted by zzattack
The LF is simply the 3.3v version of that PIC. All 28-pin PIC16F's have the ICSP pins in the same location, so any of them should work.
hi zz,
this is not "LF" but "F" family and both F and LF have the same behaviour, the 1934 version is not shown in the list altough the .dev file exists.
also my version is 20pin at 9v if I am correct. Would any other similar device be ok even if the ID check fails?
BR,
George |
| zzattack |
Posted - 10/19/2015 : 03:11:00
The LF is simply the 3.3v version of that PIC. All 28-pin PIC16F's have the ICSP pins in the same location, so any of them should work. |
| F-bone |
Posted - 10/16/2015 : 01:04:52
The weird thing is that there is PIC16F1934.dev and PIC16LF1934.dev in the Devices directory????
EDIT, guys I really need your support in this. Please provide your insight on this matter. |
|
|
