emmc can't identify on DM385 kernel

Zhilin Cao

Other Parts Discussed in Thread: DM385, CSD

Hi,

We use appro RDK 3.5.0 and have a 16GB Tohiba emmc, we can boot up from emmc and uboot can read and write this emmc successful, but kernel can't identify this emmc, it return timeout when send command to emmc, it seems not generate mmc irq, but same kernel binary works fine with Appro DM385 IPNC and it can identify SD card. They are only one difference: Appro DM385 IPNC use SD card, our hardware use emmc, they both use SD1 interface. I trace this, but can't get any clue about this.

Thanks

over 12 years ago

0 Pavel Botev over 12 years ago

TI__Guru**** 170625 points

Hi Zhilin,

For DM814x eMMC/eSD, the maximum size for booting is 2GB, with some exceptions.

In some cases eMMC can be more than 2GB capacity. Refer to the below e2e thread, in which our DM814x ROM Code expert, Madans, explain how this higher eMMC capacity (4GB, 8GB) can be achieved:
http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/716/t/151914.aspx

Also, one customer comments that eMMC 4GB from Sandisk fit the requirements.
http://processors.wiki.ti.com/index.php/AM387x_/_C6A814x_Schematic_Review_Checklist
3. MMC/SD. User should please note the following: a. Centaurus has 3 instances of MMC/SD/SDIO controller (suffix 0,1 or 2). Booting is supported from MMC/SD/SDIO1 only b. Centaurus ROM is incompatible with most eMMC devices which are >2GB. Sandisk makes a 4GB device which IS compatible with Centaurus ROM.

I can not say for sure about DM385, but I suspect it is similar with DM814x.

BR

Pavel

0 Zhilin Cao over 12 years ago in reply to Pavel Botev

Prodigy 40 points

I have fixed this, it is caused by kernel only supporting EXT_CSD revision 4.41, but my emmc is 4.5.

Processors

Processors forum

emmc can't identify on DM385 kernel