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 http://www.mikrocontroller.net/topic/95432#823132) If you like I can implement those and send you a patch. brgds Thomas _______________________________________________________ Reply to this item at: <http://savannah.nongnu.org/bugs/?22883> _______________________________________________ Message sent via/by Savannah http://savannah.nongnu.org/ _______________________________________________ avrdude-dev mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/avrdude-dev
