• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 98 subscribers
  • Views 996 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.

Original question:

AM6442: Changing SD card speed rate in Linux SDK

AM6442: Disabling HS400 mode in MMC controller

Koichiro Tashiro
Mastermind 22915 points
Part Number: AM6442

Hi,

The customer tried to disable HS400 mode. Please see above original question.
He tried below configurations.

k3-am642-r5-evm.dts configuration:

&sdhci0 {
              /delete-property/ power-domains;
              clocks = <&clk_200mhz>;
              clock-names = "clk_xin";
              ti,driver-strength-ohm = <50>;
              disable-wp;
              pinctrl-0 = <&main_mmc0_pins_default>;
 
              sdhci-caps-mask = <0x80000000 0x00000000>; /* disable HS400 speed mode */
};


k3-am642-evm.dts configuration:
&sdhci0 {
              /* emmc */
              bus-width = <8>;
              non-removable;
              ti,driver-strength-ohm = <50>;
              disable-wp;
 
              sdhci-caps-mask = <0x80000000 0x00000000>; /* disable HS400 speed mode */
};


But, it seems u-boot recognized eMMC card as HS400 mode.

=> mmcinfo
Device: mmc@fa10000
Manufacturer ID: 13
OEM: 14e
Name: S0J56
Bus Speed: 200000000
Mode: HS400 (200MHz)
Rd Block Len: 512
MMC version 5.1

Console log output:
Fullscreen GreenRef_eMMC_HS400_limit_TI_fix_test.txt Download 
U-Boot SPL 2021.01-dirty (Mar 23 2023 - 16:58:02 +0900)
Resetting on cold boot to workaround ErrataID:i2331
resetting ...

U-Boot SPL 2021.01-dirty (Mar 23 2023 - 16:58:02 +0900)
SYSFW ABI: 3.1 (firmware rev 0x0008 '8.4.7--v08.04.07 (Jolly Jellyfi')
SPL initial stack usage: 13424 bytes
Trying to boot from MMC2
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Starting ATF on ARM64 core...

NOTICE:  BL31: v2.7(release):08.04.01.005
NOTICE:  BL31: Built : 16:58:14, Mar 23 2023

U-Boot SPL 2021.01-dirty (Mar 23 2023 - 16:58:20 +0900)
SYSFW ABI: 3.1 (firmware rev 0x0008 '8.4.7--v08.04.07 (Jolly Jellyfi')
Trying to boot from MMC2
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted


U-Boot 2021.01-dirty (Mar 23 2023 - 16:58:20 +0900)

SoC:   AM64X SR1.0 GP
Model: Texas Instruments AM642 EVM
Board: AM64-GPEVM rev E2
DRAM:  2 GiB
NAND:  0 MiB
MMC:   mmc@fa10000: 0, mmc@fa00000: 1
Loading Environment from FAT... *** Warning - bad CRC, using default environment

In:    serial@2800000
Out:   serial@2800000
Err:   serial@2800000
Net:   eth0: ethernet@8000000port@1
Hit any key to stop autoboot:  0 
=> 
=> mmcinfo 
Device: mmc@fa10000
Manufacturer ID: 13
OEM: 14e
Name: S0J56 
Bus Speed: 200000000
Mode: HS400 (200MHz)
Rd Block Len: 512
MMC version 5.1
High Capacity: Yes
Capacity: 14.8 GiB
Bus Width: 8-bit DDR
Erase Group Size: 512 KiB
HC WP Group Size: 8 MiB
User Capacity: 14.8 GiB WRREL
Boot Capacity: 31.5 MiB ENH
RPMB Capacity: 4 MiB ENH
Boot area 0 is not write protected
Boot area 1 is not write protected
=>


Anything is wrong or missing?

Thanks and regards,
Koichiro Tashiro