SD card not detected in Jetson NX

Robotics & Edge Computing Jetson & Embedded Systems Jetson Xavier NX
1

Hi,

We have our custom build BSP (based on L4T32.4.3)on custom carrier board and one of our customer reports issue with SD card not detected. Below is the issue, any suggestion?

I’m attempting the manual install of CUDA, however I’ve run out of space on the eMMC. I’ve inserted a 128GB uSD card into the uSD card slot on the NX, but the uSD card is not being recognized as a format-able disk. The jetson appears to recognize that the uSD card is being inserted, but I can’t view the partitions or file contents using tools like gparted, Ubuntu Disks application, or df –h.

Here is the dmesg output when I take out the uSD card, and then put it back in:

[ 3468.709278] extcon-gpio-states external-connection:extcon@1: Cable state:0, cable id:0
[ 3468.709293] tegra-xudc-new 3550000.xudc: vbus state: 0
[ 3468.709302] tegra-xudc-new 3550000.xudc: device mode off: 0
[ 3468.709347] tegra-xudc-new 3550000.xudc: active: 1 => 0
[ 3468.709359] tegra-xudc-new 3550000.xudc: entering ELPG
[ 3468.714697] tegra-xudc-new 3550000.xudc: entering ELPG done
[ 3471.093108] extcon-gpio-states external-connection:extcon@1: Cable state:1, cable id:1
[ 3471.093241] tegra-xudc-new 3550000.xudc: vbus state: 1
[ 3471.093256] tegra-xudc-new 3550000.xudc: exiting ELPG
[ 3471.096889] tegra-xudc-new 3550000.xudc: exiting ELPG done
[ 3471.096918] tegra-xudc-new 3550000.xudc: device mode on: 0
[ 3471.096937] tegra-xudc-new 3550000.xudc: active: 0 => 1
I’ve mounted the uSD card on another system and it is detected, with file system: exfat

Any guidance on how to get uSD storage compatible with the NX?

2

I am not sure what is going on here. The xudc log is for the usb driver. Not for the sdcard.

Thus, I am not sure why removing a sdcard will trigger something from usb driver. Any info for this custom board?

3

Hi,

we have Disconnected optional SDCARD_CD from SODIMM] pin 208, connected pin 208 to FAN_TACH .GPIO00 (USB_VBUS_EN0) is being used as SDCARD_CD for design requirement, I will get the details meanwhile. attached the SD card details and board details picture

fld-bb01-normal
fld-bb01-normal800×827 112 KB

SD_CARD
SD_CARD953×172 18.8 KB

FFR
FFR710×392 74.9 KB

4

And does your board dtb have any patch for the sdcard?

Actually, cd gpio should not be optional…

5

Yes we have made some changes related to SD card to align this design change. here is the patch, anything wrong?

6

So the cd-gpio is the GPIO00?

7

Yes correct SDCARD_CD in the schematic I have shared is GPIO00 (USB_VBUS_EN0)

8

Your cd-gpios in the device tree does not match your hardware.

9

sorry, I missed the GPIO changes here it is
patch.diff (2.4 KB)

10

You better checking if your final dtb is really same as what you are doing now.
If some user unplug the sdcard and usb gets affected, then I guess it means the usb power is still related to your cd-gpio.

11

Yes, I have checked now with my final dtb it is same. so for my design change my patch files need any update, change?

12

I don’t know. You just share me few patches, a partial log, one block diagram and a schematic that only has few sd data pins connected.

Honestly, totally not sufficient information.

13

customer have made routine updates to Ubuntu packages. the top USB2(usb2-0 ) slot doesn’t work after CUDA updates.

they did use the top USB to create a backup image of the device at some point, and they saw it on their host machine when they were attempting to install CUDA with jetpack. Also SD card is an issue.

Is there any chance the update changes the DTBs? or by chance they made any update to the patch changes to reset? Here SD card and USB-2 are the changes made as part of patch.

14

Sorry for the broken info. we have made only the SD card changes I have shared earlier plus enabled the USB-2 to host mode as below:
ports {
usb2-0 {

  •   		mode = "otg";

  •   		mode = "host";
  		status = "okay";
  	};
  	usb2-1 {

these are the dtbs changes. and attached is the Schematic for SD card

I will ask for the full log from customer.

15

Please try to figure out what has customer tried on their board.

If this is caused by update, then this issue should be gone if they re-flash the board again with the driver package that you provided. And again, they shall hit this issue again when they run the update.

Also, what kind of update is that? apt-get upgrade ?

And please stop sharing me some partial usb dts. This really does not help. If you want others to help analyze, you shall share the finalized dts and the full log.

1 Like
16

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