WinPicProg Forums

[Jeff Hall]

I am trying to ICSP a PIC16F877 on COM1 ($378). The BIOS is configured to set the parallel port to EPP. No matter what I try, WinPicProg refuses to find the port so I can program my PIC16F877. Once in a blue moon, it does find the port at $378, and then everything works. Here are the settings I use:

Vdd: D3 (Off)
Vpp: D1 (On)
Vpp40: D3 (On)
Output: STB (Invert Low)
Clock: D0 (Low)
Input: STB (Low)
Port: $378

Both delays are set to 14.

I have no reason to suspect the programming cable is bad, as it’s worked before.

Here’s the steps I do:

1. Connect the Parallel cable to the board.
2. Apply power to the board
3. Start WinPicProg 1.95c

At this point, WinPicProg says the port address is $000.

4. Load the HEX file to be programmed
5. Open hardware settings and make necessary adjustments

Now, hardware settings has to always be reset to what I want. Some of the values stay correct after exiting and re-loading WinPicProg, but Input always defaults to BSY and I have to change it back to STB. Sometimes the port is set to $3BC and I have to change that back. Vpp and Vpp40 usually have to be turned back on as well.

If I try to scan for the port, it reports back “None”.

I then Write to the PIC, and after about 71 seconds, it reports that 2156 words were written. Clicking verify returns a Verify program error. Reading the PIC back returns all zeros (the chip was blank to begin with). I don't think it actually read the chip.

I would really appreciate any light you could shed on this problem.

Thanks!
_________________
Regards,
-Jeff

[Nigel Goodwin]

Once you've got it working, I suggest you disable the auto-port detection (menu option), this will prevent it trying to find the programmer again.

I can only suggest though that you manually select the correct port, and use the manual toggle buttons to switch the output lines while you check them with a meter.

[fleawit]

I see he calls out STB for both output and input. Isn't that illegal?
If they are set the same would not WinPicProg be looking at its own data mixed with the PIC output upon readback/verify ?

[fleawit]

oops- forgot the other part-

As I understand how the world turns, the port is found by checking the data input for changes that follow data output changes. If both input and output are set to same parallel port pin then at best WInPiCpROg would find the rpogrammer on the first port it tried?

[PriSon]

My programer worked well about one year.
Then the error 0x000 happend. I recognized that the solders were bad. I solder all pins again. Then the programmer worked. I load a simple code for LED blinking (i tried to erase and write-->everything well). I tought everythings all right, so i am going to connect a textool in to the normal 40-pin socket with some wire (also putting the wire in the pins od the normal socket). The reason was that I had a idea putting my programmer in a plastic shaped box.
After the connection of the textool the programmer did not work.
I am sure that the hardwear is OK. I alreadey removed the textool wire connections and it is still not working!!!

I removed the DLPortIO and istalled it againt. I removed winpicprog from my PC and install it again.

Now i have the problem to find the port.
Winpicprog doesn't find the port.

Also:
1. Connect the Parallel cable to the board.
2. Apply power to the board
3. Start WinPicProg 1.95c

At this point, WinPicProg says the port address is $000.

When I disable the auto-port detection WinPicProg says the port address is None.

Manualy the port is every time when I run winpicprog changing.

I have note changed my bios settings at all.

Thanx for help.

[PriSon]

I found the problem with the port finding. One of the LED diod had a bad solder.

But the programmer is still not working. I checked everything possible!!

The error 0x000 will kill my nerves. What could be wrong on the hardwear? Maybe some typical mistakes?!

I am using pic16f877a.

Please help!