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.

Linux/AM5726: MMC1 pinmux configuration

Part Number: AM5726

Tool/software: Linux

When using the TI PinMux Tool to configure the pins for MMC1 which are connected to an SD Card cage, I have noticed that the Mode setting affects the genericFileFormatIOdelay.txt and the genericFileFormatPadConf.txt

What is the difference between Mode = DS, HS, and SDR104?  Is there any reason to select one over the others where MMC1 is being used for SD Card?

  • The PMT team have been notified. They will respond here.
  • Hello,

    Kent Kanja said:
    I have noticed that the Mode setting affects the genericFileFormatIOdelay.txt and the genericFileFormatPadConf.txt

    Correct. These menus, and in fact whole bunch of other settings you have inputted, are taken into account by the code generation engine to export the correct iodelay values. For details see this app note on configuring iodelays with the PinMux tool: 

    So when you are tinkering with the menus, the templates will export one of the following delay modes (see Data Manual Table 7-2. Modes Summary for details).

    Kent Kanja said:
    What is the difference between Mode = DS, HS, and SDR104?  Is there any reason to select one over the others where MMC1 is being used for SD Card?

    The options correspond to the MMC1 actual functional modes supported. So, you should be configuring these to correspond to the mode being used, whether it is high speed, SDR, DDR, etc. And these are basically SD card standard Part A2 v3.00 data transfer rates (see chapter eMMC/SD/SDIO in the TRM for details). Not sure which one your setup is doing, you need to figure that out yourself.

    thanks,

    Alex

  • Hello,

    We haven't heard back from you, I'm assuming you were able to resolve your issue.
    If not, just post a reply below (or create a new thread if the thread has locked due to time-out).

    Thanks,
    Alex