Re: [avrdude-dev] help - win2k:ppi (dt006) issues with avrdude, uisp works fine

[Davin Gibb]

inline;

> On Wednesday 21 January 2004 10:58, Jan-Hinnerk Reichert wrote:
> > On Wednesday 21 January 2004 02:51, Davin Gibb wrote:
> > > Hi guys, I'm hoping someone will be able to shed some light on
> > > this one!
> > >
> > > I have a dt006 parallel port programmer. I'm using Win2K. All my
> > > software has come from AVR GCC at avrfreaks.net (so I'm using the
> > > cygwin compiled avrdude-4.2.0).
> > >
> > > My parallel port under windows is called 'lpt1', however, I'm on
> > > a laptop, so the base address is 0x3bc.
> > >
> > > uisp works a treat, avrdude (and ponyprog) are no good, below is
> > > the output (first success with uisp, then fail with avrdude, yes
> > > I have getio.sys loaded).
> > >
> > > You guys have any clue as to why they are different? Any help
> > > greatly appreciated.
> >
> > Not really ;-)
> >
> > IMHO lpt3 should be right.
> >
> > Can you add some "fprintf"s in ppiwin.c and recompile?
> >
> > Have you double checked the pin-definitions of dt006?
> >
> > Try avrdude "-v -v -v -v" and see if anything is received (or if it
> > is just 0xff over and over again).
> 
> I've just read something in the (german-speaking) newsgroup 
> "de.sci.electronics" which might be relevant.
> 
> Aparently, the OS (was Win98 there) can fake an I/O-access. This would 
> happen if the port is used by another program (e.g. a printer 
> spooler).

Is there a way to directly tell avrdude an I/O address? Instead of using 
the port handler names? I'm sure this is why uisp works and avrdude 
doesn't (thats what the gut is saying anyway).

> 
> I also took a quick look at uisp-sources, but I couldn't see any 
> obvious differences. Perhaps Ted can tell us more, as he is familiar 
> with uisp ;-)
> 
> /Jan-Hinnerk
> 
>