[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[avrdude-dev] [bug #30680] Checking for all 0xff not best way to decide
From: |
Joerg Wunsch |
Subject: |
[avrdude-dev] [bug #30680] Checking for all 0xff not best way to decide which pages to program |
Date: |
Sun, 08 Aug 2010 18:59:26 +0000 |
User-agent: |
Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.11) Gecko/20100729 Firefox/3.5.11 |
Update of bug #30680 (project avrdude):
Status: None => Duplicate
Open/Closed: Open => Closed
_______________________________________________________
Follow-up Comment #1:
I know that the current implementation leaves a bit to be
desired. Alas, there's currently nobody who has the time
and energy to implement the complete rework that would be
needed in order to avoid the underlying problem, that any
actual file information is lost by the time the programming
is started.
Anyway, you (respectively your bootloader) makes one
assumption which is fundamentally wrong, and which in turn
gives the implementation the right to skip any flash cell
that would be written to 0xffff: flash bits can _only_ be
written from 1 to 0, consequently, any attempt to write a
1 bit is essentially a nop. As it is a nop, it can be skipped.
(In order to return a flash cell back to 1 bits, it must be
erased.)
The problem here is apparently an implementation flaw in the
Arduino bootloader. It has already been discussed in
bug #30061, so I'm closing this bug here as a duplicate of
that one.
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?30680>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/