MCUmall EPROM BIOS Chip Burner Forum Active Users: / Visits Today:
Highest Active Users:
MCUmall EPROM BIOS Chip Burner Forum
Home | Profile | Register | Active Topics | Members | Search | FAQ
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 MCUmall Forums
 True USB Willem Programmer (GQ-2X,3X,4X & GQ-4x4)
 PIC12F1840 support

Note: You must be registered in order to post a reply.
To register, click here. Registration is FREE!

Screensize:
UserName:
Password:
Format Mode:
Format: BoldItalicizedUnderlineStrikethrough Align LeftCenteredAlign Right Horizontal Rule Insert HyperlinkInsert EmailInsert Image Insert CodeInsert QuoteInsert List Spell Checker
   
Message:

* HTML is OFF
* Forum Code is ON
Smilies
Smile [:)] Big Smile [:D] Cool [8D] Blush [:I]
Tongue [:P] Evil [):] Wink [;)] Clown [:o)]
Black Eye [B)] Eight Ball [8] Frown [:(] Shy [8)]
Shocked [:0] Angry [:(!] Dead [xx(] Sleepy [|)]
Kisses [:X] Approve [^] Disapprove [V] Question [?]

   Insert an Image File
Check here to include your profile signature.
    

T O P I C    R E V I E W
marquitos550b 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
8   L A T E S T    R E P L I E S    (Newest First)
anniel 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.
free30 Posted - 12/24/2017 : 16:40:48

Ruled out on both counts there then. ;)

Thanks again
anniel 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.
free30 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.
anniel 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.
free30 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

marquitos550b 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.
ZLM 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";

MCUmall EPROM BIOS Chip Burner Forum © Copyright 2003 - 2009 Mcumall Electronics Inc. Go To Top Of Page
Generated in 0.14 sec. Snitz Forums 2000