SAM9G10 Atmel Corporation, SAM9G10 Datasheet - Page 555

• Manufacturer Part Number: SAM9G10
• Manufacturer: Atmel Corporation

Specifications of SAM9G10

• Flash (kbytes): 0 Kbytes
• Pin Count: 217
• Max. Operating Frequency: 266 MHz
• Cpu: ARM926
• Hardware Qtouch Acquisition: No
• Max I/o Pins: 96
• Ext Interrupts: 96
• Usb Transceiver: 3
• Usb Speed: Full Speed
• Usb Interface: Host, Device
• Spi: 2
• Twi (i2c): 1
• Uart: 4
• Ssc: 3
• Sd / Emmc: 1
• Graphic Lcd: Yes
• Video Decoder: No
• Camera Interface: No
• Resistive Touch Screen: No
• Temp. Sensor: No
• Crypto Engine: No
• Sram (kbytes): 16
• Self Program Memory: NO
• External Bus Interface: 1
• Dram Memory: sdram
• Nand Interface: Yes
• Picopower: No
• Temp. Range (deg C): -40 to 85
• I/o Supply Class: 1.8/3.3
• Operating Voltage (vcc): 1.08 to 1.32
• Fpu: No
• Mpu / Mmu: No/Yes
• Timers: 3
• Output Compare Channels: 3
• Input Capture Channels: 3
• 32khz Rtc: Yes
• Calibrated Rc Oscillator: No

33.6.9.9
33.6.9.10
33.6.9.11
11053B–ATARM–22-Sep-11
11053B–ATARM–22-Sep-11
Data OUT
Bulk OUT or Interrupt OUT
Bulk OUT or Interrupt OUT: Receiving a Packet Under Application Control (Host to Device)
Like data IN, data OUT packets are sent by the host during the data or the status stage of con-
trol transfer or during an interrupt/bulk/isochronous OUT transfer. Data buffers are sent packet
by packet under the control of the application or under the control of the DMA channel.
Algorithm Description for Each Packet:
Note:
Algorithm to Fill Several Packets:
If the application doesn’t know the size of the receive buffer, instead of using the BUSY_BANK
interrupt, the application must use RX_BK_RDY.
• ERR_FLUSH: At least one packet has been sent inside the microframe, but the number of
• ERR_TRANS: At least one packet has been sent inside the microframe, but the number of
• ERR_FL_ISO + ERR_FLUSH: At least one packet has been sent inside the microframe, but
• ERR_FL_ISO + ERR_TRANS: At least one packet has been sent inside the microframe, but
• ERR_FLUSH + ERR_TRANS: The first token IN has been answered and it was the only one
• ERR_FL_ISO + ERR_FLUSH + ERR_TRANS: The first token IN has been treated, the data
• The application enables an interrupt on RX_BK_RDY.
• When an interrupt on RX_BK_RDY is received, the application knows that UDPHS_EPTSTAx
• The application reads the BYTE_COUNT bytes from the endpoint.
• The application clears RX_BK_RDY.
• The application enables the interrupts of BUSY_BANK and AUTO_VALID.
• When a BUSY_BANK interrupt is received, the application knows that all banks available for
token IN received is lesser than the number of transactions actually validated (TX_BK_RDY)
and likewise with the NB_TRANS programmed.
token IN received is lesser than the number of programmed NB_TRANS transactions and the
packets not requested were not validated.
the data has not been validated in time to answer one of the following token IN.
the data has not been validated in time to answer one of the following token IN and the data
can be discarded at the microframe end.
received, a second bank has been validated but not the third, whereas NB_TRANS was
waiting for three transactions.
for the second Token IN was not available in time, but the second bank has been validated
before the end of the microframe. The third bank has not been validated, but three
transactions have been set in NB_TRANS.
register BYTE_COUNT bytes have been received.
the endpoint have been filled. Thus, the application can read all banks available.
If the application does not know the size of the transfer, it may not be a good option to use
AUTO_VALID. Because if a zero-length-packet is received, the RX_BK_RDY is automatically
cleared by the AUTO_VALID hardware and if the endpoint interrupt is triggered, the software will
not find its originating flag when reading the UDPHS_EPTSTAx register.
SAM9G35
SAM9G35
555
555