avrdude-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [avrdude-dev] Release soon?


From: Brian Dean
Subject: Re: [avrdude-dev] Release soon?
Date: Tue, 4 Mar 2003 23:42:12 -0500
User-agent: Mutt/1.4i

On Tue, Mar 04, 2003 at 09:44:14PM -0500, Brian Dean wrote:

> On Mon, Mar 03, 2003 at 11:55:51PM -0800, Theodore A. Roth wrote:
> 
> > Avrdude can erase the device (an 8515), but can not program
> > it. Attached is the output of: 
> 
> This turned out to be something unrelated.  Turns out, the algorithm
> for the stk500 never did work for any non-paged device, i.e.,
> non-ATmega part.
> 
> The AVR061 protocol seems a bit unclear on this, but it seemed to
> imply that the "program page" command works for non-paged parts.
> Thus, as an optimization, if the selected programmer supports this
> command, 'avr_write()' would always use that, instead of programming
> each individual byte.
> 
> Well ... it looks like this is not the case.  Since the 8515 is does
> not have a paged memory, it failed.

Ok - that was completely wrong.  Turns out that this is supported just
fine, and the real problem was that I was just not waiting long enough
for a response from the STK500 after issuing the "program page"
command.  Non-paged (non-ATmega) parts seem to program slower than
paged parts, and while I never ran into this while testing with my
ATmega128, programming a whole page size full on the 8515 was taking
longer than the 0.5 second timeout I was giving for the STK500 to
acknowledge a command.

Anyway, I dropped the page size from 256 to 128 for non-paged parts,
and increased the timeout to 5 seconds.

All's well again.

Ted, if you could please try your 1.14 firmware again after updating,
that'd be great.

-Brian




reply via email to

[Prev in Thread] Current Thread [Next in Thread]