EPIC, Code programming error at 0000

[shorton]

Hi guys:

I've used the EPIC since 1995. I still have that one but use a slightly newer one these days. I am currently programming 16F628A DIPs (or trying to) via the EPIC 8-40 pin ZIF adapter. My EPIC has worked fine with no problems until today. I went to make a change on an existing program and I couldn't get it to program.

To make a long story shorter, apparently there's an issue with LPT1 on my main PC. I did recently install a HP officejet. Maybe that's what hosed it, can't tell.

So, needing to get these chips programmed, and of course as luck would have it, I was unable to find my meLabs software disc. Lacking that, I downloaded the meProg "beta" and installed it on my XP Pro Dell laptop.

Could not get it to program a chip either. Unlike the desktop, it was reading the chips, but would not program them. Gave the "...error at 0000".

I accidentally discovered if I kept trying, eventually it would program. Sometimes it takes 20-30 tries.

I followed *every* troubleshooting step on Melabs page. I also checked some of what was mentioned in other threads on the same subject here. No luck. My laptop has 3 protocol settings for the LPT port, tried all 3. I checked the 2 resistors under Q1, they are 1k's on my newer board (circa 99), they are 10k on the old board. I've checked both Reg's voltages, tuned Reg2 to 13.5 exactly. No luck. I tried fresh batteries instead and jumpered to use them, no luck. I normally use a surplus nice laptop external 18VDC PS, so to be sure it wasn't the culprit, I tried a differenty one, still no luck.

The laptop is pretty clean, has no print drivers, I have spoolsvc killed just to be thorough.

My ZIF board isn't one that calls for an modification as far as I could tell (mine says 04221 JMS no other visible part #), and the other mods indicate they are for other chips.

I've got 2 problems, one, how to figure out why meProg won't talk on my desktop's LPT port, but more related:

How do I get the EPIC to program reliably again?

I finally got my batch of chips done, but I need it to program every time, not every 35th.

Figures it would happen on a holiday weekend, when I need to get it done and Melabs is closed

Thanks for any help!
Scott

[Pic_User]

Hi Scott,
Sorry to hear about the EPIC problem.
Look at this tread, might help?
http://www.picbasic.co.uk/forum/showthread.php?t=1189
-Adam-

[mister_e]

make sure you also have the Parallel port polling patch for XP.
http://www.melabs.com/support/patches.htm#xppolling

error @0000 is often caused by a too low MCLR/Vpp voltage while programming, it should be close to 13V. I would suggest you to measure it, and make sure you have 0.1uF capacitor installed as close as possible of your PIC Vcc line.

You could also try to do it using the ICSP connector



Page link
http://www.melabs.com/support/icsp.htm

[Darrel Taylor]

Just a guess, but maybe installing that printer driver re-enabled "Printer Polling".

You might try the registry entries shown at the bottom of this page again.

Stop Windows XP from polling printer port
http://www.melabs.com/support/patches.htm

I also had to change the 7407 once. But I wasn't able to read the PIC, so that might not be it.

DOH! - beat me again Steve

[mister_e]

Nice to hear about the 7407. Could be handy for all EPIC user.

At least we are two with the same suggestion

[shorton]

Hi guys. Thanks for the time to give suggestions but as I mentioned in the original post I tried every debug step on melabs page. Including:

- On both PC's I applied the polling registry edit. It had no visible effect.

- As for the 7407 I wouldn't think it would work sporatically. But I changed it to be sure, did not help.

re: the other thread, no suggestions there helped.

error @0000 is often caused by a too low MCLR/Vpp voltage while programming, it should be close to 13V. I would suggest you to measure it,

See original post. Not only did I measure it, I adjusted Reg2 to be exactly 13.5.

0.1uF capacitor installed as close as possible of your PIC Vcc line

You mean add one to the EPIC? I'm not doing ICP, just using the EPIC and ZIF adapter.

Just to avoid confusion, let's ignore the desktop issue. I'll deal with that later. Sticking to the laptop, all above applies, all debug suggestions tried. Using the laptop I can reliably read the 16F628A, but it will only program it sporatically. I don't change anything in meProg, I just click on burn, then OK on the ...0000 error, over and over. Eventually it will burn one.

[mister_e]

mmm, could be, but can you confirm you already program a 16F628A with the same programmer before?

Assuming there's no faulty/dirty/loose connector pin (DIP & Printer ones), your printer cable is OK and you don't have any switch-box in between... it has to work.

Apart of a cold joint, those on-Board Transistors is my last bet. Even if they test good with a multimeter, they could be lazy and/or leaky... Lazy electrolytic? mmmpfff

Bah why not change all parts on, as there only a few?

Sure a weird coincidence with the HP printer... In the HP Printer Properties, is the printer assign to a DOT port? let's say DOT4_001? Is the Enable printer pooling check box checked?

<IMG SRC="http://www.picbasic.co.uk/forum/attachment.php?attachmentid=1683&stc=1&d=118028323 9">

EDIT: did you also try the EPIC.INI suggested modification?
http://www.melabs.com/support/epicini.htm

Now i'm out of idea