MCUmall EPROM BIOS Chip Burner Forum
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
 PIC Programmer
 PIC Programmer won't work
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

mparodi

5 Posts

Posted - 12/11/2011 :  14:22:26  Show Profile  Reply with Quote
Hello,

A friend and me bought two pic programmers (h**p://www.ebay.com/itm/Enhance-JDM-PIC-programmer-V2-Microchip-40pin-lowest-cost-Great-deal-/110759718689?pt=LH_DefaultDomain_0&hash=item19c9cb2f21) few weeks ago.

I tried to burn a 16F648A PIC and I believe the first time it worked but now it's impossible to burn it again.

I'm using picprog in Linux:

quote:

# picprog --burn --slow --input myFile.hex --pic /dev/ttyS0



It returns:

quote:

Trying realtime priority 1
Using 10 Ás delays.
/dev/ttyS0: id 0x1105: detected pic16f648a version 0x05
Device pic16f648a, program memory: 4096, data memory: 128.
Burning program memory,/dev/ttyS0:0000: programmed=2804, read=0185:unable to verify pic while programming.
Is code protection enabled, or does the chip need to be
erased completely before programming?
Use --erase option to disable code protection.




So I added --erase:

quote:

# picprog --erase --burn --slow --input myFile.hex --pic /dev/ttyS0



Here is the output:

quote:

Trying realtime priority 1
Using 10 Ás delays.
/dev/ttyS0: id 0x1105: detected pic16f648a version 0x05
Device pic16f648a, program memory: 4096, data memory: 128.
Erased and removed code protection.
Burning program memory,/dev/ttyS0:0000: programmed=2804, read=0185:unable to verify pic while programming.
Is code protection enabled, or does the chip need to be
erased completely before programming?
Use --erase option to disable code protection.




The output is the same!

I ignored the error and I tried to use the PIC anyway without success. It seems it still have the old application I burned.

There's one more thing, if I read the PIC and I generate an .hex file from it using:

quote:

# picprog --slow --pic /dev/ttyS0 --output current.hex



I get:

quote:

:080000000185018616830185018612831405100681
:08000800201A10051406201A280630FA00003EFFB8
:080010001D03280F0008008C30F8200F28170B8CD0
:080018002814000830FA201330FA201330FA201385
:0800200030FA2013000828233FFF3FFF3FFF3FFF30
:080028003FFF3FFF3FFF3FFF3FFF3FFF3FFF3FFFE0
:080030003FFF3FFF3FFF3FFF3FFF3FFF3FFF3FFFD8
:080038003FFF3FFF3FFF3FFF3FFF3FFF3FFF3FFFD0
:080040003FFF3FFF3FFF3FFF3FFF3FFF3FFF3FFFC8
:080048003FFF3FFF3FFF3FFF3FFF3FFF3FFF3FFFC0
:080050003FFF3FFF3FFF3FFF3FFF3FFF3FFF3FFFB8
:080058003FFF3FFF3FFF3FFF3FFF3FFF3FFF3FFFB0
...same again and again...



Which doesn't make any sense.

I asked my friend and he's having the same problem with his 16F628A after about 10 burns! What's going on!?

It seems both programmers are broken in the same way. Any way to check what is broken? I only used it once, I can't believe that!

Matt

Edited by - mparodi on 12/11/2011 14:23:51
Reply #1

mparodi

5 Posts

Posted - 12/11/2011 :  21:25:08  Show Profile  Reply with Quote
By the way, I have realized that MAYBE it's happening since the last time I tried to burn something using LVP off. I'm not sure but maybe the problem is that the PIC has to be erasable using HVP now but this programmer only works with LVP.

Can anyone confirm that? What can I do in order to erase it?

Thanks you in advance!

Matt
Go to Top of Page
Reply #2

ZLM

2926 Posts

Posted - 12/12/2011 :  14:09:46  Show Profile  Reply with Quote
This is HVP programmer. All chips need to be erased before write any new data.

Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
MCUmall EPROM BIOS Chip Burner Forum © Copyright 2003 - 2009 Mcumall Electronics Inc. Go To Top Of Page
Generated in 0.17 sec. Snitz Forums 2000