Emmc Dl Command

The multimedia card high-speed/SDIO (MMC/SDIO) host controller provides an interface between a local host (LH) such as a microprocessor unit (MPU) or digital signal processor (DSP) and either MMC, SD® memory cards, or SDIO cards and handles MMC/SDIO transactions with minimal LH intervention. Command operates in two modes, open-drain for initialization and push-pull for fast command transfer. Now, eMMC DL Tool will flash the firmware on your Android Device. Find any firmware, ever released by Samsung. Uncha lamba kad 3d song download mp3. These erase commands are not recommended for secure ly removing customer data.

Multiple Link for eMMC DL Tool V5.2.0 Download

eMMCDL Tool Specification and Features

!! Important !!

1. Device charges 40%-45% minimum.
2. Make a backup of your Qualcomm android tab or mobile all data.
3. Using eMMCDL tools - Make any mistake bricked your tab-phone.
With this in mind:
Users are also advised to frequently visit the eMMC DL Tool official website or Foneric, Inc developer site to view and download tool the new eMMCDL Flash Tool V5.2.0 / eMMCDL tools file. It is also requested for the users to keep them updated with the latest changes in the Qualcomm-chip tool.

You might also be interested page in:

Overview¶

The SD/SDIO/MMC driver currently supports SD memory, SDIO cards, and eMMC chips. This is a protocol level driver built on top of SDMMC and SD SPI host drivers.

SDMMC and SD SPI host drivers (driver/include/driver/sdmmc_host.h) provide API functions for:

• Sending commands to slave devices

• Sending and receiving data

• Handling error conditions within the bus

For functions used to initialize and configure:

Combo (memory + IO) cards¶

The driver does not support SD combo cards. Combo cards are treated as IO cards.

Thread safety¶

Most applications need to use the protocol layer only in one task. For this reason, the protocol layer does not implement any kind of locking on the sdmmc_card_t structure, or when accessing SDMMC or SD SPI host drivers. Such locking is usually implemented on a higher layer, e.g., in the filesystem driver.

• SD SPI host, see SD SPI Host API

The SDMMC protocol layer described in this document handles the specifics of the SD protocol, such as the card initialization and data transfer commands.

The protocol layer works with the host via the sdmmc_host_t structure. This structure contains pointers to various functions of the host.

Application Example¶

An example which combines the SDMMC driver with the FATFS library is provided in the storage/sd_card directory of ESP-IDF examples. This example initializes the card, then writes and reads data from it using POSIX and C library APIs. See README.md file in the example directory for more information.

Protocol layer API¶

The protocol layer is given the sdmmc_host_t structure. This structure describes the SD/MMC host driver, lists its capabilities, and provides pointers to functions of the driver. The protocol layer stores card-specific information in the sdmmc_card_t structure. When sending commands to the SD/MMC host driver, the protocol layer uses the sdmmc_command_t structure to describe the command, arguments, expected return values, and data to transfer if there is any.

Using API with SD memory cards¶

1. To initialize the host, call the host driver functions, e.g., sdmmc_host_init(), sdmmc_host_init_slot().

2. To initialize the card, call sdmmc_card_init() and pass to it the parameters host - the host driver information, and card - a pointer to the structure sdmmc_card_t which will be filled with information about the card when the function completes.

3. To read and write sectors of the card, use sdmmc_read_sectors() and sdmmc_write_sectors() respectively and pass to it the parameter card - a pointer to the card information structure.

4. If the card is not used anymore, call the host driver function - e.g., sdmmc_host_deinit() - to disable the host peripheral and free the resources allocated by the driver.

Using API with eMMC chips¶

From the protocol layer's perspective, eMMC memory chips behave exactly like SD memory cards. Even though eMMCs are chips and do not have a card form factor, the terminology for SD cards can still be applied to eMMC due to the similarity of the protocol (sdmmc_card_t, sdmmc_card_init). Note that eMMC chips cannot be used over SPI, which makes them incompatible with the SD SPI host driver.

