• Locked Locked
  • Replies 9 replies
  • Subscribers 99 subscribers
  • Views 685 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.

mmc1 boot problem on omap3530

Huai Hellen
Expert 1030 points

Hi, all

when I boot from sd1, there appear below information:

SDHC: command response timeout CTO!
MMC::MMCCommandResponse: MMCSendCommand error, command = 8
MMC::MMCCommandResponse: Command Response Error

then, it goes on to boot and can be renognized by sd1 slot.

but it could not be recognized by sd2 slot, through debug info, I find it stopped when first send cmd17, no response

Besides, I find another 2G sd card which appears the same phenomina

and also, the system have detected this card and the sdloaddevice() function succeed

  • TI__Genius 9185 points

    What version of BSP are you using? And I assume you are on your custom board and not on the EVM if you are testing SD2 slot.

    A few months back we did get confirmation from a customer that undefining the following definition "#define MMCHS1_VDDS_WORKAROUND" in the file OMAP35XX_TPS659XX_TI_V1\inc\sdhc.h helped with this issue. 

    Give this a try and let us know if it helps.

     

  • in reply to Jatin Jain
    Expert 1030 points

    Hi, Jatin

    You are right, I use sd2 slot on my custom board, the bsp version is 6.14.01

    I undef the macro MMCHS1_VDDS_WORKAROUND in in the file OMAP35XX_TPS659XX_TI_V1\inc\sdhc.h, but it does not make any difference.

    The level shifter I used is tx0106, and what I cleared is that there are two sd cards among the ten sd cards I tested happens what I described, which is recognized by sd1 slot,  not recognized by sd2 slot. Other eight cards can be recognized by both sd1 slot and sd2 slot2

  • in reply to Huai Hellen
    Expert 1030 points

    and in fact, as the macro MMCHS1_VDDS_WORKAROUND is defined in sdcontroller.h again, so undef it in sdhc.h has no impacts.

    Moreover, I undef the MMCHS1_VDDS_WORKAROUND in file sdcontroller.h, there is no impacts yet.

  • in reply to Huai Hellen
    TI__Genius 9185 points

    Maybe this is a different issue. The flag related comment I made was to get the MMC working with SD2 slot. Since you clarified that SD1 and SD2 work for you for 8 different cards and only 2 cards are showing the problem with SD2 (but do work with SD1) this maybe a different issue.

    Which cards are showing the problem? 

     

  • in reply to Jatin Jain
    Expert 1030 points

    a 2G kinston and a 512M mini SD through a SD reader show the above problem

  • in reply to Huai Hellen
    Expert 1030 points

    Jatin,

    Could you tell me when to show the disk such as "Storage card" in my device page??

    I find the sd card client driver has been loaded and registered successfully, and has read the registery item "folder" ="SD Memory"' in path [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\SDMemory],

    why not display the disk sign?

  • in reply to Huai Hellen
    Expert 1030 points

    and It hang up when send cmd17(SD_CMD_READ_SINGLE_BLOCK) twice, it gets no response

  • in reply to Huai Hellen
    Expert 1030 points

    and It hangs up when send cmd17(SD_CMD_READ_SINGLE_BLOCK) twice, it gets no response

  • in reply to Huai Hellen
    Expert 1030 points

    Jatin,

    the latest state is:

     when I decrease clock frequency to 19.2MHz, SD2 slot can identify all ten sd cards I tested. However, when play video file about 700M size, it occurs "play file error"

    Then, I continued to decrease clock to 16MHz, 12MHz, 8MHz, 4MHz ,till to 1MHz, when copy file from sd cards to itself, the copied file is about 20M size. it occurs error code 38,

    which means "reached the end of file", and when play the above video file, it plays slowly.

    So, I could not make balance between clock and play continuity.

    And is there any suggestion about my problem?