forum.hobbycomponents.com

HI
I HAVE GOT IT WORKING ITS SAYS ITS PROGRAMMED THE CHIP 16F631 BUT WHEN I TRY THE DEVICE IN CIRCUIT IT DOSEN,T WORK YET IT SAYS VERFIED PUT BACK THE CHIP I COPIED FROM WORKS FINE IAM NOT TO WELL UP ON THIS BUT LOOKING AT THE ROM ITS JUST GOT ZEROES & ON THE EEPROM BIT ITS JUST GOT A LOAD OF FFF BUT IT SAYS THE FILE IS 6K NOT TO SURE IF THIS IS RIGHT OR IF THE K150 CAN COPY THIS FILE FROM THE CHIP ANY HELP WOULD BE GREAT
CLIVE

Can you connect your original working device, read in the data by clicking the 'read' button and then click the 'fuses' button. A new window should open up . Could you tell me the what the CPD and Code protect fuses say.

Does the entire ROM window show zero's ?

WDT= ENA MCLRE= DIS CPD=DIS INEX SWITCH OVER=DIS OSC=INTRC_10 PWRTE=DIS CODE PRO=ENA BODEN=BOD OFF SBODEN OFF FAIL CLOCK MON=DISA
YES AL ROM DATA ARE ZEROES AND ALL EEPROM ARE F
Clive

I'm afraid it looks like whoever originally programmed the device blew the code protection fuse. This is a copy protection system that is built into PIC devices (and other microcontrollers) that is designed to stop you from being able to read the program back out of the device to copy it. This will be the reason why you are only able to read zero's out of its ROM.

Hi

i got my programmer today and have not been able to get it to work. I have looked through the posts but still am having issues.

I am trying to load a LED prog onto a 12F683

I have checked its in the correct place for programming

Im running Windows 7 64 bit

here are some images, hope they are useful















Hopefully you can help me to get this working

thx
jason

From your screenshots it looks like everything is installed correctly, you are running the correct version of the software, and the software is correctly seeing the K150 programmer. One thing you can try is increasing the program delay time for your device. There is a bit of information on how to do this at the bottom of the first post in this thread. this may not work in your case but it is worth a try as it is relatively easy to do and may fix the problem.

already tried increasing it by 10 each time, ended up at 140 and figured something wasn't right

Ok well it doesn't seem to be a setup problem. If you can, try a different USB cable. It does sound unlikely but cables are more likely to fail then the boards themselves and can fail in a way where the board still appears in device manager. Failing that, are you able to confirm that your PIC is working?

tried 3 different PIC of the same type and no change. usb also made no difference

still isnt working