SK-AM62: An SDIO device is externally connected using the SD pins on the EVB board. After adapting the driver, a power-on failure error is reported

xiaoding yang

Prodigy 30 points

Part Number: SK-AM62

Tool/software:

HW：Connect an SDIO device via fly wires.

SW：arch/arm64/boot/dts/ti/k3-am62x-sk-common.dtsi

Rewrite the SDIO1 device node as follows:

&sdhci1 {
- /* SD/MMC */
- bootph-all;
- status = "okay";
- pinctrl-names = "default";
- pinctrl-0 = <&main_mmc1_pins_default>;
- disable-wp;
+ /* SD/MMC */
+ bootph-all;
+ status = "okay";
+ pinctrl-names = "default";
+ pinctrl-0 = <&main_mmc1_pins_default>;
+ /* Limit frequency to 50Mhz under 3.3v */
+ max-frequency = <50000000>;
+ sd-uhs-sdr12;
+ broken-cd;
+ no-sd;
+ no-mmc;
};

check dmesg log as follows:

root@am62xx-evm:~# dmesg | grep mmc
[ 1.897508] mmc0: CQHCI version 5.10
[ 1.939803] mmc0: SDHCI controller on fa10000.mmc [fa10000.mmc] using ADMA 64-bit
[ 1.949484] mmc1: CQHCI version 5.10
[ 2.024789] mmc0: Command Queue Engine enabled
[ 2.029287] mmc0: new HS200 MMC card at address 0001
[ 2.035544] mmcblk0: mmc0:0001 G1M15L 29.6 GiB
[ 2.043552] mmcblk0: p1
[ 2.046687] mmcblk0boot0: mmc0:0001 G1M15L 31.5 MiB
[ 2.052740] mmcblk0boot1: mmc0:0001 G1M15L 31.5 MiB
[ 2.058895] mmcblk0rpmb: mmc0:0001 G1M15L 4.00 MiB, chardev (239:0)
[ 3.477348] sdhci-am654 fa00000.mmc: Power on failed
[ 3.512954] mmc1: SDHCI controller on fa00000.mmc [fa00000.mmc] using ADMA 64-bit
[ 3.637011] EXT4-fs (mmcblk0p1): recovery complete
[ 3.642471] EXT4-fs (mmcblk0p1): mounted filesystem df55c9b4-ab34-4143-af16-febd6b620543 r/w with ordered data mode. Quota mode: none.
[ 5.269331] EXT4-fs (mmcblk0p1): re-mounted df55c9b4-ab34-4143-af16-febd6b620543 r/w. Quota mode: none.

add info below:

[ 1135.316321] mmc1: Timeout waiting for hardware cmd interrupt.
[ 1135.322092] mmc1: sdhci: ============ SDHCI REGISTER DUMP ===========
[ 1135.328519] mmc1: sdhci: Sys addr: 0x00000000 | Version: 0x00001004
[ 1135.334944] mmc1: sdhci: Blk size: 0x00000000 | Blk cnt: 0x00000000
[ 1135.341369] mmc1: sdhci: Argument: 0x00000000 | Trn mode: 0x00000000
[ 1135.347795] mmc1: sdhci: Present: 0x01f00001 | Host ctl: 0x00000001
[ 1135.354221] mmc1: sdhci: Power: 0x0000000e | Blk gap: 0x00000080
[ 1135.360645] mmc1: sdhci: Wake-up: 0x00000000 | Clock: 0x0000e8c3
[ 1135.367070] mmc1: sdhci: Timeout: 0x00000000 | Int stat: 0x00000000
[ 1135.373496] mmc1: sdhci: Int enab: 0x00ff0003 | Sig enab: 0x00ff0003
[ 1135.379921] mmc1: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00000000
[ 1135.386346] mmc1: sdhci: Caps: 0x3de8c801 | Caps_1: 0x18002407
[ 1135.392772] mmc1: sdhci: Cmd: 0x00000000 | Max curr: 0x00000000
[ 1135.399196] mmc1: sdhci: Resp[0]: 0x00000000 | Resp[1]: 0x00000000
[ 1135.405622] mmc1: sdhci: Resp[2]: 0x00000000 | Resp[3]: 0x00000000
[ 1135.412047] mmc1: sdhci: Host ctl2: 0x00000000
[ 1135.416478] mmc1: sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0x0000000000000000
[ 1135.423596] mmc1: sdhci: ============================================

1 month ago

0 Biao Li 1 month ago

TI__Expert 6440 points

Hi Prashant,

