bugAVR Downloader/UploaDEr - Bugs: bug #18581, safemode destroys fuse bits

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #18581: safemode destroys fuse bits

Submitted by:  None
Submitted on:  Sat 23 Dec 2006 06:54:00 PM UTC  
 
Category: NoneSeverity: 3 - Normal
Priority: 5 - NormalItem Group: None
Status: FixedPrivacy: Public
Assigned to: Thomas Fischl <fischl>Originator Name: stefan noll
Originator Email: -unavailable-Open/Closed: Closed
Release: NoneProgrammer hardware: 
Device type: 

Fri 02 Feb 2007 04:32:08 PM UTC, comment #3:

AVRDUDE stops now if communication between USBasp and target isn't possible.

Thomas Fischl <fischl>
Project MemberIn charge of this item.
Sun 07 Jan 2007 09:59:57 PM UTC, comment #2:

After some private email exchange with Stefan (who unfortunately
opened the bug tracker anonymously so he cannot add a comment
himself), this appears to be an issue with avrdude talking to
USBasp before some part of the communication has been settled
correctly. Thus, the initial readout of the AVR is just junk
(it reads a wrong signature, and consistently reads all fuses
as 0).

It needs to be clarified how it can be ensured that avrdude
won't start prematurely.

Joerg Wunsch <joerg_wunsch>
Project Administrator
Sat 23 Dec 2006 10:09:31 PM UTC, comment #1:

Well, the purpose of safemode is not to prevent the operator
from writing to the fuse bits at all, but rather to prevent
inadvertent fuse bit changes resulting out of flakey (usually
simple bit-bang) programming hardware. Actually, the first
implementation of safemode even prevented any writes to the
fuse bits (unless you disabled it using -u), and that caused
the majority of users to object. Additionally, safemode never
writes anything to the fuses without asking the operator.

If you tell us more about your setup, and in particular some
analysis about why the fuses might have been read wrong
initially, perhaps there will be some help to you, and/or
some additional improvement to safemode. Right now, it
already reads each fuse three times, and refuses to continue
if these three readings disagree.

Joerg Wunsch <joerg_wunsch>
Project Administrator
Sat 23 Dec 2006 06:54:00 PM UTC, original submission:

hi,

this kind of "safemode" destroyed the fusebits of three of my avrs.
when on startup the fusebits read wrong, the safemode writes back the wrong fusebits.
could you please implement a "real" safemode that refuses the write access to the fuses and not a recovery mode?

sincerely,
stefan noll

Anonymous

 

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by fischl (Posted a comment)
  • -unavailable- added by joerg_wunsch (Posted a comment)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 5 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Fri 02 Feb 2007 04:32:08 PM UTCfischlStatusIn Progress=>Fixed
      Open/ClosedOpen=>Closed
    Sun 07 Jan 2007 09:59:57 PM UTCjoerg_wunschStatusNeed Info=>In Progress
      Assigned toNone=>fischl
    Sat 23 Dec 2006 10:09:31 PM UTCjoerg_wunschStatusNone=>Need Info

    Back to the top


    Powered by Savane 3.1-cleanup1