![](http://datasheet.mmic.net.cn/100000/IF180C52TXXX-20R_datasheet_3493957/IF180C52TXXX-20R_87.png)
87
32099I–01/2012
AT32UC3L016/32/64
The SECURE fuses have the following functionality:
To erase or write a general-purpose fuse bit, the commands Write General-Purpose Fuse Bit
(WGPB) and Erase General-Purpose Fuse Bit (EGPB) are provided. Writing one of these com-
mands, together with the number of the fuse to write/erase, performs the desired operation.
An entire General-Purpose Fuse byte can be written at a time by using the Program GP Fuse
Byte (PGPFB) instruction. A PGPFB to GP fuse byte 2 is not allowed if the flash is locked by the
security bit. The PFB command is issued with a parameter in the PAGEN field:
PAGEN[2:0] - byte to write
PAGEN[10:3] - Fuse value to write
All general-purpose fuses can be erased by the Erase All General-Purpose fuses (EAGP) com-
mand. An EAGP command is not allowed if the flash is locked by the security bit.
Two errors can be detected in the FSR register after issuing these commands:
Programming Error: A bad keyword and/or an invalid command have been written in the
FCMD register.
Lock Error:
– A write or erase of the BOOTPROT or EPFL or UPROT fuse bits was attempted
while the flash is locked by the security bit.
– A write or erase of the SECURE fuse bits was attempted when SECURE mode was
enabled.
The lock bits are implemented using the lowest 16 general-purpose fuse bits. This means that
the 16 lowest general-purpose fuse bits can also be written/erased using the commands for
Table 8-4.
Boot Loader Area Specified by BOOTPROT
BOOTPROT
Pages protected by
BOOTPROT
Size of protected
memory
7None
0
6
0-1
512 byte
50-3
1Kbyte
40-7
2Kbyte
3
0-15
4Kbyte
2
0-31
8Kbyte
10-63
16Kbyte
0
0-127
32Kbyte
Table 8-5.
Secure State Configuration
SECURE
Functionality
SSE
SSDE
00
Secure state disabled
0
01
Secure enabled, secure state debug enabled
1
10
Secure enabled, secure state debug disabled
1
0
11
Secure state disabled
0