
- •Features
- •Disclaimer
- •Overview
- •Block Diagram
- •Pin Descriptions
- •Port B (PB7..PB0)
- •Port C (PC7..PC0)
- •Port D (PD7..PD0)
- •D-/SDATA
- •UGND
- •UVCC
- •UCAP
- •RESET/PC1/dW
- •XTAL1
- •XTAL2/PC0
- •AVR CPU Core
- •Introduction
- •Status Register
- •Stack Pointer
- •TABLE 1.
- •TABLE 2.
- •AVR AT90USB82/162 Memories
- •I/O Memory
- •Clock Systems and their Distribution
- •Clock Switch
- •Exemple of use
- •Swith from external clock to RC clock
- •Switch from RC clock to external clock
- •Clock Sources
- •Default Clock Source
- •External Clock
- •Internal PLL for USB interface
- •Idle Mode
- •Power-down Mode
- •Power-save Mode
- •Standby Mode
- •Analog Comparator
- •Brown-out Detector
- •Watchdog Timer
- •Port Pins
- •Resetting the AVR
- •Reset Sources
- •Power-on Reset
- •External Reset
- •Watchdog Reset
- •USB Reset
- •Watchdog Timer
- •TABLE 2.
- •TABLE 2.
- •Interrupts
- •TABLE 2.
- •Introduction
- •Configuring the Pin
- •Toggling the Pin
- •Reading the Pin Value
- •TABLE 3.
- •Unconnected Pins
- •Alternate Port Functions
- •Register Description for I/O-Ports
- •Timer/Counter0 and Timer/Counter1 Prescalers
- •Internal Clock Source
- •Prescaler Reset
- •External Clock Source
- •8-bit Timer/Counter0 with PWM
- •Overview
- •Registers
- •Definitions
- •Counter Unit
- •Normal Mode
- •Fast PWM Mode
- •8-bit Timer/Counter Register Description
- •Overview
- •Registers
- •Definitions
- •Counter Unit
- •Input Capture Unit
- •Noise Canceler
- •Force Output Compare
- •Normal Mode
- •Fast PWM Mode
- •16-bit Timer/Counter Register Description
- •TABLE 2.
- •TABLE 2.
- •Slave Mode
- •Master Mode
- •Data Modes
- •USART
- •Overview
- •Clock Generation
- •External Clock
- •Frame Formats
- •Parity Bit Calculation
- •TABLE 2.
- •TABLE 3.
- •TABLE 4.
- •Parity Generator
- •TABLE 3.
- •TABLE 2.
- •Receiver Error Flags
- •Parity Checker
- •Disabling the Receiver
- •TABLE 2.
- •Using MPCMn
- •Receiver Flow Control
- •Overview
- •Clock Generation
- •Frame Formats
- •TABLE 2.
- •Data Transfer
- •TABLE 3.
- •USB controller
- •Features
- •Block Diagram
- •Typical Application Implementation
- •Device mode
- •Bus Powered device
- •Introduction
- •Interrupts
- •Power modes
- •Idle mode
- •Power down
- •Freeze clock
- •Memory access capability
- •Memory management
- •PAD suspend
- •D+/D- Read/write
- •Registers description
- •USB general registers
- •USB Software Operating modes
- •USB Device Operating modes
- •Introduction
- •Power-on and reset
- •Endpoint reset
- •USB reset
- •Endpoint selection
- •Endpoint activation
- •Address Setup
- •Detach
- •Remote Wake-up
- •STALL request
- •Special consideration for Control Endpoints
- •STALL handshake and Retry mechanism
- •CONTROL endpoint management
- •Control Write
- •Control Read
- •Overview
- •“Manual” mode
- •Detailed description
- •IN endpoint management
- •“Manual” mode
- •Detailed description
- •Abort
- •Isochronous mode
- •Underflow
- •CRC Error
- •Overflow
- •Interrupts
- •Registers
- •USB device general registers
- •USB device endpoint registers
- •Characteristics
- •Analog Comparator
- •Application Section
- •Boot Reset Fuse
- •Simple Assembly Code Example for a Boot Loader
- •debugWIRE On-chip Debug System
- •Features
- •Overview
- •Physical Interface
- •Software Break Points
- •Limitations of debugWIRE
- •debugWIRE Related Register in I/O Memory
- •Fuse Bits
- •Latching of Fuses
- •Signature Bytes
- •Calibration Byte
- •Signal Names
- •Chip Erase
- •Reading the Flash
- •Reading the EEPROM
- •Electrical Characteristics
- •Absolute Maximum Ratings*
- •DC Characteristics
- •External Clock Drive Waveforms
- •External Clock Drive
- •Maximum speed vs. VCC
- •Supply Current of IO modules
- •Example 1
- •Example 2
- •Example 3
- •Instruction Set Summary
- •Packaging Information
- •TQFP32

