AT32UC3B0256-A2UR Atmel, AT32UC3B0256-A2UR Datasheet - Page 375

• Manufacturer Part Number: AT32UC3B0256-A2UR
• Description: MCU AVR32 256K FLASH 64-TQFP
• Manufacturer: Atmel
• Series: AVR®32 UC3r

Specifications of AT32UC3B0256-A2UR

• Package / Case: 64-TQFP, 64-VQFP
• Voltage - Supply (vcc/vdd): 1.65 V ~ 1.95 V
• Operating Temperature: -40°C ~ 85°C
• Speed: 60MHz
• Number Of I /o: 44
• Core Processor: AVR
• Program Memory Type: FLASH
• Ram Size: 32K x 8
• Program Memory Size: 256KB (256K x 8)
• Data Converters: A/D 8x10b
• Oscillator Type: Internal
• Peripherals: Brown-out Detect/Reset, DMA, POR, PWM, WDT
• Connectivity: I²C, IrDA, SPI, SSC, UART/USART, USB
• Core Size: 32-Bit
• Package: 64TQFP
• Device Core: AVR32
• Family Name: AT32
• Maximum Speed: 60 MHz
• Operating Supply Voltage: 1.8|3.3 V
• Data Bus Width: 32 Bit
• Number Of Programmable I/os: 44
• Interface Type: I2S/SPI/TWI/USART/USB
• On-chip Adc: 8-chx10-bit
• Number Of Timers: 3
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant
• Eeprom Size: -

22.7.1.7
32059K–03/2011
Pad Suspend
Figure 22-9 on page 375
Figure 22-9. Pad Behavior
Figure 22-10 on page 376
• There is no way the data of the pipe/endpoint 0 can be lost (except if it is de-allocated) as
• Deactivating then reactivating a same pipe/endpoint with the same configuration only
• When the user write a one to the ALLOC bit, the Configuration OK Status bit in the Endpoint
• In the Idle state, the pad is put in low power consumption mode, i.e., the differential receiver
• In the Active state, the pad is working.
memory allocation and de-allocation may affect only higher pipes/endpoints.
modifies temporarily the controller DPRAM pointer and size for this pipe/endpoint, but
nothing changes in the DPRAM, so higher endpoints seem to not have been moved and their
data is preserved as far as nothing has been written or received into them while changing the
allocation state of the first pipe/endpoint.
n Status register (UESTAn.CFGOK) is set only if the configured size and number of banks
are correct compared to their maximal allowed values for the endpoint and to the maximal
FIFO size (i.e. the DPRAM size), so the value of CFGOK does not consider memory
allocation conflicts.
of the USB pad is off, and internal pull-down with strong value(15K) are set in both DP/DM to
avoid floating lines.
shows the pad behavior.
illustrates the pad events leading to a PAD state change.
Idle
| DETACH = 1
| Suspend
USBE = 0
& DETACH = 0
& Suspend
USBE = 1
Active
AT32UC3B
375