Re: [avrdude-dev] program error?

[E. Weddington]

On 1 Apr 2003 at 23:11, Alex Shepherd wrote:

> Hi Guys,
> 
> > So I figured I'd give avrdude on win32 another try. Last week it
> > detected a verification error even though my avrstudio was able to
> > program and verify just fine. It's still showing the same error:
> > 
> > avrdude: verifying ...
> > avrdude: verification error, first mismatch at byte 0x0022
> >          0xb3 != 0xb0
> > avrdude: verification error; content mismatch
> > 
> > avrdude done.  Thank you.
> 
> I think its really good to have this programmer now included with
> WinAVR. Now you really do only need a single package to get going,
> good work guys!
> 
> However I too have been getting this verify error sometimes, not
> always but sometimes. It seems to have problems and that it is fine
> for quite some time. Before I started to type this email I retried it
> to capture the screen output but it was fine for a few runs and then
> failed about 3 times in a row and then was good for another 6 or so
> times. The addresses are not always in the same place, they seem to
> change. I'm pretty sure my hardware is ok as I can use PonyProg2000
> 2.05a for some time with no verify problems. See screen output below
> 
> I would like to be able to use this, but because its not 100% reliable
> I am still using PonyProg called from my make file with a *.e2s file.
> 
> My board is a Dontronics DT006, programmed via the parallel port and
> I'm running on Win2K.
> 
> Also I am running avrdude from within the JFE (Jen's File Editor) and
> when it captures the output window, the updating numbers cause it to
> scroll. Running from the CMD.EXE window is fine of course. Would it be
> possible to have an option to print a "." for each block across the
> screen a bit like FTP, rather than the numbers to reduce the
> scrolling?
> 
> Any suggestions?
> 

Group,

Could this perhaps be a marginal timing issue? The Windows code 
doesn't go through the ioctl stuff and may execute slightly faster. 
I'm not as knowledgeable about programming and any potential timing 
issues.

Eric