gnupic: Thread: P16PRO40 Programmer

I am currently having success programming with the above programmer at uni, 
but under windows. Does anyone know of any programming software that can use 
this programmer under Linux?

This link shows the schematic:

www.lpilsley.co.uk/pdf/p16pro40.pdf

I was hoping to use picprg, but as far as I can tell it wouldn't be able to 
deal with the Vpp40 line...

Martyn

On Tue, Mar 18, 2003 at 08:05:25AM +0000, Martyn Welch wrote:
> I am currently having success programming with the above programmer at uni, 
> but under windows. Does anyone know of any programming software that can use 
> this programmer under Linux?
> 
> This link shows the schematic:
> 
> www.lpilsley.co.uk/pdf/p16pro40.pdf
> 
> I was hoping to use picprg, but as far as I can tell it wouldn't be able to 
> deal with the Vpp40 line...

You are correct. That programmer attempts to save socket space through 
software.

The best way is setup a jumper/switch for the line so that you can either
connect it to the parallel port line, or manually set it high or low.

picprg2.3d should handle the rest of the circuit just fine.

BAJ

On Tue, Mar 18, 2003 at 08:05:25AM +0000, Martyn Welch wrote:
> I am currently having success programming with the above programmer at uni, 
> but under windows. Does anyone know of any programming software that can use 
> this programmer under Linux?
> 
> This link shows the schematic:
> 
> www.lpilsley.co.uk/pdf/p16pro40.pdf
> 
> I was hoping to use picprg, but as far as I can tell it wouldn't be able to 
> deal with the Vpp40 line...

I use PICPRG just fine with a similar programmer(with 3 Vpp lines)
I just reconfigure the software to toggle whichever Vpp line I need 
to use for a particular chip in the configuration screen.

I may have also changed the code so that unused bits in the parallel port
are set correctly, depending on if you're using an inverting or
non-inverting buffer, to make sure the other Vpp lines are always off when
not in use. (But I don't have the code with me so I can't tell you exactly
what it was, if I made any change it was pretty simple in the lowlvl.c file)

-Steve Wormley