This manual covers the SanDisk MultiMediaCard which was developed by
SanDisk’s Design Center located in Tefen, Israel. The MultiMediaCard
supports version 1.4 of the MultiMediaCard Specification.
CORPORATE HEADQUARTERS
140 Caspian Court
Sunnyvale, CA 94089-1000
408-542-0500
FAX: 408-542-0503
URL: http://www.sandisk.com
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.
The information in this manual is subject to change without notice.
SanDisk Corporation shall not be liable for technical or editorial errors or omissions contained herein; nor for incidental or
consequential damages resulting from the furnishing, performance, or use of this material.
All parts of the SanDisk MultiMediaCard documentation are protected by copyright law and all rights are reserved. This
documentation may not, in whole or in part, be copied, photocopied, reproduced, translated, or reduced to any electronic
medium or machine readable form without prior consent, in writing, from SanDisk Corporation.
SanDisk and the SanDisk logo are registered trademarks 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-00089 Rev 2 4/2000Printed in U.S.A.
Revision History
• Revisions dated before 1/98—initial release and general changes.
• Revision dated 1/98—general editorial changes, manual reorganized, technical changes to reflect support of
MultiMediaCard Specification version 1.3, new timing diagrams added. Pin 6 definition changed in SPI mode from SPI
select to VSS2 (supply voltage ground).
• Revision dated 4/98— changes reflect support of MultiMediaCard Specification version 1.4, updated timing for
Multiple Write with no Busy, updated SPI command class definition, added Error Protection section, changed
operating temperature specification to -25° to 85°C.
• Revision dated 4/28/98—Updated C_SIZE and C_SIZE_MULT field definitions.
• Revision 1 dated 4/99—Added 32 MB MultiMediaCard, general technical and editorial changes, added power up
section.
The SanDisk MultiMediaCard is a very small,
removable flash storage device, designed
specifically for storage applications that put a
premium on small form factor, low power and low
cost. Flash is the ideal storage medium for
portable, battery-powered devices. It features low
power consumption and is non-volatile, requiring
no power to maintain the stored data. It also has a
wide operating range for temperature, shock and
vibration.
The MultiMediaCard is well suited to meet the
needs of small, low power, electronic devices.
With a form factor of 32mm by 24mm and 1.4mm
thick, MultiMediaCards are expected to be used in
a wide variety of portable devices like mobile
phones, pagers and voice recorders. This ultrasmall form factor is part of a new, emerging,
proposed open standard.
To support this wide range of applications, the
MultiMediaCard protocol, a high performance
seven pin serial interface, is designed for
maximum scalability and configurability. A l l
device and interface configuration data (such as
maximum frequency, card identification, etc.) are
stored on the card.
The MultiMediaCard interface allows for easy
integration into any design, regardless of
microprocessor used. For compatibility with
existing controllers, the MultiMediaCard offers,
in addition to the MultiMediaCard interface, an
alternate communication protocol which is based
on the SPI standard.
The MultiMediaCard provides up to 32 million
bytes of memory using SanDisk Flash memory
chips which were designed by SanDisk especially
for use in mass storage applications. In addition to
the mass storage specific flash memory chip, the
MultiMediaCard includes an on-card intelligent
controller which manages interface protocols and
data storage and retrieval, as well as Error
Correction Code (ECC) algorithms, defect
handling and diagnostics, power management and
clock control.
MultiMediaCards are fully compatible with t he
MultiMediaCard standard specification listed
below:
The MultiMediaCard System Specification
Version 1.4
This specification may be obtained from:
MultiMediaCard Association
19672 Stevens Creek Blvd., Suite 404
Cupertino, CA 95014-2465
USA
Phone: 408-253-0441
Fax: 408-253-8811
Email: prophet2@mmca.org
http://www.mmca.org
1.5Functional Description
SanDisk MultiMediaCards contain a high level,
intelligent subsystem as shown in the block
diagram, Figure 1-1. This intelligent
(microprocessor) subsystem provides many
capabilities not found in other types of memory
cards. These capabilities include:
1. Host independence from details of erasing
and programming flash memory.
2. Sophisticated system for managing
defects (analogous to systems found in
magnetic disk drives).
3. Sophisticated system for error recovery
including a powerful error correction code
(ECC).
4.Power management for low power
operation.
1.5.1Flash Technology Independence
The 512 byte sector size of the MultiMediaCard is
the same as that in an IDE magnetic disk drive. To
write or read a sector (or multiple sectors), t he
host computer software simply issues a Read or
Write command to the MultiMediaCard. 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 more and more complex in th e
future. Because the MultiMediaCard 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 MultiMediaCard today will be able
to access future SanDisk MultiMediaCards built
with new flash technology without having to
update or change host software.
1.5.2Defect and Error Management
MultiMediaCards 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. MultiMediaCards 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, MultiMediaCards
replace this bad bit with a spare bit within the
sector header. If necessary, MultiMediaCards
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 MultiMediaCard’s soft error rate
specification is much better than the magnetic
disk drive specification. In the extremely rare
case a read error does occur, MultiMediaCards
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 t h e
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
MultiMediaCards unparalleled reliability.
SanDisk MultiMediaCards have an endurance
specification for each sector of 300,000 writes
(reading a logical sector is unlimited). This is far
beyond what is needed in nearly all applications
of MultiMediaCards. Even very heavy use of t h e
MultiMediaCard in cellular phones, personal
communicators, pagers and voice recorders will use
only a fraction of the total endurance over t h e
typical device’s five year lifetime. For instance,
it would take over 34 years to wear out an area on
the MultiMediaCard on which a file of any size
(from 512 bytes to capacity) was 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.5.4 Wear Leveling
When the host is ready to access t h e
MultiMediaCard and it is in sleep mode, any
command issued to the MultiMediaCard will
cause it to exit sleep and respond.
1.5.7Hot Insertion
Support for hot insertion will be required on th e
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. Please
see connector data sheets for more details. This
approach is similar to that used in PCMCIA to
allow for hot insertion. This applies to both
MultiMediaCard and SPI modes.
1.5.8MultiMediaCard Mode
1.5.8.1MultiMediaCard Standard
Compliance
SanDisk MultiMediaCards do not require or
perform a Wear Level operation.
1.5.5Using the Erase Command
The Erase (sector or group) command provides t he
capability to substantially increase the write
performance of the MultiMediaCard. Once a
sector has been erased using the Erase command, a
write to that sector will be much faster. This is
because a normal write operation includes a
separate sector erase prior to write.
1.5.6Automatic Sleep Mode
A unique feature of the SanDisk MultiMediaCard
(and other SanDisk products) is automatic
entrance and exit from sleep mode. Upon
completion of an operation, the MultiMediaCard
will enter the sleep mode to conserve power if no
further commands are received within 5 msec. Th e
host does not have to take any action for this to
occur. In most systems, the MultiMediaCard is in
sleep mode except when the host is accessing i t ,
thus conserving power.
The MultiMediaCard is fully compliant with
MultiMediaCard Standard Specification V1.4.
The structure of the Card Specific Data (CSD)
register is compliant with CSD structure V1.4.
1.5.8.2Negotiating Operation Conditions
The MultiMediaCard supports the operation
condition verification sequence defined in th e
MultiMediaCard standard specifications. Should
the MultiMediaCard host define an operating
voltage range which is not supported by the
MultiMediaCard 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 t h e
GO_INACTIVE_STATE command.
The MultiMediaCard bus is a single master
(MultiMediaCard host) and multi-slaves (cards)
bus. The host can query the bus and find out how
many cards of which type are currently connected.
The MultiMediaCard’s CID register is preprogrammed with a unique card identification
number which is used during the acquisition and
identification procedure.
In addition, the MultiMediaCard host can read
the card’s CID register using the READ_CID
MultiMediaCard command. The CID register is
programmed during the MultiMediaCard testing
and formatting procedure, on the manufacturing
floor. The MultiMediaCard host can only read
this register and not write to it.
1.5.8.4Card Status
MultiMediaCard status is stored in a 32 bit status
register which is sent as the data field in the card
respond to host commands. 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.
Although the MultiMediaCard memory space is
byte addressable with addresses ranging from 0 to
the last byte, it is not a simple byte array but
divided into several structures.
Memory bytes are grouped into 512 byte blocks
called sectors. Every block can be read, written
and erased individually.
Sectors are grouped into erase groups of 16 or 32
sectors depending on card size. Any combination of
sectors within one group or, any combination of
erase groups can be erased in a single erase
command. A write command implicitly erases th e
memory before writing new data into it. Explicit
WP Group 2
WP Group 1
Erase Group
erase command can be used for pre-erasing of
memory which will speed up the next write
operation.
Erase groups are grouped into Write Protect Groups
(WPG) of 32 erase groups. The write/erase access
to each WPG can be limited individually. A
diagram of the memory structure hierarchy is
shown in Figure 1-2.
The number of various memory structures, for th e
different MultiMediaCards are summarized in
Table 1-3. The last (highest in address) WPG will
be smaller and contain less than 32 erase groups.
The MultiMediaCard supports three read/write
modes as shown in the above figure.
Stream Mode
In stream mode the host reads or writes continues
stream of data. The starting address is specified
in the read/write command and the operation
ends when the host sends a stop transmission
command.
In this mode there is no validity check on th e
transferred data.
The start address for a read operation can be any
random byte address in the valid address space of
the memory card. For a write operation, the start
address must be sector aligned and the data length
must be an integer multiplication of the sector
length.
Single Block Mode
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 which
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 Mode
This mode is similar to the single block mode, but
the host can read/write multiple data blocks (all
have the same length) which will be 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 as well and are identical to t he
single block read/write operations.
1.5.8.7Data Protection in the Flash Card
1.5.8.8Erase
The smallest erasable unit in th e
MultiMediaCard is a sector. In order to speed up
the erase procedure, multiple sectors can be erased
in the same time. The erase operation is divided
into two stages:
Tagging - Selecting the Sectors for Erasing
To facilitate selection, a first command with t he
starting address is followed by a second command
with the final address, and all sectors within this
range will be selected for erase. After a range is
selected, individual sectors (or groups) within
that range can be removed using the UNTAG
command.
Erasing - Starting the Erase Process
The sectors are grouped into erase groups of 16 or 32
sectors. Tagging can address sectors or erase
groups. Either an arbitrary set of sectors within a
single erase group, or an arbitrary selection of
erase groups may be erased at one time, but not
both together. That is, the unit of measure for
determining an erase is either a sector or an erase
group, but if a sector, all selected sectors must l i e
within the same erase group. Tagging and erasing
sectors must follow a strict command sequence.
1.5.8.9Write Protection
The MultiMediaCard erase groups are grouped
into write protection groups. Commands a re
provided for limiting and enabling write and
erase privileges for each group individually. The
current write protect map can be read using t h e
SEND_WRITE_PROT command.
In addition two, permanent and temporary, card
level write protection options are available. Both
can be set using the PROGRAM_CSD command
(see below). The permanent write protect bit, once
set, cannot be cleared. This feature is implemented
in the MultiMediaCard controller firmware and
not with a physical OTP cell.
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, th e
data is corrected prior to transmission to the host.
The content of a MultiMediaCard can be marked
as an original or a copy using the copy bit in th e
CSD register. Once the Copy bit is set (marked as
a copy) it cannot be cleared. The Copy bit of the
MultiMediaCard is programmed (during test and
formatting on the manufacturing floor) as a copy.
The MultiMediaCard can be purchased with th e
copy bit set (copy) or cleared, indicating the card
is a master. This feature is implemented in t he
MultiMediaCard controller firmware and not
with a physical OTP cell.
1.5.8.11The CSD Register
All the configuration information of the
MultiMediaCard is stored in the CSD register.
The MSB bytes of the register contain
manufacturer data and the two least significant
bytes contain the host controlled data—the card
Copy and write protection and the user ECC
register.
1.5.9.2Card Acquisition and Identification
The card acquisition and identification function of
the MultiMediaCard bus is not supported in S PI
mode. The host must know the number of cards
currently connected on the bus. Specific card
selection is done via the CS signal.
1.5.9.3Card Status
In SPI mode only 16 bits (containing the errors
relevant to SPI mode) can be read out of t h e
MultiMediaCard status register.
1.5.9.4Memory Array Partitioning
Memory partitioning in SPI mode is equivalent to
MultiMediaCard mode. All read and write
commands are byte addressable.
1.5.9.5Read and Write Operations
The host can read the CSD register and alter the
host controlled data bytes using the SEND_CSD
and PROGRAM_CSD commands.
1.5.9SPI Mode
The SPI mode is a secondary communication
protocol for MultiMediaCards. This mode is a
subset of the MultiMediaCard protocol, designed
to communicate with an SPI channel, commonly
found in Motorola’s (and lately a few other
vendors’) microcontrollers.
1.5.9.1Negotiating Operating Conditions
The operating condition negotiation function of
the MultiMediaCard bus is not supported in S PI
mode. The host must work within the valid
voltage range (2.7 to 3.6) volts of the card.
In SPI mode, only single block read/write mode i s
supported.
1.5.9.6Data Transfer Rate
Same as for the MultiMediaCard mode when the
card is operating in single block read/write mode.
The MultiMediaCard has seven exposed contacts on one side. (See Figure 2-1.) The host is connected to
the MultiMediaCard using a seven pin connector as shown in the Appendix at the end of this manual.
The ROD is switched on and off by the host
synchronously to the open-drain and push-pull
mode transitions. R
and R
DAT
are pull-up
CMD
resistors protecting the CMD and the DAT line
against bus floating when no card is inserted or
when all card drivers are in a hi-impedance
mode.
R
CMD
CMD
DAT
CLK
C1C2C
3
1 2 3 4 5 6 7
MultiMediaCard
4.2.1Power Protection
Cards can be inserted/removed into/from the bus
without damage. If one of the supply pins (V
VSS) is not connected properly, then the current is
drawn through a data line to supply the card.
DD
or
A constant current source can replace the ROD in
order to achieve a better performance (constant
slopes for the signal rising and falling edges). If
the host does not allow the switchable R
implementation, a fix R
can be used.
CMD
OD
Consequently the maximum operating frequency in
the open drain mode has to be reduced in this case.
Hot Insertion/Removal
Hot insertion and removal are allowed. The
SanDisk MultiMediaCard will not be damaged by
inserting or removing it into the MultiMediaCard
bus even when the power is up.
•The inserted card will be properly reset
also when CLK carries a clock frequency
fPP.
•Data transfer failures induced by
removal/insertion should be detected by
the bus master using the CRC codes which
suffix every bus transaction.
Every cards output must also be able to withstand
short cuts to either supply.
If the hot insertion feature is implemented in the
host, the host has to withstand a shortcut
between V
DD
and V
without damage.
SS
4.2.2Programmable Card Output Driver
This option, defined in chapter 6 of th e
MultiMediaCard standard, is not implemented in
the SanDisk MultiMediaCard.
The MultiMediaCard SPI interface is compatible
with SPI hosts available on the market. As any
other SPI device the MultiMediaCard SPI
channel consists of the following 4 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, which is
implemented in the MultiMediaCard as well, is
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. The
MultiMediaCard uses a subset of t h e
MultiMediaCard protocol and command set.
Power
Supply
The MultiMediaCard identification and
addressing algorithms are replaced by a
hardware Chip Select (CS) signal. There are no
broadcast commands. A card (slave) is selected,
for every command, by asserting (active low) t h e
CS signal (see Figure 4-2).
The CS signal must be continuously active for th e
duration of the SPI transaction (command,
response and data). The only exception is card
programming time. At this time the host can deassert the CS signal without affecting t he
programming process.
The bidirectional CMD and DAT lines are
replaced by unidirectional dataIn and dataOut
signals. This eliminates the ability of executing
commands while data is being read or written and,
therefore, eliminates the sequential and multi
block read/write operations. Only single block
read/write is supported by the SPI channel.
The power up of the MultiMediaCard bus is handled locally in each MultiMediaCard and in the bus
master.
After power-up (including hot insertion, that is,
inserting a card when the bus i s operating), th e
MultiMediaCard enters the Idle State. During
this state, the MultiMediaCard ignores all bus
transactions until CMD1 is received.
CMD1 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 CMD1 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 a t
least one card is not ready. The host has to wait
(and continue to poll the cards) until this bit is
cleared.
MultiMediaCard Product Manual
Getting individual cards, as well as the whole
MultiMediaCard system, out of Idle State is up to
the responsibility of the bus master. Since t he
power-up time and the supply ramp up time
depend on application parameters such as th e
maximum number of MultiMediaCards, 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
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
ones. The sequence length is the maximum of one
msec, 74 clocks or the supply ramp up time. The
additional ten clocks (beyond the 64 clocks after
which the card should be ready for
communication) are provided to eliminate powerup synchronization problems.
CMD1) before CMD1 is transmitted.
4.4.2Bus Operating Conditions
SPI Mode bus operating conditions are identical to MultiMediaCard Mode bus operating conditions. The
CS (chip select) signal timing is identical to the input signal timing. (See Figure 4-5.)
General
ParameterSymbolMin.Max.UnitRemark
Peak voltage on all lines-0.53.6V
All Inputs
Input Leakage Current-1010
µA
All Outputs
Output Leakage Current-1010
µA
Power supply voltage
ParameterSymbolMin.Max.UnitRemark
Supply voltageV
Supply voltage differentials (V
SS1
, V
)-0.50.5V
SS2
DD
2.03.6V
The current consumption of any card during the power-up procedure must not exceed 10 mA.
The total capacitance CL of each line of the MultiMediaCard bus is the sum of the bus master
capacitance CHOST, the bus capacitance CBUS itself and the capacitance CCARD of each card
connected to this line:
CL = CHOST + CBUS + N∗CCARD
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 following values must not be exceeded:
ParameterSymbolMin.Max.UnitRemark
Pull-up resistanceRCMD
RDAT
Bus signal line capacitanceCL250pF
50100
kΩ
To prevent bus floating
fPP # 5 MHz,
30 cards
Bus signal line capacitanceCL100pF
Single card capacitanceCCARD7pF
Maximum signal line inductance16nH
4.4.3Bus Signal Levels
As the bus can be supplied with a variable supply voltage, all signal levels are related to the supply
voltage.
The input levels are identical with the push-pull mode bus signal levels.
4.4.5Push-pull Mode Bus Signal Level
To meet the requirements of the JEDEC specification JESD8-1A, the card input and output voltages
shall be within the following specified ranges for any VDD of the allowed voltage range:
ParameterSymbolMin.Max.UnitConditions
Output HIGH voltageVOH
Output LOW voltageVOL
Input HIGH voltageVIH
0.75∗VDD
0.625∗VDD
0.125∗VDD
VDD + 0.3V
V
V
V
IOH = -100 µA
IOH=-100 µA
@V
(min.)
DD
IOL=100 µA
@V
(min.)
DD
Input LOW voltageVILVSS-0.3
4.4.6Bus Timing
Clock
Input
Output
Note:Data in the shaded areas is not valid.
0.25∗VDD
T
PP
t
THL
t
WL
t
TLH
t
ISU
t
OSU
t
WH
t
IH
t
OH
V
V
IH
V
IL
V
IH
V
IL
V
O
V
OL
Figure 4-5 Timing Diagram Data Input/Output Referenced to Clock
ParameterSymbolMin.Max.UnitRemark
Clock CLK (All values are referred to min. (VIH) and max. (VIL)
Clock Frequency Data Transfer Mode
(PP)
f
PP
020MHzCL ≤ 100 pF
(10 cards)
Clock Frequency Identification Mode
(OD)
Clock Low Timet
Clock High Timet
Clock Rise Timet
Clock Fall Timet
Clock Low Timet
Clock High Timet
Clock Rise Timet
Clock Fall Timet
Inputs CMD, DAT (referenced to CLK)
Input set-up timet
Input hold timet
Outputs CMD, DAT (referenced to CLK)
Output set-up timet
Output hold timet
f
OD
WL
WH
TLH
THL
WL
WH
TLH
THL
ISU
OSU
OH
0400kHzCL ≤ 250 pF
(30 cards)
10nsCL ≤ 100 pF
(10 cards)
10nsCL ≤ 100 pF
(10 cards)
10nsCL ≤ 100 pF
(10 cards)
10nsCL ≤ 100 pF
(10 cards)
50nsCL ≤ 250 pF
(30 cards)
50nsCL ≤ 250 pF
(30 cards)
50nsCL ≤ 250 pF
(30 cards)
50nsCL ≤ 250 pF
(30 cards)
3ns
IH
3ns
5ns
5ns
4.5MultiMediaCard Registers
There is a set of six registers within the card interface. The OCR, CID and CSD registers carry the card
configuration information. The RCA register holds the card relative communication address for th e
current session. The DSR register is not implemented in the SanDisk MultiMediaCard.
4.5.1Operating Conditions Register (OCR)
The 32-bit operation conditions register stores the VDD voltage profile of the card. The
MultiMediaCard is capable of executing the voltage recognition procedure (CMD1) with any standard
MultiMediaCard host using operating voltages form 2 to 3.6 Volts.
Accessing the data in the memory array, however, requires 2.7 to 3.6 Volts. The OCR shows the voltage
range in which the card data can be accessed. The structure of the OCR register is described in Table 4-4.