SH7760 Datasheet, PDF (976/1345 Pages) Renesas Technology Corp – SuperHTM RISC engine

In multiblock transfer, the transfer clock output should be temporarily halted at every block break
to select either to continue to the next block or to abort the multiblock transfer command by
issuing the CMD12 command, and the transfer clock output should be resumed. To continue to
the next block, the RD_CONTI and DATAEN bits should be set to 1. To issue the CMD12
command, the CMDOFF bit should be set to 1 to abort the command sequence on the MMCIF
side.
Note: The FIFO full interrupt source must be cleared (FIFO data read) only after five or more
transfer clock cycles have been passed since the interrupt occurred.
26.3.9 Command Timeout Control Register (CTOCR)
CTOCR specifies the period to generate a timeout for the command response.
The counter (CTOUTC), to which the peripheral bus does not have access, counts the transfer
clock to monitor the command timeout. The initial value of CTOUTC is 0, and CTOUTC starts
counting the transfer clock from the start of command transmission. CTOUTC is cleared and stops
counting the transfer clock when command response reception has been completed, or when the
command sequence has been aborted by setting the CMDOFF bit to 1.
When the command response cannot be received, CTOUTC continues counting the transfer clock,
and enters the command timeout error state when the number of transfer clock cycles reaches the
number specified in CTOCR. When the CTERIE bit in INTCR1 is set to 1, the CTERI flag in
INTSTR1 is set. As CTOUTC continues counting transfer clock, the CTERI flag setting condition
is repeatedly generated. To perform command timeout error handling, the command sequence
should be aborted by setting the CMDOFF bit to 1, and then the CTERI flag should be cleared to
prevent extra-interrupt generation.
Bit: 7
-
Initial value: 0
R/W: R
6
5
-
-
0
0
RR
4
3
-
-
0
0
RR
2
1
0
- _{CTSEL1 CTSEL0}
0
0
0
R R/W R/W
Bit
7 to 2
Bit
Name
—
Initial
Value R/W
All 0 R
Description
Reserved
These bits are always read as 0. The write value should
always be 0.
Rev. 1.0, 02/03, page 926 of 1294