The jetson nano b01 devkit can't use the extra SD Card

Hey, guys!
I just designed a carrier for jetson nano b01 and use the module of the jetson nano b01 devit to test the carrier board.
I refer the topic SD Card not detected - #42 by Karis to the device tree.

sdhci@700b0400 {
compatible = “nvidia,tegra210-sdhci”;
reg = <0x0 0x700b0400 0x0 0x200>;
interrupts = <0x0 0x13 0x4>;
aux-device-name = “sdhci-tegra.2”;
iommus = <0x2b 0x1b>;
nvidia,runtime-pm-type = <0x0>;
clocks = <0x21 0x45 0x21 0xf3 0x21 0x136 0x21 0xc1>;
clock-names = “sdmmc”, “pll_p”, “pll_c4_out2”, “sdmmc_legacy_tm”;
resets = <0x21 0x45>;
reset-names = “sdhci”;
status = “okay”;
tap-delay = <0x3>;
trim-delay = <0x3>;
mmc-ocr-mask = <0x3>;
max-clk-limit = <0x61a80>;
ddr-clk-limit = <0x2dc6c00>;

When I flash the dtb, I found the jetson nano boot failed.

bash: cannot set terminal process group(-1): Inappropriate ioctl for device.
bash: no job control in this shell

The jetson-nano-qspi-sd can’t use the extra SD Card?
I need some help.
Thank you.

Can anyboay help me QAQ

Can anyboay help me QAQ

Hello @iyric,

I was able to reproduce on my end the reported issue. I will be investigating the root cause and reach out with more details soon.

Thank you mike, I used the lastest version.I’m looking forward to your reply.

Hello @iyric,

customization is not supported for modules coming from devkits. I assume you designed your carrier board targeting a production module. For the latter, the instructions on the OEM Design Guide demonstrate how to utilize the SDMMC3 interface.

Thank you.But I want to be compatible with nano devit and nano EMMC.

Modules from a developer kit are not meant for production and should be used with the the devkit carrier board. For other use cases the production module is the way to go.

Thank you for your answer.

Are you saying that SDMMC3 interface is used on devkit modules for embedded sdcard?
If it’s not the case, why can’t we use both SDcard on Nano module and SDcard on carrier board? Technically I mean, not because of your strange marketing policy…