avrdude-dev
[Top][All Lists]
Advanced

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

[avrdude-dev] writing two Fuse Bytes faild


From: Markus Burrer
Subject: [avrdude-dev] writing two Fuse Bytes faild
Date: Sat, 12 Dec 2009 10:54:10 +0100
User-agent: Thunderbird 2.0.0.23 (X11/20090817)

Hi, if I try to write more than one fuse byte with one command, the
second fuse byte fails. For example

avrdude -pm32 -Ulfuse:w:0xff:m -U hfuse:w:0xc9:m

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.00s

avrdude: Device signature = 0x1e9502
avrdude: reading input file "0xff"
avrdude: writing lfuse (1 bytes):

Writing | ################################################## | 100% 0.00s

avrdude: 1 bytes of lfuse written
avrdude: verifying lfuse memory against 0xff:
avrdude: load data lfuse data from input file 0xff:
avrdude: input file 0xff contains 1 bytes
avrdude: reading on-chip lfuse data:

Reading | ################################################## | 100% 0.00s

avrdude: verifying ...
avrdude: 1 bytes of lfuse verified
avrdude: reading input file "0xc9"
avrdude: writing hfuse (1 bytes):

Writing |                                                    | 0% 0.00s
***failed; 
Writing | ################################################## | 100% 0.03s

avrdude: 1 bytes of hfuse written
avrdude: verifying hfuse memory against 0xc9:
avrdude: load data hfuse data from input file 0xc9:
avrdude: input file 0xc9 contains 1 bytes
avrdude: reading on-chip hfuse data:

Reading | ################################################## | 100% 0.00s

avrdude: verifying ...
avrdude: verification error, first mismatch at byte 0x0000
         0xc9 != 0x99
avrdude: verification error; content mismatch

avrdude: safemode: hfuse changed! Was c9, and is now 99
Would you like this fuse to be changed back? [y/n] n
avrdude: safemode: Fuses OK

avrdude done.  Thank you.

If I repeat the same command, both fuse bytes are written successfull.
What's wrong here? (I'm using Ubuntu Linux)

Regards
Markus





reply via email to

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