![](http://datasheet.mmic.net.cn/30000/M66596FP_datasheet_2360759/M66596FP_93.png)
M66596FP/WG
rev .1.00
2006.3.14
page 91 of 127
3.8.1
Interval counter in the Host mode
3.8.1.1 Overview
Set the interval of a transaction as the IITV bit of PIPEPERI at the Interrupt transfer. This controller sends out the
token of Interrupt transfer according to the IITV bit.
3.8.1.2 Initialization of a counter
The conditions on which this controller initializes an interval counter are as follows.
(1) H/W reset
IITV
bit is initialized.
(2) S/W reset
IITV
bit is initialized.
(3) The return from Low-power sleep state
An IITV bit is initialized.
(4) Buffer memory initialization by ACLRM
A count is initialized although an IITV bit is not initialized. By setting an ACLRM bit to 0, the setting value of
IITV
is counted from the beginning.
In the following cases, an interval counter is not initialized.
(1) USB bus reset, USB suspensd
An IITV bit is not initialized. By setting a UACT bit to 1, a count is started from the value before considering
as USB bus reset or a USB suspend state.
3.8.1.3 When a token is not transmitted
When as follows, a token is not transmitted even if it is the transmitting timing of a token. In such a case,
execution of a transaction is tried at the next interval.
(1) When PID is set as NAK or STALL
(2) When a buffer memory is not empty at the time of transmission of the IN direction (reception).
(3) When there is no transmitting data in a buffer memory at the time of transmission of the OUT direction
(transmission).
3.9 Isochronous transfers(PIPE1-2)
The controller is equipped with the following functions pertaining to isochronous transfers.
(1)
Notification of isochronous transfer error information
(2)
Interval counter (specified by the IITV bit)
(3)
Isochronous IN transfer data setup control (IDLY function)
(4)
Isochronous IN transfer buffer flush function (specified by the IFIS bit)
(5)
SOF pulse output function
The controller does not support the High-Bandwidth transfers of isochronous transfers.