> -----Original Message----- > From: > avr-libc-dev-bounces+eric.weddington=atmel....@nongnu.org > [mailto:avr-libc-dev-bounces+eric.weddington=atmel....@nongnu. > org] On Behalf Of Galen Seitz > Sent: Friday, March 12, 2010 8:43 PM > To: avr-libc-dev@nongnu.org > Subject: [avr-libc-dev] fuse API on the xmega16a4 > > The fuse API documentation doesn't seem to quite match up with the > xmega implementation. I tried using the FUSES macro, but it doesn't > appear to be defined when targeting an xmega16a4. However, the > following does work. > > /* Configure fuses. */ > NVM_FUSES_t __fuse FUSEMEM = { > .FUSEBYTE0 = FUSE0_DEFAULT, > .FUSEBYTE1 = 0x00, > .FUSEBYTE2 = (FUSE_BODPD0), > .FUSEBYTE4 = FUSE4_DEFAULT, > .FUSEBYTE5 = (FUSE_BODACT0 & FUSE_BODLVL2 & FUSE_BODLVL0) > }; > > > Is this a user error, a bug, or is the xmega fuse API intentionally > different?
My guess is that the API is intentionally different. However, it's a bug in that avr-libc is not correctly accounting for the differences. That's something we need to fix. _______________________________________________ AVR-libc-dev mailing list AVR-libc-dev@nongnu.org http://lists.nongnu.org/mailman/listinfo/avr-libc-dev