To initialize eMMC memory and perform read/write operations, follow the steps listed for SD cards in the previous section.

Using API with SDIO cards¶

Initialization and the probing process is the same as with SD memory cards. The only difference is in data transfer commands in SDIO mode.

During the card initialization and probing, performed with sdmmc_card_init(), the driver only configures the following registers of the IO card:

1. The IO portion of the card is reset by setting RES bit in the I/O Abort (0x06) register.

2. If 4-line mode is enabled in host and slot configuration, the driver attempts to set the Bus width field in the Bus Interface Control (0x07) register. If setting the filed is successful, which means that the slave supports 4-line mode, the host is also switched to 4-line mode.

3. If high-speed mode is enabled in the host configuration, the SHS bit is set in the High Speed (0x13) register.

In particular, the driver does not set any bits in (1) I/O Enable and Int Enable registers, (2) I/O block sizes, etc. Applications can set them by calling sdmmc_io_write_byte().

For card configuration and data transfer, choose the pair of functions relevant to your case from the table below.

SDIO interrupts can be enabled by the application using the function sdmmc_io_enable_int(). When using SDIO in 1-line mode, the D1 line also needs to be connected to use SDIO interrupts.

If you want the application to wait until the SDIO interrupt occurs, use sdmmc_io_wait_int().

There is a component ESSL (ESP Serial Slave Link) to use if you are communicating with an ESP32SDIO slave. See ESP Serial Slave Link and example peripherals/sdio/host.

API Reference¶

Functions¶

Probe and initialize SD/MMC card using given host

Only SD cards (SDSC and SDHC/SDXC) are supported now. Support for MMC/eMMC cards will be added later.

• ESP_OK on success

• One of the error codes from SDMMC host controller

• host: pointer to structure defining host controller

• out_card: pointer to structure which will receive information about the card when the function completes

Print information about the card to a stream.

• stream: stream obtained using fopen or fdopen

• card: card information structure initialized using sdmmc_card_init

Write given number of sectors to SD/MMC card

• ESP_OK on success

• One of the error codes from SDMMC host controller

• card: pointer to card information structure previously initialized using sdmmc_card_init

• src: pointer to data buffer to read data from; data size must be equal to sector_count * card->csd.sector_size

• start_sector: sector where to start writing

• sector_count: number of sectors to write

Write given number of sectors to SD/MMC card

• ESP_OK on success

• One of the error codes from SDMMC host controller

• card: pointer to card information structure previously initialized using sdmmc_card_init

• dst: pointer to data buffer to write into; buffer size must be at least sector_count * card->csd.sector_size

• start_sector: sector where to start reading

• sector_count: number of sectors to read

Read one byte from an SDIO card using IO_RW_DIRECT (CMD52)

• ESP_OK on success

• One of the error codes from SDMMC host controller

• card: pointer to card information structure previously initialized using sdmmc_card_init

• function: IO function number

• reg: byte address within IO function

• [out]out_byte: output, receives the value read from the card

Write one byte to an SDIO card using IO_RW_DIRECT (CMD52)

• ESP_OK on success

• One of the error codes from SDMMC host controller

• card: pointer to card information structure previously initialized using sdmmc_card_init

• function: IO function number

• reg: byte address within IO function

• in_byte: value to be written

• [out]out_byte: if not NULL, receives new byte value read from the card (read-after-write).

Read multiple bytes from an SDIO card using IO_RW_EXTENDED (CMD53)

This function performs read operation using CMD53 in byte mode. For block mode, see sdmmc_io_read_blocks.

• ESP_OK on success

• ESP_ERR_INVALID_SIZE if size exceeds 512 bytes

• One of the error codes from SDMMC host controller

Emmcdl Command

• card: pointer to card information structure previously initialized using sdmmc_card_init

• function: IO function number

• addr: byte address within IO function where reading starts

• dst: buffer which receives the data read from card

• size: number of bytes to read

Write multiple bytes to an SDIO card using IO_RW_EXTENDED (CMD53)

