Corporate Headquarters • 140 Caspian Court • Sunnyvale, CA 94089
SanDisk Corporation
Phone (408) 542-0500 • Fax (408) 542-0503
www.sandisk.com
Revision 2.2 SanDisk SD Card Product Manual
®
SanDisk
Corporation general policy does not recommend the use of its products in life support applications where in a failure
or malfunction of the product may directly threaten life or injury. Per SanDisk Terms and Conditions of Sale, the user of SanDisk
products in life support applications assumes all risk of such use and indemnifies SanDisk against all damages. See “Disclaimer
of Liability.”
This document is for information use only and is subject to change without prior notice. SanDisk Corporation assumes no
responsibility for any errors that may appear in this document, nor for incidental or consequential damages resulting from the
furnishing, performance or use of this material. No part of this document may be reproduced, transmitted, transcribed, stored in
a retrievable manner or translated into any language or computer language, in any form or by any means, electronic,
mechanical, magnetic, optical, chemical, manual or otherwise, without the prior written consent of an officer of SanDisk
Corporation.
All parts of the SanDisk documentation are protected by copyright law and all rights are reserved.
SanDisk and the SanDisk logo are registered trademarks of SanDisk Corporation. CompactFlash is a U.S. registered trademark
of SanDisk Corporation.
Product names mentioned herein are for identification purposes only and may be trademarks and/or registered trademarks of
their respective companies.
SanDisk products are covered or licensed under one or more of the following U.S. Patent Nos. 5,070,032; 5,095,344; 5,168,465;
5,172,338; 5,198,380; 5,200,959; 5,268,318; 5,268,870; 5,272,669; 5,418,752; 5,602,987. Other U.S. and foreign patents
awarded and pending.
Lit. No. 80-13-00169 Rev. 2.2 119/04 Printed in U.S.A.
Revision History
June 2001 Revision 1.0—initial release; Product Rev. n/a
Nov 2001 Revision 1.1—minor editorial and technical changes; Product Rev. n/a
June 2002 Revision 1.2—minor editorial and technical changes; Product Rev. n/a
July 2002 Revision 1.3—minor editorial and technical changes; Product Rev. n/a
Nov 2002 Revision 1.4—minor editorial change; Product Rev. n/a
Mar 2003 Revision 1.5—changed power requirements in Section 2.3, Table 2.3; updated addresses in Appendix A;
adjusted footers and front matter; Product Rev. n/a
Aug 2003 Revision 1.6—added 512- and 1024-Mb capacities; updated Limited Warranty appendix; added Disclaimer
of Liability appendix; Product Rev. n/a
Sept 2003 Revision 1.7—minor revisions; added appnote as Appendix A; Product Rev. n/a
Nov 2003 Revision 1.8—changed VDD r/w values in Section 2 and Table 3-10; Product Rev. n/a
Dec 2003 Revision 1.9—changed VDD r/w values in Table 3-10; Product Rev. n/a
Jan 2004 Revision 2.0—changed value in Section 2.4 and 1.5.10.6; Product Rev. n/a
Apr 2004 Revision 2.1—added two additional part numbers; Product Rev.# 55
Oct/Nov 2004 Revision 2.2—added new performance info; command 6; added 2GB capacity; revised Hong Kong address;
moved application note to App E; updated all sections to reflect SD Phys Spec v1.10 info; Product Rev.# 57
The SanDisk Secure Digital (SD) Card is a flash-based memory card specifically designed
to meet the security, capacity, performance and environmental requirements inherent in
next generation mobile phones and consumer electronic devices. The SanDisk SD Card
includes a copyright protection mechanism that complies with the security of the SDMI
standard, and is faster and capable of higher memory capacity. The SD Card security
system uses mutual authentication and a “new cipher algorithm” to protect against illegal
usage of the card content. Unsecured access to the user‘s own content is also available. The
physical form factor: pin assignment and data transfer protocol, with some additions, are
forward compatible with the SD Card.
SanDisk SD Card communication is based on an advanced nine-pin interface (clock,
command, 4xData and 3xPower lines) designed to operate in a low voltage range. The
communication protocol is defined as part of this specification. The SD Card host interface
supports regular MultiMediaCard operation as well. In other words, MultiMediaCard
forward compatibility was kept. The main difference between the SD Card and
MultiMediaCard is the initialization process. Matsushita Electric Company (MEI), Toshiba
Corporation, and SanDisk Corporation defined the SD Card Specification originally.
Currently, the Secure Digital Association (SDA) controls the specifications. The SanDisk
SD Card was designed to be compatible with the SD Card Physical Specification.
The SD Card Interface allows for easy integration into any design, regardless of
microprocessor used. For compatibility with existing controllers, the SanDisk SD Card
offers, in addition to the SD Card Interface, an alternate communication protocol based on
the SPI standard.
Currently, the SanDisk SD Card provides up to 1024 million bytes of memory using flash
memory chips, which were designed especially for use in mass storage applications. In
addition to the mass storage specific flash memory chip, the SD Card includes an on-card
intelligent controller which manages interface protocols, security algorithms for copyright
protection, data storage and retrieval, as well as Error Correction Code (ECC) algorithms,
defect handling and diagnostics, power management and clock control.
Up to 50 MB/sec data transfer rate (using 4 parallel data lines)
Maximum data rate with up to 10 cards
►Correction of memory-field errors
►Copyrights Protection mechanism
Complies with highest security of SDMI standard
►Password-protection (specific models only)
►Write Protect using mechanical switch
►Built-in write protection features (permanent and temporary)
►Card detection (Insertion/Removal)
►Application-specific commands
►Comfortable erase mechanism
1.3 SD Card Standard
SanDisk SD cards are fully compatible with the SD Card Physical Layer System
Specification, Version 1.10. This specification is available from the SD Card Association.
SD Association
719 San Benito St., Suite C
Hollister, CA 95023 USA
Phone: +1 831-636-7322
FAX: +1 831-623-2248
E-mail: president@sdcard.org
URL: http://www.sdcard.org
SanDisk SD cards contain a high-level, intelligent subsystem as shown in Figure 1-1. This
intelligent (microprocessor) subsystem provides many capabilities not found in other types
of memory cards. These capabilities include:
• Host independence from details of erasing and programming flash memory
• Sophisticated system for managing defects (analogous to systems found in magnetic
disk drives)
• Sophisticated system for error recovery including a powerful error correction code
(ECC)
• Power management for low-power operation
1.5 Independent Flash Technology
The 512-byte sector size of the SanDisk SD Card is the same as that in an IDE magnetic
disk drive. To write or read a sector (or multiple sectors), the host computer software
simply issues a read or write command to the SD Card. This command contains the
address. The host software then waits for the command to complete. The host software
does not get involved in the details of how the flash memory is erased, programmed or
read. This is extremely important as flash devices are expected to get increasingly complex
in the future. Because the SD Card uses an intelligent on-board controller, the host system
software will not require changing as new flash memory evolves. In other words, systems
that support the SD Card today will be able to access future SD cards built with new flash
technology without having to update or change host software.
1.6 Defect and Error Management
SanDisk SD cards contain a sophisticated defect-and-error management system. This
system is analogous to the systems found in magnetic disk drives and in many cases offers
enhancements. For instance, disk drives do not typically perform a read after write to
confirm the data is written correctly because of the performance penalty that would be
incurred. SD cards do a read after write under margin conditions to verify that the data is
written correctly. In the rare case that a bit is found to be defective, SD cards replace this
bad bit with a spare bit within the sector header. If necessary, SD cards will even replace
the entire sector with a spare sector. This is completely transparent to the host and does not
consume any user data space.
The SD Card’s soft error rate specification is much better than the magnetic disk drive
specification. In the extremely rare case a read error does occur, SD cards have innovative
algorithms to recover the data. This is similar to using retries on a disk drive but is much
more sophisticated. The last line of defense is to employ a powerful ECC to correct the
data. If ECC is used to recover data, defective bits are replaced with spare bits to ensure
they do not cause any future problems. These defect and error management systems
coupled with the solid-state construction give SD cards unparalleled reliability.
A detailed description of the Copyright Protection mechanism and related security SD Card
commands can be found in the SD Security Specification from the SD Association. All SD
Card security-related commands operate in the data transfer mode.
As defined in the SDMI specification, data content saved in the card is already encrypted
and passes transparently to and from the card. No operation is done on the data and there is
no restriction to read the data at any time. Associated with every data packet (e.g., a song)
that is saved in the unprotected memory, there is special data that is saved in a protected
memory area for any access (Read, Write or Erase command) to or from the data in the
protected area.
For an authentication procedure is done between the card and the connected device, either
the LCM (PC for example) or the PD (portable device, such as SD player). After the
authentication process passes, the card is ready to accept or give data from/to the connected
device. While the card is in the secured mode of operation (after the authentication
succeeded) the argument and the associated data that is sent to the card or read from the
card are encrypted. At the end of the Read, Write or Erase operation, the card gets out
automatically of its secured mode.
1.8 Endurance
SanDisk SD cards have an endurance specification for each sector of 100,000 writes typical
(reading a logical sector is unlimited). This far exceeds what is typically required in almost
all SD Card applications. Therefore, extremely heavy use of the card in cellular phones,
personal communicators, pagers and voice recorders will use only a fraction of the total
endurance over the device’s lifetime. For instance—it would take over 10 years to wear out
an area on an SD Card based on a file of any size (from 512 bytes to maximum capacity)
being rewritten 3 times per hour, 8 hours a day, 365 days per year.
With typical applications, the endurance limit is not of any practical concern to the vast
majority of users.
1.9 Wear Leveling
Wear leveling is an intrinsic part of the erase pooling functionality of the SD Card, using
NAND memory. The Wear Level command is supported as a NOP operation to maintain
backward compatibility with existing software utilities.
1.10 Automatic Sleep Mode
A unique feature of the SanDisk SD Card is automatic entrance and exit from sleep mode.
Upon completion of an operation, the card enters the sleep mode to conserve power if no
further commands are received in less than five milliseconds (ms). The host does not have
to take any action for this to occur. However, in order to achieve the lowest sleep current,
the host needs to shut down its clock to the card. In most systems, the SD card is in sleep
mode except when the host is accessing it, thus conserving power.
When the host is ready to access the card in sleep mode, any command issued to it will
cause it to exit sleep, and respond.
Support for hot insertion will be required on the host but will be supported through the
connector. Connector manufacturers will provide connectors that have power-pins long
enough to be powered before contact is made with the other pins. This approach is similar
to that used in PCMCIA and MMCA devices to allow for hot insertion.
1.12 SD Card—SD Bus Mode
The following sections provide valuable information on the SD Card in SD Bus mode.
1.12.1 SD Card Standard Compliance
The SD Card is fully compliant with SD Card Physical Layer Standard Specification v1.10.
The structure of the Card Specific Data (CSD) register is compliant with CSD Structure
1.0.
1.12.2 Negotiating Operating Conditions
The SD Card supports the operation condition verification sequence defined in the SD Card
standard specifications. Should the SD Card host define an operating voltage range, which
is not supported by the SD Card it will put itself in an inactive state and ignore any bus
communication. The only way to get the card out of the inactive state is by powering it
down and up again.
In Addition the host can explicitly send the card to the inactive state by using the
GO_INACTIVE_STATE command.
1.12.3 Card Acquisition and Identification
The SD Card bus is a single master (SD Card host application) and a multi-slaves (cards)
bus. The Clock and Power lines are common to all cards on the bus. During the
identification process, the host accesses each card separately through its own command
lines. The SD Card’s CID Register is pre-programmed with a unique card identification
number, which is used during the identification procedure.
In addition, the SD Card host can read the card’s CID Register using the READ_CID
command. The CID Register is programmed during the SD Card testing and formatting
procedure, on the manufacturing floor. The SD Card host can only read, and not write, this
register.
An internal pull-up resistor on the DAT3 line may be used for card detection
(insertion/removal). The resistor can be disconnected during data transfer (using
ACMD42). Additional practical card detection methods can be found in SD Physical
Specification’s application notes given by the SDA.
1.12.4 Card Status
The card status is separated into the following two fields:
• Card Status is stored in a 32-bit status register that is sent as a data field in the card
response to host commands. The Status Register provides information about the card’s
current state and completion codes for the last host command. The card status can be
explicitly read (polled) with the SEND_STATUS command.
• SD Status is stored in 512 bits that are sent as a single data block after it was requested
by the host using the SD_STATUS (ACMD13) command. SD_STATUS contains
extended status bits that relate to BUS_WIDTH, security related bits and future
specific applications.
1.12.5 Memory Array Partitioning
The basic unit of data transfer to/from the SanDisk SD Card is one byte. All data transfer
operations that require a block size always define block lengths as integer multiples of
bytes. Some special functions need other partition granularity. Figure 1-2 shows the
Memory Array Partitioning.
For block-oriented commands, the following definition is used:
• Block—A unit related to block-oriented read and write commands. Its size is the
number of bytes that are transferred when one block command is sent by the host. The
size of a block is either programmable or fixed; information about allowed block sizes
and the programmability is stored in the CSD Register.
The granularity of the erasable units is, in general, not the same as for the block-oriented
commands:
• Sector—A unit related to the erase commands. Its size is the number of blocks that are
erased in one portion. The size of a sector is fixed for each device. The information
about the sector size (in blocks) is stored in the CSD Register.
For devices that include write protection, the following definition is used:
• WP Group—A minimal unit that may have individual write protection. Its size is the
number of groups to be write protected by one bit. The size of a WP group is fixed for
each device. The information about the size is stored in the CSD Register.
The SD Card supports two read/write modes as shown in Figure 1-3 and defined in Table
1-2.
Figure 1-3 Data Transfer Formats
Single Block Mode
Memory
Sectors
Memory
Sectors
Memory
Sectors
Start Address
(Read)
Memory
Sectors
Start Address
Data Area +
Protected size
(Blocks)
Memory
Sectors
Memory
Sectors
Start Address
(Write)
Multiple Block Mode
Memory
Sectors
Memory
Sectors
Write
Protected Area2 size
(Blocks)
Misalignment Error
Memory
Sectors
Start Address
(Read/Write)
Memory
Sectors
StopStart
Memory
Sectors
Memory
Sectors
Read
User Area
(Blocks0
Memory
Sectors
Memory
Sectors
Stop
Table 1-2 Mode Definitions
Mode Description
Single Block In this mode the host reads or writes one data block in a pre-specified length. The
data block transmission is protected with 16-bit CRC that is generated by the
sending unit and checked by the receiving unit.
The block length for read operations is limited by the device sector size (512 bytes)
but can be as small as a single byte. Misalignment is not allowed. Every data block
must be contained in a single physical sector.
The block length for write operations must be identical to the sector size and the
start address aligned to a sector boundary.
Multiple Block This mode is similar to the single block mode, except for the host can read/write
multiple data blocks (all have the same length) that are stored or retrieved from
contiguous memory addresses starting at the address specified in the command.
The operation is terminated with a stop transmission command.
Misalignment and block length restrictions apply to multiple blocks and are identical
to the single block read/write operations.
1.12.7 Data Transfer Rate
The SD Card can be operated using either a single data line (DAT0) or four data lines
(DAT0-DAT3) for data transfer. The maximum data transfer rate for a single data line is 50Mb per second, and 200-Mb (25 MB) per second using four data lines.
Every sector is protected with an error correction code (ECC). The ECC is generated (in
the memory card) when the sectors are written and validated when the data is read. If
defects are found, the data is corrected prior to transmission to the host.
1.12.9 Write Protection
Two-card level write-protection options are available: permanent and temporary. Both can
be set using the PROGRAM_CSD command (refer to CSD Programming). The permanent
write-protect bit, once set, cannot be cleared. This feature is implemented in the SD Card
controller firmware and not with a physical OTP cell.
Use the Write Protect (WP) Switch located on the card’s side edge to prevent the host from
writing to or erasing data on the card. The WP switch does not have any influence on the
internal Permanent or Temporary WP bits in the CSD Register.
1.12.10 Copy Bit
The copy bit can be used to mark an SD Card content as an original or a copy. The copy
bit of the card is programmed as a copy when testing and formatting are performed during
manufacturing. When set, the copy bit in the CSD Register is a copy and cannot be cleared.
The card is available with the copy-bit set or cleared. If the bit is set, it indicates that the
card is a master. This feature is implemented in the card’s controller firmware and not with
a physical OTP cell.
1.12.11 CSD Register
All SD Card configuration information is stored in the CSD Register. The MSB bytes of
the register contain manufacturer data and the two least significant bytes contain the hostcontrolled data: the card copy/write protection, and the user file format.
The host can read the CSD Register and alter the host-controlled data bytes using the
SEND_CSD and PROGRAM_CSD commands.
1.13 SPI Mode
The SPI mode is a secondary communication protocol for SD cards. This mode is a subset
of the SD Protocol, designed to communicate with an SPI channel, commonly found in
Motorola and other vendors’ microcontrollers.
Table 1-3 SPI Mode
Function Description
Negotiating Operating Conditions The operating condition negotiation function of the SD Card bus
Card Acquisition and Identification The host must know the number of cards currently connected on
is supported differently in SPI mode by using the READ_OCR
(CMD58) command. The host works within the valid voltage
range (2.7 to 3.6 v) of the card or put the card in inactive state
by sending a GO_INACTIVE command to the card.
the bus. Specific card selection is done via the CS signal
(CD/DAT3). The internal pull-up resistor on the CD/DAT3 line
may be used for card detection (insertion/removal). Additional
practical card detection methods can be found in SD Physical
Specification’s Application Notes given by the SDA.
The SanDisk SD Card has nine exposed contacts on one side as shown in Figure 3-1. The
host is connected to the card using a dedicated 9-pin connector.
Table 3-1 SD Card Pad Assignment
Pin No. Name Type1 Description
SD Mode
1 CD/DAT32 I/O3, PP Card detect/Data line [Bit 3]
2 CMD I/O, PP Command/Response
3 V
4 VDD S Supply voltage
5 CLK I Clock
S Supply voltage ground
SS1
6 V
S Supply voltage ground
SS2
7 DAT0 I/O, PP Data line [Bit 0]
8 DAT1 I/O, PP Data line [Bit 1]
9 DAT2 I/O, PP Data line [Bit 2]
SPI Mode
1 CS I Chip Select (active low)
2 DataIn I Host-to-card Commands and Data
3 V
S Supply voltage ground
SS1
4 VDD S Supply voltage
5 CLK I Clock
6 V
S Supply voltage ground
SS2
7 DataOut O Card-to-host Data and Status
8 RSV4 --- Reserved
9 RSV5 --- Reserved
1
Type Key: S=power supply; I=input; O=output using push-pull drivers; PP=I/O using push-pull drivers
2
The extended DAT lines (DAT1-DAT3) are input on power up. They start to operate as DAT lines after the
SET_BUS_WIDTH command. It is the responsibility of the host designer to connect external pullup resistors to
all data lines even if only DAT0 is to be used. Otherwise, non-expected high current consumption may occur due
to the floating inputs of DAT1 & DAT2 (in case they are not used).
3
After power up, this line is input with 50Kohm(+/-20Kohm) pull-up (can be used for card detection or SPI mode
selection). The pull-up may be disconnected by the user, during regular data transfer, with
SET_CLR_CARD_DETECT (ACMD42) command.
4
The ‘RSV’ pins are floating inputs. It is the responsibility of the host designer to connect external pullup resistors
to those lines. Otherwise non-expected high current consumption may occur due to the floating inputs.
Each card has a set of information registers (refer to Table 3-3). Detailed descriptions are
provided in Section 3.5.
Table 3-2 SD Card Registers
Name Width Description
CID 128 Card identification number: individual card number for identification.
RCA6 16 Relative card address: local system address of a card, dynamically
CSD 128 Card specific data: information about the card operation conditions.
SCR 64 SD Configuration Register: information about the SD Card’s special
OCR 32 Operation Condition Register
suggested by the card and approved by the host during initialization.
features capabilities.
The host may reset the cards by switching the power supply off and on again. The card has
its own power-on detection circuitry that puts the card into an idle state after the power-on.
The GO_IDLE (CMD0) command can also reset the card.
During the initialization process, commands are sent to each card individually, allowing the
application to detect the cards and assign logical addresses to the physical slots. Data is
always sent to each card individually. However, to simplify the handling of the card stack,
after initialization, all commands may be sent concurrently to all cards. Addressing
information is provided in the command packet.
The SD bus allows dynamic configuration of the number of data lines. After power-up, by
default, the SD Card will use only DAT0 for data transfer. After initialization, the host can
change the bus width (number of active data lines). This feature allows and easy trade off
between hardware cost and system performance.
Figure 3-3 Bus Circuitry Diagram
SD
Memory
Card
Host
R
DAT
and R
are pull-up resistors protecting the CMD and DAT line against bus floating
CMD
when no card is inserted or all card drivers are in a hi-impedance mode.
R
is used for the Write Protect Switch. See Section 5.4.2 for the component values and
WP
conditions.
3.2.1 Hot Insertion and Removal
Hot insertion and removal are allowed; inserting or removing the SD Card to or from the
bus will not damage the card. This also applies when the power is up.
• The inserted card will be properly reset when CLK carries a clock frequency (f
• Data transfer failures induced by removal/insertion should be detected by the bus
master using the CRC codes that suffix every bus transaction.
R
DAT
R
C1C
CMD
R
DAT0-3
2C
WP
Write Protect
CMD
3
1 2 3 4 5 6 7 8
9
Vss
SD Memory
Card
CLK
).
pp
3.2.2 Power Protection
Cards can be inserted or removed to and from the bus without damage, however if one of
the supply pins (V
line to supply the card.
Data transfer operations are protected by CRC codes; therefore, the SD bus master can
detect any bit changes induced by card insertion and removal. Also, the inserted card must
be properly reset when CLK carries a clock frequency f
If the hot insertion feature is implemented in the host, the host must withstand a shortcut
between V
The SD Card SPI Interface is compatible with SPI hosts available on the market. Similar to
any other SPI device, the SD Card SPI channel consists of the following four signals:
• CS—Host-to-card Chip Select signal
• CLK—Host-to-card Clock signal
• DataIn—Host-to-card Data signal
• DataOut—Card-to-host Data signal
Another SPI common characteristic implemented in the SD Card are byte transfers. All
data tokens are multiples of 8-bit bytes and always byte-aligned to the CS signal. The SPI
standard defines the physical link only and not the complete data transfer protocol. In SPI
bus mode, the SD Card uses a subset of the SD Card protocol and command set.
The SD Card identification and addressing algorithms are replaced by the hardware CS
signal. A card (slave) is selected for every command by asserting the CS signal (active
low). Refer to Figure 3-2.
The CS signal must be continuously active for the duration of the SPI transaction
(command, response and data). The only exception is card-programming time. At this time
the host can de-assert the CS signal without affecting the programming process.
The bi-directional CMD and DAT lines are replaced by unidirectional dataIn and dataOut
signals. This eliminates the ability to execute commands while data is being read or written
which prevents sequential multi read/write operations. The Stop Transmission command
can be sent during data read. In the multi block write operation a Stop Transmission token
is sent as the first byte of the data block.
The following sections provide valuable information about the electrical interface.
3.4.1 Power Up
The power-up of the SD Card bus is handled locally, in each SD Card and in the bus
master.
Figure 3-5 Power-up Diagram
Supply Voltage
V
max
DD
Bus master supply voltage
V
min
DD
Power-up
Time
Supply Ramp-up
Initialization delay:
the max. of 1 ms,
74 clock cycles
and supply ramp-
Time
Initialization
Sequence
up time
Valid voltage
range for
commands CMD0,
15, 55, and
ACMD41
Timeout value for initialization process = 1 second
ACMD
N
CC
41
ACMD
41
Optional repetitions of ACMD1 until no
cards respond with busy bit set
Logic working level
Valid voltage
range for all
other commands
and memory
access
N
ACMD
CC
41
time
N
CC
CMD2
After power up, including hot insertion (i.e., inserting a card when the bus is operating) the
SD Card enters the idle state. During this state the SD Card ignores all bus transactions
until ACMD41 is received (ACMD command type shall always precede with CMD55).
ACMD41 is a special synchronization command used to negotiate the operation voltage
range and to poll the cards until they are out of their power-up sequence. Besides the
operation voltage profile of the cards, the response to ACMD41 contains a busy flag,
indicating that the card is still working on its power-up procedure and is not ready for
identification. This bit informs the host that the card is not ready. The host has to wait (and
continue to poll the cards, each one on his turn) until this bit is cleared. The maximum
period of power up procedure of single card shall not exceed one second.
Getting individual cards, and the entire SD Card system, out of idle state is up to the
responsibility of the bus master. Since the power up time and the supply ramp up time
depend on application parameters such as the maximum number of SD Card s, the bus
length and the power supply unit, the host must ensure that the power is built up to the
operating level (the same level which will be specified in ACMD41) before ACMD41 is
transmitted.
After power up, the host starts the clock and sends the initializing sequence on the CMD
line. This sequence is a contiguous stream of logical ‘1’s. The sequence length is the
maximum of 1msec, 74 clocks or the supply-ramp-up-time; the additional 10 clocks (over
the 64 clocks after what the card should be ready for communication) is provided to
eliminate power-up synchronization problems.
Every bus master shall have the capability to implement ACMD41 and CMD1. CMD1 will
be used to ask MultiMediaCards to send their operation conditions. In any case the
ACMD41 or the CMD1 shall be send separately to each card accessing it through its own
CMD line.
3.4.2 Bus Operating Conditions
SPI Mode bus operating conditions are identical to SD Card mode bus operating
conditions. Table 3-4 lists the power supply voltages. The CS (chip select) signal timing is
identical to the input signal timing (see Figure 3-8).
Table 3-4 Bus Operating Conditions Summary
Parameter SymbolMinMaxUnitRemark
General
Peak voltage on all lines --- -0.3 VDD + 0.3 V
All Inputs
Input Leakage Current --- -10 10 uA
All Outputs
Output Leakage Current --- -10 10 uA
Power Supply Voltage7
Supply Voltage VDD 2.0 3.6 V CMD0, 15, 55,
V
Supply voltage differentials
, V
SS1
SS2
)
(V
Power-up Time --- --- 250 mS From 0 V to VDD min.
2.7 3.6 V Except CMD0, 15, 55,
DD
--- -0.3 0.3 V
ACMD41 commands
ACMD41 commands
3.4.3 Bus Signal Line Load
The total capacitance, C
capacitance (C
card connected to this line:
C
= C
L
HOST
Where N is the number of connected cards. Requiring the sum of the host and bus
capacitances not to exceed 30 pF for up to 10 cards, and 40 pF for up to 30 cards, the
values in Table 3-4 must not be exceeded.
Bus signal line capacitance CL --- 250 pF fPP < 5 MHz, 21 cards
Bus signal line capacitanceC
Signal card capacitance C
---100pF
L
--- 10 pF
CARD
f
< 20 MHz, 7 cards
PP
Max. signal line inductance------16nHfPP <20 MHz
Pull-up resistance inside card (pin 1) R
10 90 kΩ May be used for card
DAT3
detection
3.4.4 Bus Signal Levels
All signal levels are related to the supply voltage because the bus can have a variable
supply voltage (see Figure 3-6).
Figure 3-6 Bus Signal Levels
V
V
DD
Input
High
Level
V
OH
V
IH
Input
Low
Level
3.4.5 Open-drain Mode Bus Signal Level
To meet the requirements of the JEDEC specification JESD8-1A, the card input and output
voltages are within the specified ranges in Table 3-6 for any V
range.
Table 3-6 Input/Output Voltage
Parameter Symbol Min. Max. Unit Conditions
Output high voltage VOH 0.75*VDD --- V IOH = -100 uA@ VDD (minimum)
Output low voltage VOL --- 0.125*VDD V IOL = 100 uA@ VDD (minimum)
Output
High
Level
Undefined
V
L
Output
V
OL
V
SS
t
Low
Level
of the allowed voltage
DD
Input high voltage VIH 0.625*VDD V
Input low voltage VIL V
8
The total capacitance of CMD and DAT lines will consist of C
connected separately to the SD Card host.