Can you help priority this thread? Any unclear pls let us know, customer is reworking the TI EVM and connect new SDIO device using MMC1 interface.

BR,

Biao

0 xiaoding yang 1 month ago

Prodigy 30 points

When the CD pin is pulled low, the following logs are displayed:

[ 81.058362] sdhci-am654 fa00000.mmc: card claims to support voltages below defined range
[ 81.068297] mmc1: error -110 whilst initialising SDIO card

0 Prashant Shivhare 1 month ago in reply to xiaoding yang

TI__Guru 69581 points

Hello,

The issue is that the SDIO card is not being detected? What is the SDIO device you are using?

0 xiaoding yang 1 month ago in reply to Prashant Shivhare

Prodigy 30 points

RX145 is V2X module

0 xiaoding yang 1 month ago

Prodigy 30 points

Hello,

We try open the config of CONFIG_MMC_DEBUG ,is't work.

root@am62xx-evm:~# zcat /proc/config.gz | grep CONFIG_MMC_DEBUG
CONFIG_MMC_DEBUG=y
root@am62xx-evm:~#
root@am62xx-evm:~#
root@am62xx-evm:~#
root@am62xx-evm:~#
root@am62xx-evm:~#
root@am62xx-evm:~# cat /proc/sys/kernel/printk
7 4 1 7
root@am62xx-evm:~#
root@am62xx-evm:~#
root@am62xx-evm:~# echo 8 > /proc/sys/kernel/printk
root@am62xx-evm:~# cat /proc/sys/kernel/printk
8 4 1 7
root@am62xx-evm:~# [ 234.354728] sdhci-am654 fa00000.mmc: card claims to support voltages below defined range
[ 234.415415] mmc1: error -110 whilst initialising SDIO card
[ 234.468598] sdhci-am654 fa00000.mmc: card claims to support voltages below defined range
[ 234.529477] mmc1: error -110 whilst initialising SDIO card
[ 234.583416] sdhci-am654 fa00000.mmc: card claims to support voltages below defined range
[ 234.648280] mmc1: error -110 whilst initialising SDIO card
[ 234.704587] sdhci-am654 fa00000.mmc: card claims to support voltages below defined range
[ 234.777611] mmc1: error -110 whilst initialising SDIO card

0 Prashant Shivhare 1 month ago in reply to xiaoding yang

TI__Guru 69581 points

Hello,

As per the datasheet, the MMC1 interface supports both SD cards and SDIO devices. The Kernel already has the support for TI CC33 WiFi device connected to the MMC2 interface.

If the SDIO device, you are using, is not working then it could be something specific to the SDIO device only. Please connect with the SDIO device vendor once as well for the suggestions.

Thanks!

0 Prashant Shivhare 1 month ago in reply to Prashant Shivhare

TI__Guru 69581 points

Hello,

As for the support from us, could you please share the snapshot of the SDIO device connected to the EVM? We would like to see if there are any obvious errors in the connections.

Additionally, please clarify the following:

Have you pulled SDCD signal low to stimulate an always connected SDIO device? I believe you have already done so as you conveyed in one of the previous response.
What IO voltage are you using for the attached SDIO device?

Thanks!

0 xiaoding yang 1 month ago in reply to Prashant Shivhare

Prodigy 30 points

The v2x module is adapted to IMX8 MINI, It is obvious that the device tree parameters of TI and NXP are inconsistent.

0 Prashant Shivhare 1 month ago in reply to xiaoding yang

TI__Guru 69581 points

Have you tried evaluating the differences between the parameters? Is it possible to share the working DTB from their platform and the non-working DTB from ours?

0 xiaoding yang 1 month ago in reply to Prashant Shivhare

Prodigy 30 points

V2X is connected to the DAT0/1/2/3, CLK, CMD, and CD pins of MMC1

0 xiaoding yang 1 month ago in reply to Prashant Shivhare

Prodigy 30 points

For your analysis, do you only need the dmesg logs?

0 Xu(SH) Liu 1 month ago in reply to xiaoding yang

TI__Expert 3775 points

Xiaoding, as suggested by our BU team, kindly please share the working/verified DTS entries includes this V2X module through SDIO interface, and also add one schematic snapshot on the connection of this part, so we can accelerate the software changes and debug support from expert team. thanks.

0 Xu(SH) Liu 1 month ago in reply to Xu(SH) Liu

TI__Expert 3775 points

customer identified issue from V2X module when receiving commands from SoC, close at this moment from ti side.

Processors

Processors forum

SK-AM62: An SDIO device is externally connected using the SD pins on the EVB board. After adapting the driver, a power-on failure error is reported