Table 33. Lock Bit Protection Modes(1)(2) (Continued)
Memory Lock Bits |
Protection Type |
|||
|
|
|
|
|
BLB1 Mode |
BLB12 |
BLB11 |
|
|
|
|
|
|
|
1 |
1 |
1 |
No restrictions for SPM or (E)LPM accessing the Boot |
|
Loader section. |
||||
|
|
|
||
|
|
|
|
|
2 |
1 |
0 |
SPM is not allowed to write to the Boot Loader section. |
|
|
|
|
|
|
|
|
|
SPM is not allowed to write to the Boot Loader section, |
|
|
|
|
and (E)LPM executing from the Application section is not |
|
3 |
0 |
0 |
allowed to read from the Boot Loader section. If Interrupt |
|
Vectors are placed in the Application section, interrupts |
||||
|
|
|
||
|
|
|
are disabled while executing from the Boot Loader |
|
|
|
|
section. |
|
|
|
|
|
|
|
|
|
(E)LPM executing from the Application section is not |
|
|
|
|
allowed to read from the Boot Loader section. If Interrupt |
|
4 |
0 |
1 |
Vectors are placed in the Application section, interrupts |
|
|
|
|
are disabled while executing from the Boot Loader |
|
|
|
|
section. |
|
|
|
|
|
Notes: 1. Program the Fuse bits and Boot Lock bits before programming the LB1 and LB2. 2. “1” means unprogrammed, “0” means programmed
Fuse Bits |
The AT90USB82/162 has four Fuse bytes. Table 34 - Table 36 describe briefly the functionality |
||||
|
of all the fuses and how they are mapped into the Fuse bytes. Note that the fuses are read as |
||||
|
logical zero, “0”, if they are programmed. |
|
|
||
|
Table 34. Extended Fuse Byte |
|
|
||
|
|
|
|
|
|
|
Fuse Low Byte |
Bit No |
Description |
Default Value |
|
|
|
|
|
|
|
|
– |
7 |
– |
1 |
|
|
|
|
|
|
|
|
– |
6 |
– |
1 |
|
|
|
|
|
|
|
|
– |
5 |
– |
1 |
|
|
|
|
|
|
|
|
– |
4 |
– |
1 |
|
|
|
|
|
|
|
|
HWBE |
3 |
Hardware Boot Enable |
0 (programmed) |
|
|
|
|
|
|
|
|
BODLEVEL2(1) |
2 |
Brown-out Detector trigger level |
1 (unprogrammed) |
|
|
BODLEVEL1(1) |
1 |
Brown-out Detector trigger level |
1 (unprogrammed) |
|
|
BODLEVEL0(1) |
0 |
Brown-out Detector trigger level |
1 (unprogrammed) |
|
Note: 1. See Table 16 on page 49 for BODLEVEL Fuse decoding.
234
7707A–AVR–01/07

Table 35. Fuse High Byte
Fuse High Byte |
Bit No |
Description |
Default Value |
||
|
|
|
|
|
|
DWEN(4) |
7 |
|
1 |
(unprogrammed, |
|
Enable debugWIRE |
debugWIRE disabled) |
||||
|
|
||||
|
|
|
|
|
|
RSTDSBL |
6 |
|
1 |
(unprogrammed, Reset |
|
Disable Reset |
enabled) |
||||
|
|
||||
|
|
|
|
|
|
SPIEN(1) |
5 |
Enable Serial Program and Data |
0 |
(programmed, SPI prog. |
|
Downloading |
enabled) |
||||
|
|
||||
|
|
|
|
|
|
WDTON(3) |
4 |
Watchdog Timer always on |
1 |
(unprogrammed) |
|
EESAVE |
3 |
EEPROM memory is preserved |
1 |
(unprogrammed, |
|
through the Chip Erase |
EEPROM not preserved) |
||||
|
|
||||
|
|
|
|
|
|
BOOTSZ1 |
2 |
Select Boot Size (see Table 37 |
|
(programmed)(2) |
|
for details) |
0 |
||||
|
|
||||
BOOTSZ0 |
1 |
Select Boot Size (see Table 37 |
|
(programmed)(2) |
|
for details) |
0 |
||||
|
|
||||
BOOTRST |
0 |
Select Reset Vector |
1 |
(unprogrammed) |
|
|
|
|
|
|
Note: 1. The SPIEN Fuse is not accessible in serial programming mode.
2.The default value of BOOTSZ1..0 results in maximum Boot Size. See Table 29 on page 229 for details.
3.See “Watchdog Timer Control Register - WDTCSR” on page 56 for details.
4.Never ship a product with the DWEN Fuse programmed regardless of the setting of Lock bits and RSTDSBL Fuse. A programmed DWEN Fuse enables some parts of the clock system to
be running in all sleep modes. This may increase the power consumption.
Table 36. Fuse Low Byte
Fuse Low Byte |
Bit No |
Description |
Default Value |
|
|
|
|
|
|
CKDIV8(4) |
7 |
Divide clock by 8 |
0 |
(programmed) |
CKOUT(3) |
6 |
Clock output |
1 |
(unprogrammed) |
SUT1 |
5 |
Select start-up time |
1 |
(unprogrammed)(1) |
SUT0 |
4 |
Select start-up time |
0 |
(programmed)(1) |
CKSEL3 |
3 |
Select Clock source |
0 |
(programmed)(2) |
CKSEL2 |
2 |
Select Clock source |
0 |
(programmed)(2) |
CKSEL1 |
1 |
Select Clock source |
1 |
(unprogrammed)(2) |
CKSEL0 |
0 |
Select Clock source |
0 |
(programmed)(2) |
Note: 1. The default value of SUT1..0 results in maximum start-up time for the default clock source. See Table 15 on page 47 for details.
2.The default setting of CKSEL3..0 results in internal RC Oscillator @ 8 MHz. See Table 3 on page 29 for details.
3.The CKOUT Fuse allow the system clock to be output on PORTC7. See “Clock Output Buffer” on page 33 for details.
4.See “System Clock Prescaler” on page 33 for details.
The status of the Fuse bits is not affected by Chip Erase. Note that the Fuse bits are locked if Lock bit1 (LB1) is programmed. Program the Fuse bits before programming the Lock bits.
235
7707A–AVR–01/07