ATSAM3S1BA-AU Atmel, ATSAM3S1BA-AU Datasheet - Page 935

• Manufacturer Part Number: ATSAM3S1BA-AU
• Description: IC MCU 32BIT 64KB FLASH 64LQFP
• Manufacturer: Atmel
• Series: SAM3Sr

Specifications of ATSAM3S1BA-AU

• Core Processor: ARM® Cortex-M3™
• Core Size: 32-Bit
• Speed: 64MHz
• Connectivity: I²C, MMC, SPI, SSC, UART/USART, USB
• Peripherals: Brown-out Detect/Reset, DMA, I²S, POR, PWM, WDT
• Number Of I /o: 47
• Program Memory Size: 64KB (64K x 8)
• Program Memory Type: FLASH
• Ram Size: 16K x 8
• Voltage - Supply (vcc/vdd): 1.62 V ~ 1.95 V
• Data Converters: A/D 10x10/12b, D/A 2x12b
• Oscillator Type: Internal
• Operating Temperature: -40°C ~ 85°C
• Package / Case: 64-LQFP
• Controller Family/series: ATSAM3S
• No. Of I/o's: 47
• Ram Memory Size: 16KB
• Cpu Speed: 64MHz
• No. Of Timers: 6
• Rohs Compliant: Yes
• Processor Series: ATSAM3x
• Core: ARM Cortex M3
• 3rd Party Development Tools: JTRACE-CM3, MDK-ARM, RL-ARM, ULINK2
• Development Tools By Supplier: ATSAM3S-EK
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant
• Eeprom Size: -
• Lead Free Status / Rohs Status: Details

37.6.2.3
Figure 37-9. Data OUT Transfer for Non Ping-pong Endpoints
6500C–ATARM–8-Feb-11
RX_DATA_BK0
(UDP_CSRx)
FIFO (DPR)
Content
USB Bus
Packets
Data OUT Transaction Without Ping-pong Attributes
Using Endpoints With Ping-pong Attributes
Data OUT Transaction
Data OUT
PID
Host Sends Data Payload
Written by USB Device
Data OUT 1
Data OUT transactions are used in control, isochronous, bulk and interrupt transfers and con-
duct the transfer of data from the host to the device. Data OUT transactions in isochronous
transfers must be done using endpoints with ping-pong attributes.
To perform a Data OUT transaction, using a non ping-pong endpoint:
An interrupt is pending while the flag RX_DATA_BK0 is set. Memory transfer between the USB
device, the FIFO and microcontroller memory can not be done after RX_DATA_BK0 has been
cleared. Otherwise, the USB device would accept the next Data OUT transfer and overwrite the
current Data OUT packet in the FIFO.
During isochronous transfer, using an endpoint with ping-pong attributes is obligatory. To be
able to guarantee a constant bandwidth, the microcontroller must read the previous data pay-
Data OUT 1
1. The host generates a Data OUT packet.
2. This packet is received by the USB device endpoint. While the FIFO associated to this
3. The microcontroller is notified that the USB device has received a data payload polling
4. The number of bytes available in the FIFO is made available by reading RXBYTECNT
5. The microcontroller carries out data received from the endpoint’s memory to its mem-
6. The microcontroller notifies the USB device that it has finished the transfer by clearing
7. A new Data OUT packet can be accepted by the USB device.
endpoint is being used by the microcontroller, a NAK PID is returned to the host. Once
the FIFO is available, data are written to the FIFO by the USB device and an ACK is
automatically carried out to the host.
RX_DATA_BK0 in the endpoint’s UDP_CSRx register. An interrupt is pending for this
endpoint while RX_DATA_BK0 is set.
in the endpoint’s UDP_CSRx register.
ory. Data received is available by reading the endpoint’s UDP_FDRx register.
RX_DATA_BK0 in the endpoint’s UDP_CSRx register.
Set by USB Device
ACK
Host Sends the Next Data Payload
Microcontroller Read
PID
Microcontroller Transfers Data
Data OUT 1
Data OUT2
Interrupt Pending
PID
Data OUT2
NAK
PID
Cleared by Firmware,
Data Payload Written in FIFO
Data OUT
PID
Host Resends the Next Data Payload
Written by USB Device
SAM3S Preliminary
Data OUT 2
Data OUT2
ACK
PID
935