This function performs write operation using CMD53 in byte mode. For block mode, see sdmmc_io_write_blocks.

• ESP_OK on success

• ESP_ERR_INVALID_SIZE if size exceeds 512 bytes

• One of the error codes from SDMMC host controller

• card: pointer to card information structure previously initialized using sdmmc_card_init

• function: IO function number

• addr: byte address within IO function where writing starts

• src: data to be written

• size: number of bytes to write

Read blocks of data from an SDIO card using IO_RW_EXTENDED (CMD53)

This function performs read operation using CMD53 in block mode. For byte mode, see sdmmc_io_read_bytes.

• ESP_OK on success

• ESP_ERR_INVALID_SIZE if size is not divisible by 512 bytes

• One of the error codes from SDMMC host controller

Emmcdl Command

• card: pointer to card information structure previously initialized using sdmmc_card_init

• function: IO function number

• addr: byte address within IO function where writing starts

• dst: buffer which receives the data read from card

• size: number of bytes to read, must be divisible by the card block size.

Write blocks of data to an SDIO card using IO_RW_EXTENDED (CMD53)

This function performs write operation using CMD53 in block mode. For byte mode, see sdmmc_io_write_bytes.

• ESP_OK on success

• ESP_ERR_INVALID_SIZE if size is not divisible by 512 bytes

• One of the error codes from SDMMC host controller

• card: pointer to card information structure previously initialized using sdmmc_card_init

• function: IO function number

• addr: byte address within IO function where writing starts

• src: data to be written

• size: number of bytes to read, must be divisible by the card block size.

Enable SDIO interrupt in the SDMMC host

• ESP_OK on success

• ESP_ERR_NOT_SUPPORTED if the host controller does not support IO interrupts

• card: pointer to card information structure previously initialized using sdmmc_card_init

Block until an SDIO interrupt is received

Slave uses D1 line to signal interrupt condition to the host. This function can be used to wait for the interrupt.

• ESP_OK if the interrupt is received

• ESP_ERR_NOT_SUPPORTED if the host controller does not support IO interrupts

• ESP_ERR_TIMEOUT if the interrupt does not happen in timeout_ticks

• card: pointer to card information structure previously initialized using sdmmc_card_init

• timeout_ticks: time to wait for the interrupt, in RTOS ticks

Get the data of CIS region of a SDIO card.

You may provide a buffer not sufficient to store all the CIS data. In this case, this functions store as much data into your buffer as possible. Also, this function will try to get and return the size required for you.

• ESP_OK: on success

• ESP_ERR_INVALID_RESPONSE: if the card does not (correctly) support CIS.

• ESP_ERR_INVALID_SIZE: CIS_CODE_END found, but buffer_size is less than required size, which is stored in the inout_cis_size then.

• ESP_ERR_NOT_FOUND: if the CIS_CODE_END not found. Increase input value of inout_cis_size or set it to 0, if you still want to search for the end; output value of inout_cis_size is invalid in this case.

• and other error code return from sdmmc_io_read_bytes

• card: pointer to card information structure previously initialized using sdmmc_card_init

• out_buffer: Output buffer of the CIS data

• buffer_size: Size of the buffer.

• inout_cis_size: Mandatory, pointer to a size, input and output.

  • input: Limitation of maximum searching range, should be 0 or larger than buffer_size. The function searches for CIS_CODE_END until this range. Set to 0 to search infinitely.

  • output: The size required to store all the CIS data, if CIS_CODE_END is found.

Parse and print the CIS information of a SDIO card.

Not all the CIS codes and all kinds of tuples are supported. If you see some unresolved code, you can add the parsing of these code in sdmmc_io.c and contribute to the IDF through the Github repository.

• ESP_OK: on success

• ESP_ERR_NOT_SUPPORTED: if the value from the card is not supported to be parsed.

• ESP_ERR_INVALID_SIZE: if the CIS size fields are not correct.

• buffer: Buffer to parse

• buffer_size: Size of the buffer.

