RE: [avrdude-dev] program error?

[Sander Pool]

> -----Original Message-----
> From: address@hidden
> [mailto:address@hidden
> Behalf Of Brian Dean
>
> On Sun, Mar 23, 2003 at 04:26:41PM -0800, Sander Pool wrote:
>
> > Yes, that is correct. If avrdude doesn't lock up it will work OK.
>
> avrdude is locking up?  Hmmm ... it'd sure be nice to run that under a
> debugger and break into it and see what it's up to when it locks up.

I haven't tried to build avrdude on my system yet. If I'm the only one with
this problem I guess it's no big deal.

>
> > > If so, then avrdude is working correctly - since after programming it
> > > reads out the entirety of the flash, and compares the results with
> > > what it just uploaded and they matched.
> >
> > Even without the -V flag?
>
> Yes.  The -V flag actually disables the verify check.

Ah yes, I misread the usage message.

>
> > So should it maybe be the default behavior then with an option
> to turn it
> > off?
>
> Maybe.  Several folks have been bitten by this.  I don't really have
> much experience with other programmers - do they always automatically
> perform a chip erase before programming?

The STK500 plugin has an option to erase before programming. It's set by
default, as is verifying.


>
> My personal preference is to not erase the chip by default.  I don't
> tend to like it when programs do stuff like that without me explicitly
> asking for it.

So why is 'verify' on by default then?

I don't like it when programs do bad things without asking for it. I also
don't like it when programs don't do the obvious correct thing which in this
case erasing before programming seems to be.

        Sander