HB28E016/D032/D064/B128MM2
52
Stream write
The data transfer starts N
WR
clock cycles after the card response to the sequential write command was
received. The bus transaction is identical to that of a write block command (see Figure “Timing of The
Block Write Command”). As the data transfer is not block-oriented, the data stream does not include the
CRC checksum. Consequently the host can not receive any CRC status information from the card. The
data stream is terminated by a stop command. The bus transaction is identical to the write block option
when a data block is interrupted by the stop command (see Figure “Stop Transmission During Data
Transfer From The Host”).
S T content CRC E Z Z P * * * P
CMD
Host command
S T content CRC E
Card response
N
CR
cycles
S T content
Host command
D D D D D D D D D D E Z Z S L
Valid write data
DAT
* * * * * * * * * * * * * * * * * * E Z Z Z Z Z Z Z Z
Card is programming
N
ST
Stop Transmission During Data Transfer From The Host
Erase block timing
The host must first tag the sector to erase. The tagged sector(s) are erased in parallel by using the CMD32-
CMD38. The card busy signaling is also used for the indication of the card erase procedure duration. In
this case the end of the card busy signaling also does mean that the erase of all tagged sectors has been
finished. The host can (also) request the card to send the actual card state using the CMD13.
L ... pull down to LOW bit
T content CRC
CMD
DAT
CMD
DAT
* * * * * * * *
Z Z * * * * * * * * * * * Z Z Z S L L * * * * * * * * * * * * * * * * * * * * L E
L
L E
E
S T
Z
* * * * *
Card active
N
CR
S T content CRC E
Card response
CRC E
content
Host active
card is erasing
card busy
Host command
Host active
Card active
Timing of Erase Operation