TMP92xy21FG Toshiba, TMP92xy21FG Datasheet - Page 263

• Manufacturer Part Number: TMP92xy21FG
• Manufacturer: Toshiba

Specifications of TMP92xy21FG

• Package: LQFP144
• Rom Types(m=mask,p=otp, F=flash,e=eeprom): Romless
• Rom Combinations: Romless
• Ram Combinations: 16
• Architecture: 32-bit CISC
• Usb/spi Channels: -
• Uart/sio Channels: 2
• I2c/sio Bus Channels: -
• (s)dram Controller: 1
• Adc 10-bit Channel: 4
• Da Converter: -
• Timer 8-bit Channel: 4
• Timer 16-bit Channel: 1
• Pwm 8-bit Channels: -
• Pwm 16-bit Channels: -
• Cs/wait Controller: 4
• Dual Clock: Y
• Number Of I/o Ports: 82
• Power Supply Voltage(v): 3.0 to 3.6

(d) Isochronous transfer type
(d-1) Isochronous transmission mode
to each frame.
Isochronous transfer type transfer only 2 phases (token, data) and it does not use
handshake phase. And data PID for data phase is always DATA0 because this
transaction does not support toggle sequence. Therefore, UDC does not confirm
when data PID is in receiving mode.
transactions for completed transfers use receiving SOF token. The UDC uses
FIFO that is divided into two in Isochronous transfer type.
Isochronous transfer type is guaranteed transfer by data number that is limited
However, this transfer does not retry when an error occurs. Therefore,
Isochronous transfer type processes data every frame. Therefore, all
is given below.
Control flow
FIFO in endpoint is transmitted by IN token in the next frame.
transferring.
X condition or Y condition. The flow below is explained as X Condition (packet
A), Y Condition (packet B) in present frame.
The transaction format for Isochronous transfer type format in transmitting
1. Token packet is received and address endpoint number error is confirmed,
2.
3.
4.
Isochronous transfer type is frame management. And data that is written to
Below are two conditions in FIFO of Isochronous transmission mode
FIFO that is divided into two (packet A and packet B) conditions is whether
X and Y conditions change one after the other by receiving SOF.
Control flow in the UDC when receiving IN token is shown below.
X. FIFO for storing data that transmits to host in present frame
Y. FIFO for storing data for transmitting host in next frame
DATA0. Next, data is transferred from FIFO (X condition) of packet A in
UDC to SIE, and DATA packet is generated.
•
•
and it checks whether the relevant endpoint transfer mode corresponds
with the IN token. If it does not correspond, the state returns to IDLE.
Condition of status register is confirmed.
•
Data packet is generated.
CRC bit (counted transfer data of FIFO from first to last) is attached to
last.
(DATASET register bit = 1)
(DATASET register bit = 0)
Data packet is generated. At this point, data PID is always attached to
Token: IN
Data: DATA0
INVALID condition: State returns to IDLE.
92CH21-261
TMP92CH21
2009-06-19