avrdude-dev
[Top][All Lists]
Advanced

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

[avrdude-dev] [bug #52963] -U option with flash memory doesn't perform c


From: anonymous
Subject: [avrdude-dev] [bug #52963] -U option with flash memory doesn't perform chip erase with arduino programmer
Date: Tue, 23 Jan 2018 18:13:19 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0 Iceweasel/38.8.0

URL:
  <http://savannah.nongnu.org/bugs/?52963>

                 Summary: -U option with flash memory doesn't perform chip
erase with arduino programmer
                 Project: AVR Downloader/UploaDEr
            Submitted by: None
            Submitted on: Tue 23 Jan 2018 11:13:18 PM UTC
                Category: None
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name: Britton Kerin
        Originator Email: address@hidden
             Open/Closed: Open
                 Release: 6.3
         Discussion Lock: Any
     Programmer hardware: arduino
             Device type: 

    _______________________________________________________

Details:


It can't because that would blow away the bootlaoder.
The -D option description currently says this:

  -D      Disable auto erase for flash.  When the -U option with flash
  memory is specified, avrdude will perform a chip erase before
  starting any of the programming operations, since it generally is a
  mistake to program the flash without performing an erase first.  This
  option disables that.  Auto erase is not used for ATxmega devices as
  these devices can use page erase before writing each page so no
  explicit chip erase is required.  Note however that any page not
  affected by the current operation will retain its previous contents.

If exceptions for ATxmega deserve a mention that the arduino programmer
exception certainly does too.  It can matter because e.g. EEPROM doesn't end
up
getting cleared like documentation in chip datasheet says it does for chip
erase (assuming EESAVE not programmed).





    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?52963>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/




reply via email to

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