bugAVR C Runtime Library - Bugs: bug #36350, FUSE4_DEFAULT wrong for Xmega A...


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

bug #36350: FUSE4_DEFAULT wrong for Xmega A devices

Submitter:  Joerg Wunsch <joerg_wunsch>
Submitted:  Mon 30 Apr 2012 11:50:42 AM UTC
Category:  Header Severity:  3 - Normal
Priority:  9 - Immediate Item Group:  Header files
Status:  None Percent Complete:  0%
Assigned to:  None Open/Closed:  Open
Release:  1.7.1 Fixed Release:  None

Sat 07 Sep 2019 06:51:31 PM UTC, comment #3: 

I see these on a fresh xmega32a4u:

fuse1: 0x00
fuse2: 0xff
fuse4: 0xfe
fuse5: 0xff

Sat 01 Dec 2012 05:17:44 PM UTC, comment #2: 

Just FYI, here's what I read off a fresh 128a3u that I've never messed with the fuses on:

fuse0: 0xff
fuse1: 0x00
fuse2: 0xff
fuse4: 0xfe
fuse5: 0xff

Erik Walthinsen <omega>
Fri 30 Nov 2012 07:04:40 PM UTC, comment #1: 

While you're at it, It seems to me that FUSE1_DEFAULT is also incorrect.
in iox128a1.h, it is defined as 0xFF
However, the xmega manual describes it to be 0x00.
Unfortunately I don't have hardware to verify this.

Mon 30 Apr 2012 11:50:42 AM UTC, original submission:  

j@uriah 55% fgrep FUSE4_DEFAULT include/avr/iox*
include/avr/iox128a1.h:#define FUSE4_DEFAULT  (0xFF)
include/avr/iox128a3.h:#define FUSE4_DEFAULT  (0xFF)
include/avr/iox128d3.h:#define FUSE4_DEFAULT  (0xFF)
include/avr/iox16a4.h:#define FUSE4_DEFAULT  (0xFF)
include/avr/iox16d4.h:#define FUSE4_DEFAULT  (0xFF)
include/avr/iox192a3.h:#define FUSE4_DEFAULT  (0xFF)
include/avr/iox192d3.h:#define FUSE4_DEFAULT  (0xFF)
include/avr/iox256a3.h:#define FUSE4_DEFAULT  (0xFF)
include/avr/iox256a3b.h:#define FUSE4_DEFAULT  (0xFF)
include/avr/iox256d3.h:#define FUSE4_DEFAULT  (0xFF)
include/avr/iox32a4.h:#define FUSE4_DEFAULT  (0xFF)
include/avr/iox32d4.h:#define FUSE4_DEFAULT  (0xFF)
include/avr/iox64a1.h:#define FUSE4_DEFAULT  (0xFF)
include/avr/iox64a3.h:#define FUSE4_DEFAULT  (0xFF)
include/avr/iox64d3.h:#define FUSE4_DEFAULT  (0xFF)

Xmega A (as well as Xmega B) device have JTAGEN programmed in
FUSE4, so their default ought to be 0xFE.

This bug results in an application using:


and then accidentally programming all fuses (like through the
"ELF production file" in AVR Studio) in a batch erroneously
turngin off their JTAG access.

Joerg Wunsch <joerg_wunsch>
Group administrator


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by omega (Posted a comment)
  • -email is unavailable- added by arcanum (Updated the item)
  • -email is unavailable- added by joerg_wunsch (Submitted the item)

    Follows 1 latest change.

    Date Changed by Updated Field Previous Value => Replaced by
    2012-11-16 arcanum Priority5 - Normal 9 - Immediate

    Back to the top

    Powered by Savane 3.12