AT90USB162-16MU Atmel, AT90USB162-16MU Datasheet - Page 187

• Manufacturer Part Number: AT90USB162-16MU
• Description: MCU AVR USB 16K FLASH 32-QFN
• Manufacturer: Atmel
• Series: AVR® 90USBr

Specifications of AT90USB162-16MU

• Core Processor: AVR
• Core Size: 8-Bit
• Speed: 16MHz
• Connectivity: EBI/EMI, PS/2, SPI, UART/USART, USB
• Peripherals: Brown-out Detect/Reset, POR, PWM, WDT
• Number Of I /o: 22
• Program Memory Size: 16KB (16K x 8)
• Program Memory Type: FLASH
• Eeprom Size: 512 x 8
• Ram Size: 512 x 8
• Voltage - Supply (vcc/vdd): 2.7 V ~ 5.5 V
• Oscillator Type: Internal
• Operating Temperature: -40°C ~ 85°C
• Package / Case: 32-TQFN
• Controller Family/series: AVR USB
• No. Of I/o's: 22
• Eeprom Memory Size: 512Byte
• Ram Memory Size: 512Byte
• Cpu Speed: 16MHz
• Rohs Compliant: Yes
• Processor Series: AT90USBx
• Core: AVR8
• Data Bus Width: 8 bit
• Data Ram Size: 512 B
• Interface Type: SPI, USART, debugWIRE
• Maximum Clock Frequency: 16 MHz
• Number Of Programmable I/os: 22
• Number Of Timers: 2
• Operating Supply Voltage: 2.7 V to 5.5 V
• Maximum Operating Temperature: + 85 C
• Mounting Style: SMD/SMT
• 3rd Party Development Tools: EWAVR, EWAVR-BL
• Development Tools By Supplier: ATAVRDRAGON, ATSTK500, ATSTK600, ATSTK525, ATSTK526, ATAVRISP2, ATAVRONEKIT, AT90USBKEY, ATEVK525
• Minimum Operating Temperature: - 40 C
• For Use With: ATSTK600 - DEV KIT FOR AVR/AVR32ATSTK526 - KIT STARTER FOR AT90USB82/162ATAVRDRAGON - KIT DRAGON 32KB FLASH MEM AVRATSTK525 - KIT STARTER FOR AT90USBAT90USBKEY2 - KIT DEMO FOR AT90USB
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant
• Data Converters: -
• Lead Free Status / Rohs Status: Details

PAD suspend
7707A–AVR–01/07
EPEN=1
ALLOC=1
Table 17. Allocation and reorganization USB memory flow
•
•
•
•
Note that :
•
•
•
The next figures illustrates the pad behaviour:
•
•
Free memory
Endpoints
activation
First, Endpoint 0 to Endpoint 4 are configured, in the growing order. The memory of each is
reserved in the DPRAM.
Then, the Endpoint 2is disabled (EPEN=0), but its memory reservation is internally kept by
the controller.
Its ALLOC bit is cleared: the Endpoint 3 “slides” down, but the Endpoint 4 does not “slide”.
Finally, the firmware chooses to reconfigure the Endpoint 2, but with a bigger size. The
controller reserved the memory after the endpoint 1 memory and automatically “slide” the
Endpoint 3. The Endpoint 4 does not move and a memory conflict appear, in that both
Endpoint 3 and 4 use a common area. The data of those endpoints are potentially lost.
the data of Endpoint 0 are never lost whatever the activation or deactivation of the higher
Endpoint. Its data is lost if it is deactivated.
Deactivate and reactivate the same Endpoint with the same parameters does not lead to a
“slide” of the higher endpoints. For those endpoints, the data are preserved.
CFGOK is set by hardware even in the case that there is a “conflict” in the memory
allocation.
In the “idle” mode, the pad is put in low power consumption mode.
In the “active” mode, the pad is working.
4
3
2
1
0
Endpoint Disable
Free memory
(ALLOC=1)
EPEN=0
4
3
1
0
Free its memory
Free memory
Lost memory
(ALLOC=0)
4
3
1
0
2 (bigger size)
Free memory
Activatation
Endpoint
3
1
0
4
Conflict
187