• fp: File pointer to print to, set to NULL to print to stdout.

Structures¶

Decoded values from SD card Card Specific Data register

Public Members

CSD structure format

MMC version (for CID format)

total number of sectors

sector size in bytes

block length for reads

Card Command Class for SD

Max transfer speed

Decoded values from SD card Card IDentification register

Public Members

manufacturer identification number

OEM/product identification number

product name (MMC v1 has the longest)

product revision

product serial number

manufacturing date

Decoded values from SD Configuration Register

Public Members

SD Physical layer specification version, reported by card

bus widths supported by card: BIT(0) — 1-bit bus, BIT(2) — 4-bit bus

Decoded values of Extended Card Specific Data

Public Members

Power class used by the card

SD SWITCH_FUNC response buffer

Public Members

response data

SD/MMC command information

Emmc Dl Commands

Public Members

SD or MMC command index

SD/MMC command argument

response buffer

buffer to send or read into

length of data buffer

block length

see below

error returned from transfer

response timeout, in milliseconds

SD/MMC Host description

This structure defines properties of SD/MMC host and functions of SD/MMC host which can be used by upper layers.

Public Members

flags defining host properties

slot number, to be passed to host functions

max frequency supported by the host

I/O voltage used by the controller (voltage switching is not supported)

Host function to initialize the driver

host function to set bus width

host function to get bus width

host function to set DDR mode

host function to set card clock frequency

host function to do a transaction

host function to deinitialize the driver

host function to deinitialize the driver, called with the slot

Host function to enable SDIO interrupt line

Host function to wait for SDIO interrupt line to be active

timeout, in milliseconds, of a single command. Set to 0 to use the default value.

SD/MMC card information structure

Public Members

Host with which the card is associated

eMMCDL Tool Specification and Features

!! Important !!

1. Device charges 40%-45% minimum.
2. Make a backup of your Qualcomm android tab or mobile all data.
3. Using eMMCDL tools - Make any mistake bricked your tab-phone.
With this in mind:
Users are also advised to frequently visit the eMMC DL Tool official website or Foneric, Inc developer site to view and download tool the new eMMCDL Flash Tool V5.2.0 / eMMCDL tools file. It is also requested for the users to keep them updated with the latest changes in the Qualcomm-chip tool.

You might also be interested page in:

Overview¶

The SD/SDIO/MMC driver currently supports SD memory, SDIO cards, and eMMC chips. This is a protocol level driver built on top of SDMMC and SD SPI host drivers.

SDMMC and SD SPI host drivers (driver/include/driver/sdmmc_host.h) provide API functions for:

• Sending commands to slave devices

• Sending and receiving data

• Handling error conditions within the bus

For functions used to initialize and configure:

Combo (memory + IO) cards¶

The driver does not support SD combo cards. Combo cards are treated as IO cards.

Thread safety¶

Most applications need to use the protocol layer only in one task. For this reason, the protocol layer does not implement any kind of locking on the sdmmc_card_t structure, or when accessing SDMMC or SD SPI host drivers. Such locking is usually implemented on a higher layer, e.g., in the filesystem driver.

• SD SPI host, see SD SPI Host API

The SDMMC protocol layer described in this document handles the specifics of the SD protocol, such as the card initialization and data transfer commands.

The protocol layer works with the host via the sdmmc_host_t structure. This structure contains pointers to various functions of the host.

Application Example¶

An example which combines the SDMMC driver with the FATFS library is provided in the storage/sd_card directory of ESP-IDF examples. This example initializes the card, then writes and reads data from it using POSIX and C library APIs. See README.md file in the example directory for more information.

Protocol layer API¶

The protocol layer is given the sdmmc_host_t structure. This structure describes the SD/MMC host driver, lists its capabilities, and provides pointers to functions of the driver. The protocol layer stores card-specific information in the sdmmc_card_t structure. When sending commands to the SD/MMC host driver, the protocol layer uses the sdmmc_command_t structure to describe the command, arguments, expected return values, and data to transfer if there is any.

