| Author |
 Topic  |
|
|
marquitos550b
Argentina
14 Posts |
 Posted - 10/26/2015 : 08:47:22
|
Hi, I need to program this chip but I don't know how to add it to the device list.
Please any advice.
This is the data sheet.
h**p://ww1.microchip.com/downloads/en/DeviceDoc/41441B.pdf
Thank you.
Regards.
Marcos |
|
| Reply #1
ZLM
2945 Posts |
Posted - 10/27/2015 : 13:16:50
|
Try to add following line into devices.txt file and make sure the PIC12F1840.dev file in the devices directory.
Name="PIC12F1840",ID="2927A0",Class="PIC16FXXX",Category="MCU",VPP="9V",WVPP="9V",MFG="Microchip",CFGAddress(Hex)="8007",CodeSize="4096",EepromSize="256",Package="DIP20",BEGPRG_COMMAND="8",ENDPRG_COMMAND="0A",BEGERASECHIP_COMMAND="9",ERASECHIP_COMMAND="",EEPROMHexFileAddress(Hex)="1E000",CFGHexFileAddress(Hex)="1000E",UserIDHexFileAddress(Hex)="10000";
|
 |
|
| Reply #2
marquitos550b
Argentina
14 Posts |
Posted - 11/07/2015 : 07:44:06
|
Hi ZLM, sorry for my delay in aswering I have been very busy at job.
This configuration works well:
Name="PIC12F1840I/P",ID="2927A0",Class="PIC16FXXX",Category="MCU",VPP="9V",WVPP="9V",MFG="Microchip",CFGAddress(Hex)="8007",CodeSize="4096",EepromSize="256",Package="DIP8",BEGPRG_COMMAND="8",ENDPRG_COMMAND="0A",BEGERASECHIP_COMMAND="9",ERASECHIP_COMMAND="",EEPROMHexFileAddress(Hex)="1E000",CFGHexFileAddress(Hex)="1000E",UserIDHexFileAddress(Hex)="10000";
Thanks for caring.
Best regards
Marcos. |
|
|
| Reply #3
free30
9 Posts |
Posted - 12/24/2017 : 05:59:42
|
Hello, thanks in advance for any help. I'm a bit naive with this stuff.
I'm using a GX-4X to try a copy a PIC12F1840.
The configuration above in 'marquitos550b' post 2 gives an error opening 'PIC12F1840I/P.dev' and then does not recognize the ID.
So I use this line in the 'devices.txt' instead and it sees the right ID.
Name="PIC12F1840",ID="2927A0",Class="PIC16FXXX",Category="MCU",VPP="9V",WVPP="9V",MFG="Microchip",CFGAddress(Hex)="8007",CodeSize="4096",EepromSize="256",Package="DIP8",BEGPRG_COMMAND="8",ENDPRG_COMMAND="0A",BEGERASECHIP_COMMAND="9",ERASECHIP_COMMAND="",EEPROMHexFileAddress(Hex)="1E000",CFGHexFileAddress(Hex)="1000E",UserIDHexFileAddress(Hex)="10000";
Now when I read the chip its gets the ID right and seems to read the 'data' but only give '0000...' for the buffer where I'd expect to see the program on the chip.
Is there something I'm missing?
Can the PIC12F1840 be locked and then'0000 0000....' is the chip locked rather than one I cant read?
Is there another PIC12F1840.dev I could try?
Should I upgrade to the GX-4X4?
Many thanks for any advise
|
|
|
| Reply #4
anniel
2572 Posts |
Posted - 12/24/2017 : 06:40:04
|
quote:
Originally posted by free30
Hello, thanks in advance for any help. I'm a bit naive with this stuff.
I'm using a GX-4X to try a copy a PIC12F1840.
The configuration above in 'marquitos550b' post 2 gives an error opening 'PIC12F1840I/P.dev' and then does not recognize the ID.
So I use this line in the 'devices.txt' instead and it sees the right ID.
Name="PIC12F1840",ID="2927A0",Class="PIC16FXXX",Category="MCU",VPP="9V",WVPP="9V",MFG="Microchip",CFGAddress(Hex)="8007",CodeSize="4096",EepromSize="256",Package="DIP8",BEGPRG_COMMAND="8",ENDPRG_COMMAND="0A",BEGERASECHIP_COMMAND="9",ERASECHIP_COMMAND="",EEPROMHexFileAddress(Hex)="1E000",CFGHexFileAddress(Hex)="1000E",UserIDHexFileAddress(Hex)="10000";
Now when I read the chip its gets the ID right and seems to read the 'data' but only give '0000...' for the buffer where I'd expect to see the program on the chip.
Is there something I'm missing?
Can the PIC12F1840 be locked and then'0000 0000....' is the chip locked rather than one I cant read?
Is there another PIC12F1840.dev I could try?
Should I upgrade to the GX-4X4?
Many thanks for any advise
Taken from the datasheet:
4.2.1 PROGRAM MEMORY PROTECTION
The entire program memory space is protected from
external reads and writes by the CP bit in Configuration
Word 1. When CP = 0, external reads and writes of
program memory are inhibited and a read will return all
‘0’s. The CPU can continue to read program memory,
regardless of the protection bit settings. Writing the
program memory is dependent upon the write
protection setting. See Section 4.3 “Write
Protection” for more information. |
|
|
| Reply #5
free30
9 Posts |
Posted - 12/24/2017 : 08:05:59
|
Thank you so much for your support.
So I'm guessing that I cant remove the protection to allow me to read the chip?
Thanks again, there was just too many variable for an inexperienced person like myself.
|
|
|
| Reply #6
anniel
2572 Posts |
Posted - 12/24/2017 : 14:50:50
|
quote:
Originally posted by free30
Thank you so much for your support.
So I'm guessing that I cant remove the protection to allow me to read the chip?
Thanks again, there was just too many variable for an inexperienced person like myself.
There is more complicated and costly ways to reverse engineer such chips. |
|
|
| Reply #7
free30
9 Posts |
Posted - 12/24/2017 : 16:40:48
|
Ruled out on both counts there then. ;)
Thanks again |
Edited by - free30 on 12/24/2017 16:41:26 |
|
|
| Reply #8
anniel
2572 Posts |
Posted - 12/25/2017 : 13:36:29
|
quote:
Originally posted by free30
Ruled out on both counts there then. ;)
Thanks again
Or you could try to contact the original programmer. |
|
|
| |
Topic |
|
|
|
PIC12F1840 support
