[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[avrdude-dev] [bug #22883] Chip Erase performed even with no-write flag
[avrdude-dev] [bug #22883] Chip Erase performed even with no-write flag (-n)
Wed, 09 Apr 2008 20:44:27 +0000
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:188.8.131.52) Gecko/20080311 Firefox/184.108.40.206
Follow-up Comment #2, bug #22883 (project avrdude):
I am not sure.
If I use "-n" I would expect that the MCU is absolutly in the same state
after avrdude as before.
So it might be better to leave safemode enabled, so when Fusebytes magically
change just by reading from the MCU (is this possible?), it might be more
consistent with the user intention to write the old values back, even if it
does mean that something is written back.
But something else: I just noticed that -Y xxxx will also write to the eeprom
regardless of "-n".
That one should be disabled as well.
And while we are at it: It might be a good idea to print a few messages if
writing has been disabled by "-n" (see
If you like I can implement those and send you a patch.
Reply to this item at:
Message sent via/by Savannah