Hi Igorpadykov:
Thanks for your reply. It seems that my problem is not same with the one you discussed above. I think if SD1 cmd and clock pinmux value were not set correct. In dts file imx6ul-14*14-evk.dts, I usethe pinmuxs as follows referenced from demo board:
pinctrl_usdhc1:usdhc1grp{
MX6UL_PAD_SD1_CMD_USDHC1_CMD 0x17059
MX6UL_PAD_SD1_CLK_USDHC1_CLK 0x10071
MX6UL_PAD_SD1_DATA0_USDHC1_DATA0 0x17059
MX6UL_PAD_SD1_DATA1_USDHC1_DATA1 0x17059
MX6UL_PAD_SD1_DATA2_USDHC1_DATA2 0x17059
MX6UL_PAD_SD1_DATA3_USDHC1_DATA3 0x17059
So, are the values above acorrding to the hardware designing? and shouled I modify them?
Thanks very much.
>values above acorrding to the hardware designing? and shouled I modify them?
this depends on custom board layout, so you should find correct settings (drive strength) yourself
based on suggestions provided on reference link with similar issue.
Best regards
igor
Hi songyonglai
such error was reported on other forums like https://forums.developer.nvidia.com/t/debugging-sd-uhs-cards-on-the-tx2/67641/3
and seems it is related to signal integrity, so one can try solutions for improving signal quality suggested on
https://community.nxp.com/t5/i-MX-Processors/eMMC-8GB-to-4GB-crash-on-linux-yocto-boot/m-p/373231
Best regards
igor