Re: [avrdude-dev] Re: program error?

[Alex Shepherd]

> Could be.  What part in specific are you trying to program, Alex?
> Just for sanity's sake, lets first lets double check the various time
> related parameters associated with the part (chip_erase_delay and
> min/max_write_delay for the flash memory).

I'm using a Mega8

> For now, please double check the values of the chip_erase_delay and
> min/max_write_delay listed in the avrdude.conf config file for the
> part you are using.  Or let me know what part it is and I'll check the
> datasheet.  You can adjust those values without in the config file and
> they will affect avrdude without having to recompile, which is the
> easiest thing to do.

Yeah I wondered if this was the easy option. I can give it a try.

> Eric mentioned the timing differences between using ioctl() on Unix vs
> in/out instructions on Windows.  The in/out instructions are
> undoubtedly faster.  It may be possible that these signals are
> changing slightly too fast - not sure about that.  Eric - just
> wondering if you might consider placing a short sleep or something
> within a few of the parallel port manipulation functions for the
> Windows port to slow them down a little at the right places, maybe
> make this enabled with a #define so that they can be easily compiled
> out?

Whatever you guys think is best. Adding a few environment variables would
just allow me to experiement with the values - thats all.

 Thanks for the effort to get this tool onto Windows!

Alex