Using API with SD memory cards¶

1. To initialize the host, call the host driver functions, e.g., sdmmc_host_init(), sdmmc_host_init_slot().

2. To initialize the card, call sdmmc_card_init() and pass to it the parameters host - the host driver information, and card - a pointer to the structure sdmmc_card_t which will be filled with information about the card when the function completes.

3. To read and write sectors of the card, use sdmmc_read_sectors() and sdmmc_write_sectors() respectively and pass to it the parameter card - a pointer to the card information structure.

4. If the card is not used anymore, call the host driver function - e.g., sdmmc_host_deinit() - to disable the host peripheral and free the resources allocated by the driver.

Using API with eMMC chips¶

From the protocol layer's perspective, eMMC memory chips behave exactly like SD memory cards. Even though eMMCs are chips and do not have a card form factor, the terminology for SD cards can still be applied to eMMC due to the similarity of the protocol (sdmmc_card_t, sdmmc_card_init). Note that eMMC chips cannot be used over SPI, which makes them incompatible with the SD SPI host driver.

To initialize eMMC memory and perform read/write operations, follow the steps listed for SD cards in the previous section.

Using API with SDIO cards¶

Initialization and the probing process is the same as with SD memory cards. The only difference is in data transfer commands in SDIO mode.

During the card initialization and probing, performed with sdmmc_card_init(), the driver only configures the following registers of the IO card:

1. The IO portion of the card is reset by setting RES bit in the I/O Abort (0x06) register.

2. If 4-line mode is enabled in host and slot configuration, the driver attempts to set the Bus width field in the Bus Interface Control (0x07) register. If setting the filed is successful, which means that the slave supports 4-line mode, the host is also switched to 4-line mode.

3. If high-speed mode is enabled in the host configuration, the SHS bit is set in the High Speed (0x13) register.

In particular, the driver does not set any bits in (1) I/O Enable and Int Enable registers, (2) I/O block sizes, etc. Applications can set them by calling sdmmc_io_write_byte().

For card configuration and data transfer, choose the pair of functions relevant to your case from the table below.

SDIO interrupts can be enabled by the application using the function sdmmc_io_enable_int(). When using SDIO in 1-line mode, the D1 line also needs to be connected to use SDIO interrupts.

If you want the application to wait until the SDIO interrupt occurs, use sdmmc_io_wait_int().

There is a component ESSL (ESP Serial Slave Link) to use if you are communicating with an ESP32SDIO slave. See ESP Serial Slave Link and example peripherals/sdio/host.

API Reference¶

Functions¶

Probe and initialize SD/MMC card using given host

Only SD cards (SDSC and SDHC/SDXC) are supported now. Support for MMC/eMMC cards will be added later.

• ESP_OK on success

• One of the error codes from SDMMC host controller

• host: pointer to structure defining host controller

• out_card: pointer to structure which will receive information about the card when the function completes

Print information about the card to a stream.

• stream: stream obtained using fopen or fdopen

• card: card information structure initialized using sdmmc_card_init

Write given number of sectors to SD/MMC card

• ESP_OK on success

• One of the error codes from SDMMC host controller

• card: pointer to card information structure previously initialized using sdmmc_card_init

• src: pointer to data buffer to read data from; data size must be equal to sector_count * card->csd.sector_size

• start_sector: sector where to start writing

• sector_count: number of sectors to write

Write given number of sectors to SD/MMC card

• ESP_OK on success

• One of the error codes from SDMMC host controller

• card: pointer to card information structure previously initialized using sdmmc_card_init

• dst: pointer to data buffer to write into; buffer size must be at least sector_count * card->csd.sector_size

• start_sector: sector where to start reading

• sector_count: number of sectors to read

Read one byte from an SDIO card using IO_RW_DIRECT (CMD52)

• ESP_OK on success

• One of the error codes from SDMMC host controller

• card: pointer to card information structure previously initialized using sdmmc_card_init

• function: IO function number

• reg: byte address within IO function

