AT91SAM9G10-EK Atmel, AT91SAM9G10-EK Datasheet - Page 598

• Manufacturer Part Number: AT91SAM9G10-EK
• Description: KIT DEV FOR SAM9G10 ARM
• Manufacturer: Atmel
• Type: MCUr

Specifications of AT91SAM9G10-EK

• Contents: Board, Cables, Power Supply
• Silicon Manufacturer: Atmel
• Core Architecture: AVR
• Kit Contents: Board
• Svhc: No SVHC (15-Dec-2010)
• Mcu Supported Families: AT91SAM9G10, ARM926EJ-S
• Tool / Board Applications: Microcontroller
• Rohs Compliant: Yes
• For Use With/related Products: *
• Lead Free Status / RoHS Status: Contains lead / RoHS non-compliant

Figure 37-5. Setup Transaction Followed by a Data OUT Transaction
37.5.2.2
37.5.2.3
598
USB
Bus Packets
RXSETUP Flag
RX_Data_BKO
(UDP_CSRx)
FIFO (DPR)
Content
AT91SAM9G10
Data IN Transaction
Using Endpoints Without Ping-pong Attributes
Setup
PID
Setup Received
Data IN transactions are used in control, isochronous, bulk and interrupt transfers and conduct
the transfer of data from the device to the host. Data IN transactions in isochronous transfer
must be done using endpoints with ping-pong attributes.
To perform a Data IN transaction using a non ping-pong endpoint:
After the last packet has been sent, the application must clear TXCOMP once this has been set.
TXCOMP is set by the USB device when it has received an ACK PID signal for the Data IN
packet. An interrupt is pending while TXCOMP is set.
Warning: TX_COMP must be cleared after TX_PKTRDY has been set.
Note:
XX
1. The application checks if it is possible to write in the FIFO by polling TXPKTRDY in the
2. The application writes the first packet of data to be sent in the endpoint’s FIFO, writing
3. The application notifies the USB peripheral it has finished by setting the TXPKTRDY in
4. The application is notified that the endpoint’s FIFO has been released by the USB
5. The microcontroller writes the second packet of data to be sent in the endpoint’s FIFO,
6. The microcontroller notifies the USB peripheral it has finished by setting the TXPK-
7. The application clears the TXCOMP in the endpoint’s UDP_CSRx.
Data Setup
endpoint’s UDP_CSRx register (TXPKTRDY must be cleared).
zero or more byte values in the endpoint’s UDP_FDRx register,
the endpoint’s UDP_CSRx register.
device when TXCOMP in the endpoint’s UDP_CSRx register has been set. Then an
interrupt for the corresponding endpoint is pending while TXCOMP is set.
writing zero or more byte values in the endpoint’s UDP_FDRx register,
TRDY in the endpoint’s UDP_CSRx register.
Refer to Chapter 8 of the Universal Serial Bus Specification, Rev 2.0, for more information on the
Data IN protocol layer.
Set by USB Device
ACK
PID
Setup Handled by Firmware
Data OUT
PID
Interrupt Pending
Data Setup
Data OUT
Cleared by Firmware
NAK
PID
Data OUT
PID
Data Out Received
Set by USB
Device Peripheral
XX
Data OUT
6462A–ATARM–03-Jun-09
ACK
PID
Data
OUT