Re: [avrdude-dev] PCI parallel ports with Windows

[David Belvedere]

Hi guys,

I have also got it working using this method.  I just changed the 
DEVICE_LPT3 base address to the pci parallel port base address, and then 
compiled as usual, which is not really a workable patch however conformation 
that it works.

The PCI card was also a multi IO card.

Thanks David

----- Original Message ----- 
From: "René Liebscher" <address@hidden>
To: <address@hidden>
Sent: Saturday, July 05, 2008 4:50 AM
Subject: [avrdude-dev] PCI parallel ports with Windows


> Hello,
>
> I know there were already a short dicussion about this topic in 2003 (*Re: 
> [*avrdude*-dev] Blank skipping, multi-byte writes, notes *on* parallel 
> ports 
> <http://lists.gnu.org/archive/html/avrdude-dev/2003-04/msg00077.html>*, 
> http://lists.gnu.org/archive/html/avrdude-dev/2003-04/msg00078.html), but 
> may be it helps to get it done now by a description how to get the 
> necessary address information for the ports.
>
> First you need to know the address of the port on your PCI card.
> I used for this the SIV (System Information Viewer, 
> http://www.rh-software.com/)
> The necessary sequence is shown in the following images.
>
> http://robot.informatik.uni-leipzig.de/~liebschr/avrdude/SIV_1_.PNG
> http://robot.informatik.uni-leipzig.de/~liebschr/avrdude/SIV_2_.PNG
> http://robot.informatik.uni-leipzig.de/~liebschr/avrdude/SIV_3_.PNG
>
> At the third screen you have the address you need.
>
> After this, I tested it changing the entries from file ppiwin.c ("lpt3" => 
> "pci" and 0x3BC => 0xBC00).
> (Actually I just used a hex editor on the executable, as I don't have the 
> sources and compiler installed ;-)
>
> As you can see on the image 
> (http://robot.informatik.uni-leipzig.de/~liebschr/avrdude/result.PNG) this 
> works perfect.
>
> If some other people could try this procedure, and find if it works for 
> them too, then it could be included in a next release of avrdude?
>
> I have no complete patch for it, but using "strtoul" as already proposed 
> would be the way to parse something like "pci_0xBC00" or similar.
>
>
> Kind regards
>
> Rene Liebscher