you can try to change the 7404 chip.
sometimes he is destroyed because of over voltage at the LPT port.
|
you can try to change the 7404 chip.
sometimes he is destroyed because of over voltage at the LPT port.
|
problem
Hi I'm having the same problem, I get an error message saying "Code error at..."... I tried changing my adapter and cable... But nothing worked..I'm getting another error message "Target device does not match the selected device".. I'm using pic16f84a... But if I select it frm the list I get this erro message.. If I select pic16f84 I'm not getting any kind of problems(but still I'm not able 2 program my uC)..
Plz I need some help, its been months since I've bought this programmer, but still I'm unable to use it...
|
How many of the troubleshooting steps listed at MeLabs have you tried?Originally Posted by elankart
|
nearly everything..
|
This is the parallel type EPIC programmer right?
Does it start to program and then quit for some silly reason? Windows XP may periodically access printer ports and interrupt the EPIC programming process. This can be stopped with a registry entry. Go to MeLabs for the registry fix. I had a similar problem with my Warp13a, only it was caused by the motherboard's periodic temperature sensor/fan sensor reading about every 5 seconds or so. Made me pull hair out until I disabled it in BIOS.
Power supply - >13VAC or >16VDC?
Parallel port set to "standard" or "ECP" (try both) in the bios setup
Use the Windows Task Manager to stop the process "spoolsv.exe".
|
Sorry misread previous suggestion about the LPT patch.
BTW, i don't think it's a good idea to kill the Spoolsv.exe process...unless it sucks 99% of your system ressource... if so.. it's probably a virus, a bad network setup (if any), or bad printer(device) driver anyways.
EDIT: are you programming your PIC in the ZIF socket or using ICSP?
Last edited by mister_e; - 24th April 2007 at 02:44.
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
|
no ZIF... ICSP... I mounted my uC in the socket provided...
|
Like you said, you have 2 separate problems here. The first seems to be a harware problem; let look into that later.
The second one, I suspect is this; are you using a statement that defines the PIC within your code (as in @ Device Pic16F84A .... ) with Microcode Studio? Chances are you have defined a different PIC in the MCS option of 'Target Processor'. I mean, your code might be specifying a 16F84A, but MCS is looking for a 16F84 (or the other way around).
Give us a feedback on the above, and then we'll move on to the hardware issue.
Regards,
Anand
Members who have read this thread : 0You do not have permission to view the list of names.
Posting Permissions
Bookmarks