• [out]out_byte: output, receives the value read from the card

Write one byte to an SDIO card using IO_RW_DIRECT (CMD52)

• ESP_OK on success

• One of the error codes from SDMMC host controller

• card: pointer to card information structure previously initialized using sdmmc_card_init

• function: IO function number

• reg: byte address within IO function

• in_byte: value to be written

• [out]out_byte: if not NULL, receives new byte value read from the card (read-after-write).

Read multiple bytes from an SDIO card using IO_RW_EXTENDED (CMD53)

This function performs read operation using CMD53 in byte mode. For block mode, see sdmmc_io_read_blocks.

• ESP_OK on success

• ESP_ERR_INVALID_SIZE if size exceeds 512 bytes

• One of the error codes from SDMMC host controller

Emmcdl Command

• card: pointer to card information structure previously initialized using sdmmc_card_init

• function: IO function number

• addr: byte address within IO function where reading starts

• dst: buffer which receives the data read from card

• size: number of bytes to read

Write multiple bytes to an SDIO card using IO_RW_EXTENDED (CMD53)

This function performs write operation using CMD53 in byte mode. For block mode, see sdmmc_io_write_blocks.

• ESP_OK on success

• ESP_ERR_INVALID_SIZE if size exceeds 512 bytes

• One of the error codes from SDMMC host controller

• card: pointer to card information structure previously initialized using sdmmc_card_init

• function: IO function number

• addr: byte address within IO function where writing starts

• src: data to be written

• size: number of bytes to write

Read blocks of data from an SDIO card using IO_RW_EXTENDED (CMD53)

This function performs read operation using CMD53 in block mode. For byte mode, see sdmmc_io_read_bytes.

• ESP_OK on success

• ESP_ERR_INVALID_SIZE if size is not divisible by 512 bytes

• One of the error codes from SDMMC host controller

Emmcdl Command

• card: pointer to card information structure previously initialized using sdmmc_card_init

• function: IO function number

• addr: byte address within IO function where writing starts

• dst: buffer which receives the data read from card

• size: number of bytes to read, must be divisible by the card block size.

Write blocks of data to an SDIO card using IO_RW_EXTENDED (CMD53)

This function performs write operation using CMD53 in block mode. For byte mode, see sdmmc_io_write_bytes.

• ESP_OK on success

• ESP_ERR_INVALID_SIZE if size is not divisible by 512 bytes

• One of the error codes from SDMMC host controller

• card: pointer to card information structure previously initialized using sdmmc_card_init

• function: IO function number

• addr: byte address within IO function where writing starts

• src: data to be written

• size: number of bytes to read, must be divisible by the card block size.

Enable SDIO interrupt in the SDMMC host

• ESP_OK on success

• ESP_ERR_NOT_SUPPORTED if the host controller does not support IO interrupts

• card: pointer to card information structure previously initialized using sdmmc_card_init

Block until an SDIO interrupt is received

Slave uses D1 line to signal interrupt condition to the host. This function can be used to wait for the interrupt.

• ESP_OK if the interrupt is received

• ESP_ERR_NOT_SUPPORTED if the host controller does not support IO interrupts

• ESP_ERR_TIMEOUT if the interrupt does not happen in timeout_ticks

• card: pointer to card information structure previously initialized using sdmmc_card_init

• timeout_ticks: time to wait for the interrupt, in RTOS ticks

Get the data of CIS region of a SDIO card.

You may provide a buffer not sufficient to store all the CIS data. In this case, this functions store as much data into your buffer as possible. Also, this function will try to get and return the size required for you.

• ESP_OK: on success

• ESP_ERR_INVALID_RESPONSE: if the card does not (correctly) support CIS.

• ESP_ERR_INVALID_SIZE: CIS_CODE_END found, but buffer_size is less than required size, which is stored in the inout_cis_size then.

• ESP_ERR_NOT_FOUND: if the CIS_CODE_END not found. Increase input value of inout_cis_size or set it to 0, if you still want to search for the end; output value of inout_cis_size is invalid in this case.

