• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 524 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DM368 MMC1 does not work

Steve Sun71571
Prodigy 20 points

Hi all,

   I am debugging on DM368 with an extend board for MMC1.  I can mount MMC1 on dm365, both MMC0 and MMC1 can work properly. However , on dm368, MMC1 cannot work. I tried several sizes of SD card, 64M, 2G, 32G.  My question is since dm365 and dm368 are PIN to PIN compatible,why the same software cannot work for dm368? Is there something special for PINMUX configuration or clock issue?

Could anybody give me some hints? Thanks in advance.

I got the following output

"<4>Enabling 4 bit mode

<7>mmc1: starting CMD16 arg 00000200 flags 00000015

<7>mmc1: req done (CMD16): 0/0/0: 00000900 00000000 00000000 00000000

<6>mmcblk1: mmc1:e2bd S064B 62080KiB 

<6> mmcblk1:<7>mmc1: starting CMD18 arg 00000000 flags 00000035

<7>davinci-mmc davinci-mmc.1: MMCSD : Data xfer (block read), DTO 10000 cycles + 50000000 ns, 8 blocks of 512 bytes

<7>davinci-mmc davinci-mmc.1: MMCSD: Data CRC error, bytes left 0

<7>mmc1: req done (CMD18): 0/2/0: 00000900 00000000 00000000 00000000

<3>mmcblk1: error 2 transferring data

<4>end_request: I/O error, dev mmcblk1, sector 0

<3>Buffer I/O error on device mmcblk1, logical block 0

<7>mmc1: starting CMD18 arg 00000000 flags 00000035

<7>davinci-mmc davinci-mmc.1: MMCSD : Data xfer (block read), DTO 10000 cycles + 50000000 ns, 8 blocks of 512 bytes

<7>davinci-mmc davinci-mmc.1: MMCSD: Data CRC error, bytes left 0

<7>mmc1: req done (CMD18): 0/2/0: 00000900 00000000 00000000 00000000

<3>mmcblk1: error 2 transferring data

<4>end_request: I/O error, dev mmcblk1, sector 0

<3>Buffer I/O error on device mmcblk1, logical block 0

<4> unable to read partition table

"

  • 0
    Genius 3925 points

    I guess your DM368 is probably using a differenct clock than the DM365, so the PLL configuration will be different. Make sure you MMC1 clock is within spec.

    Are you using the same UBL code for the DM368EVM?

  • 0 in reply to Hongfeng Wang
    Prodigy 20 points

    Hi Hongfeng,

          Yes. I catch MMC0/SD0 clock is around 200KHz, while MMC1/SD1 is 700KHz, which exceeds 400KHz noted in datasheet , so  I tried to set PLLC1SYSCLK4 Configuration using PLLC1SYSCLK4 Configuration's value, and the MMC1/SD1 can be recongnized now.   Since the PLLC1SYSCLK4 Configuration4 is for commont rate setting, I wonder if the value from PLLC1SYSCLK8 is right for other Paripheral module and EDMA.  Any suggestion ?

        thank you

     

  • 0 in reply to Steve Sun71571
    Genius 3925 points

    The datasheet says the maximum function clock for MMC is 100Mhz.

    After you set the clock for the module, you need to adjust you MMCCLK accordingly.