SD Card hot plugging issue in Jetpack 4.6

Robotics & Edge Computing Jetson & Embedded Systems Jetson TX2
1

I have the hot-plugging issue in jetpack 4.6.

The dts file as tegra186-p3636-0001-p3509-0000-a01.dts (239.6 KB)

And I try to do the same way in jetpack 4.5, the hot-plugging is work.

Have anyone had the same issue?

2

Share your board schematic and dmesg too.

3

Please also compare your dts when it is on jp4.5 and jp4.6.1.

4

The board schematic

sd card
sd card988×342 35.3 KB

1634290491509
1634290491509782×128 80.9 KB

The dmesg file dmesg.txt (66.5 KB)

5

Please compare the sdhci@344 on your jp4.5.1 and jp4.6.

6

Btw, where is your cd gpio in schematic?

7

Is this ?

card_cd_pins
card_cd_pins1003×105 32.5 KB

8

Why do you ask me?This is your carrier board.

Are you talking about gpio8? cd-gpio means card detection gpio which is responsible for the hotplug.

9

Yes, I mean the “GPIO8”.

So, we modify the content of dts as below.

sdhci@3440000 {
status = “okay”;
cd-gpios = <&tegra_main_gpio TEGRA_MAIN_GPIO(X, 4) 0>;
vmmc-supply = <&spmic_sd3>;
nvidia,vmmc-always-on;
mmc-ocr-mask = <3>;
sd-uhs-sdr104;
sd-uhs-sdr50;
sd-uhs-sdr25;
sd-uhs-sdr12;
mmc-ddr-1_8v;
mmc-hs200-1_8v;

	/delete-property/ non-removable;
	/delete-property/ force-non-removable-rescan;

};

pinmux@2430000 {
	pinctrl-names = "default";
	pinctrl-0 = <&pinmux_default>;

	pinmux_default: common {
		uart5_tx_px4 {
			nvidia,pins = "uart5_tx_px4";
			nvidia,function = "nv";
			nvidia,pull = <TEGRA_PIN_PULL_UP>;
			nvidia,tristate = <TEGRA_PIN_DISABLE>;
			nvidia,enable-input = <TEGRA_PIN_ENABLE>;
			nvidia,lpdr = <TEGRA_PIN_DISABLE>;
		};
	};
};
10

If the device can print out new log in dmesg after you hotplug the sdcard, no matter it is successful result or not, it means the hotplug can work.

11

Also, what is your problem in doing this? Sounds like you didn’t compare this yet.

12

The different content like as below.

ommus = <0x11 0x18>;
cd-inverted;

/delete-property/ uhs-mask;
/delete-property/ only-1-8-v;

And It is work after we added them into jetpack 4.6!!!

Could you tell me the root cause?

Thanks

1 Like
13

The root case is probably this one.

/delete-property/ only-1-8-v;

14

Yes, it is the root cause.

May I know the reason?

15

Your vdd-supply is 3.3v, right?

16

Yes, 3.3v!

17

So that only-1-8-v needs to be deleted. That property tells the driver to use 1v8 configuration.

18

Got it!!
Thank you so much!!!

19

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.