• and other error code return from sdmmc_io_read_bytes

• card: pointer to card information structure previously initialized using sdmmc_card_init

• out_buffer: Output buffer of the CIS data

• buffer_size: Size of the buffer.

• inout_cis_size: Mandatory, pointer to a size, input and output.

  • input: Limitation of maximum searching range, should be 0 or larger than buffer_size. The function searches for CIS_CODE_END until this range. Set to 0 to search infinitely.

  • output: The size required to store all the CIS data, if CIS_CODE_END is found.

Parse and print the CIS information of a SDIO card.

Not all the CIS codes and all kinds of tuples are supported. If you see some unresolved code, you can add the parsing of these code in sdmmc_io.c and contribute to the IDF through the Github repository.

• ESP_OK: on success

• ESP_ERR_NOT_SUPPORTED: if the value from the card is not supported to be parsed.

• ESP_ERR_INVALID_SIZE: if the CIS size fields are not correct.

• buffer: Buffer to parse

• buffer_size: Size of the buffer.

• fp: File pointer to print to, set to NULL to print to stdout.

Structures¶

Decoded values from SD card Card Specific Data register

Public Members

CSD structure format

MMC version (for CID format)

total number of sectors

sector size in bytes

block length for reads

Card Command Class for SD

Max transfer speed

Decoded values from SD card Card IDentification register

Public Members

manufacturer identification number

OEM/product identification number

product name (MMC v1 has the longest)

product revision

product serial number

manufacturing date

Decoded values from SD Configuration Register

Public Members

SD Physical layer specification version, reported by card

bus widths supported by card: BIT(0) — 1-bit bus, BIT(2) — 4-bit bus

Decoded values of Extended Card Specific Data

Public Members

Power class used by the card

SD SWITCH_FUNC response buffer

Public Members

response data

SD/MMC command information

Emmc Dl Commands

Public Members

SD or MMC command index

SD/MMC command argument

response buffer

buffer to send or read into

length of data buffer

block length

see below

error returned from transfer

response timeout, in milliseconds

SD/MMC Host description

This structure defines properties of SD/MMC host and functions of SD/MMC host which can be used by upper layers.

Public Members

flags defining host properties

slot number, to be passed to host functions

max frequency supported by the host

I/O voltage used by the controller (voltage switching is not supported)

Host function to initialize the driver

host function to set bus width

host function to get bus width

host function to set DDR mode

host function to set card clock frequency

host function to do a transaction

host function to deinitialize the driver

host function to deinitialize the driver, called with the slot

Host function to enable SDIO interrupt line

Host function to wait for SDIO interrupt line to be active

timeout, in milliseconds, of a single command. Set to 0 to use the default value.

SD/MMC card information structure

Public Members

Host with which the card is associated

OCR (Operation Conditions Register) value

decoded CID (Card IDentification) register value

raw CID of MMC card to be decoded after the CSD is fetched in the data transfer mode

Emmcdl Command Download

decoded CSD (Card-Specific Data) register value

decoded SCR (SD card Configuration Register) value

decoded EXT_CSD (Extended Card Specific Data) register value

RCA (Relative Card Address)

Maximum frequency, in kHz, supported by the card

Bit indicates if the card is a memory card

Emmc Command Queue

Bit indicates if the card is an IO card

Bit indicates if the card is MMC

If is_sdio is 1, contains the number of IO functions on the card

log2(bus width supported by card)

Card supports DDR mode

Reserved for future expansion

Macros¶

host supports 1-line SD and MMC protocol

host supports 4-line SD and MMC protocol

host supports 8-line MMC protocol

Emmc Pdf

host supports SPI protocol

host supports DDR mode for SD/MMC

host deinit function called with the slot argument

SD/MMC Default speed (limited by clock divider)

Emmc Layout

SD High speed (limited by clock divider)

SD/MMC probing speed

MMC 52MHz speed

MMC 26MHz speed

Type Definitions¶

SD/MMC command response buffer