PROCESSOR-SDK-AM62X: PROCESSOR-SDK-AM62X

Part Number: PROCESSOR-SDK-AM62X

Tool/software:

We have gone through AM62x_TRM and understood that SDMMC controller hardware supports UHS mode. We just wanted to understand if SDHC controller supports UHS speeds? When we checked k3-am62-main.dtsi file located at below Linux path, it looks like it doesn't have UHS setting.

"..\ti-processor-sdk-linux-am62xx-evm-09.02.01.10\board-support\ti-linux-kernel-6.1.83+gitAUTOINC+c1c2f1971f-ti\arch\arm64\boot\dts\ti\k3-am62-main.dtsi"

 Could you please suggest us if SDHC controller works on UHS speed and how we can test it. Please find attached screenshot for k3-am62-main.dtsi.

  • Hello,

    The AM62x MMCSD host controller supports upto HS200 & UHS-1 for eMMC & SD card respectively. By default the kernel driver tries to enumerate them in the highest supported speed mode. The logs would look something like this

    root@am64xx-evm:~# dmesg | grep mmc
    [    1.358639] mmc0: CQHCI version 5.10
    [    1.390195] mmc1: CQHCI version 5.10
    [    1.408531] mmc0: SDHCI controller on fa10000.mmc [fa10000.mmc] using ADMA 64-bit
    [    1.428592] mmc1: SDHCI controller on fa00000.mmc [fa00000.mmc] using ADMA 64-bit
    [    1.490259] mmc1: new ultra high speed SDR104 SDHC card at address aaaa
    [    1.497853] mmcblk1: mmc1:aaaa SK32G 29.7 GiB
    [    1.504851] mmc0: Command Queue Engine enabled
    [    1.505795]  mmcblk1: p1 p2
    [    1.509347] mmc0: new HS200 MMC card at address 0001
    [    1.517896] mmcblk0: mmc0:0001 S0J56X 14.8 GiB
    [    1.524646] mmcblk0boot0: mmc0:0001 S0J56X 31.5 MiB
    [    1.531035] mmcblk0boot1: mmc0:0001 S0J56X 31.5 MiB
    [    1.537312] mmcblk0rpmb: mmc0:0001 S0J56X 4.00 MiB, chardev (240:0)
    [    1.822142] EXT4-fs (mmcblk1p2): recovery complete
    [    1.828261] EXT4-fs (mmcblk1p2): mounted filesystem with ordered data mode. Quota mode: none.
    [    4.019004] EXT4-fs (mmcblk1p2): re-mounted. Quota mode: none.
    root@am64xx-evm:~# 

    Regards,

    Prashant

  • Hi Prashant,

    Thank you for your response. We understand that AM62x eMMC host controller supports up to HS200 & UHS-1. We would like to know SDHC(High capacity SD) host controller supports UHS or not. If it supports, which driver we can refer from the SDK and how we can test it. Thanks!!

    Best Regards,

    Revashankar

  • Hello,

    The SD interface of the AM62x MMCSD host controller supports UHS-1 cards as described in the TRM.

    In the previously shared logs, you should see the Linux Kernel enumerated the SDHC SD card in UHS-1 mode (mmc1: new ultra high speed SDR104 SDHC card at address aaaa).

    Regares,

    Prashant

  • Hi Revashankar,

    From the offline discussion, it seems there is still a confusion in the response above.

    > The response is not specific for SDHC controller instead its confirmed for SDMMC controller.

    Please note that the "AM62x MMCSD host controler" mentioned in the TRM is a SDHC controller. The names are just interchanged in many places.

    Please don't hesitate to follow up on the e2e threads if you have any questions.

  • Hi Bin,

    Thank you for the clarification on SDHC and SDMMC controller. Could you please further guide us on below points:

    1. From first response, we can see from the log that controller supports UHS mode.
      • We want to know which dts file, driver refers for UHS configuration? We can't see any settings for UHS mode under "..\ti-processor-sdk-linux-am62xx-evm-09.02.01.10\board-support\ti-linux-kernel-6.1.83+gitAUTOINC+c1c2f1971f-ti\arch\arm64\boot\dts\ti\k3-am62-main.dtsi".
      • Which driver file we can refer to understand UHS mode settings? in case, dts doesn't configure UHS and it is hardcoded in driver, could you please point out function name where UHS mode setting is done?
    2. Steps to test UHS mode?

    Best Regards,

    Revashankar

  • Hello,

    1) The TI MMC driver uses the OTAP properties to determine the SD card capability as defined here:

    2) You should first determine if the Linux Kernel is enumerating the SD card as UHS like shown in the previously attached logs.

    Regards,

    Prashant