Delete sdhci@340000 SD Card node

Autonomous Machines Jetson & Embedded Systems Jetson TX2
,
1

Hi

We have a faulty SD card on our custom carrier board.
We can not remove it from the board because it is mistakenly stuck to the board by conformal coating.
The faulty SD card generates errors during startup, and we want to get rid of them.
It also causes several extra seconds during startup that is very undesired to us.

I tried :

  • “disabling” the sdhci@340000 node: (status = “disabled”)
  • deleting the entire node

The errors have gone.

But, the extra time during startup still exists.

What should I do to completely remove it?

Thanks.

3

What you are doing does not make sense… the “sdcard slot” on custom board would be on sdhci@344000 but not 340000…

4

I see various post suggesting that sdhci@340000 is for SD card on Developer Kit. (And custom board?)

Beside that posts, I used 340000 and it worked!

5

You mean it is a mistake to use sdhci@340000?

So, why it works?

6

Oh sorry. My mistake.

I thought it was talking about Jetson Nano platform. Turns out it is TX2.
Then what you did is correct.

7

OK No problem.
Thanks very much for your help and support.

As I said in post #1, I tried disabling the node as well as deleting the entire sdhci@340000 node.
Both caused the errors to disappear,

But during boot time, after the message :

" Hit any key to stop auto boot: 2 1 0 "

There is an extra 8 second wait, which I think is related to this corrupted SD card.
Because before corruption of SD card, this 8 second did not exist.

8

You can try to dump the log and attach first.

9

Ok I will post the boot log.

10

Here is boot log with “quiet” keyword removed from /boot/extlinux/extlinux.conf :

Boot-Log-Putty.log (70.9 KB)

11

You could try to change the uboot “boot_targets” from sdcard to emmc first and see if that fix your problem.

https://docs.nvidia.com/jetson/archives/l4t-archived/l4t-3273/index.html?_gl=1*kulkxr*_gcl_au*ODQ0NzI0ODU5LjE3MTQzNTkyMDc.#page/Tegra%20Linux%20Driver%20Package%20Development%20Guide/uboot_guide.html

1 Like
12

Very well !
It worked for me.

According that link, I stop auto boot with serial console (Hit any key to stop autoboot):

To interrupt U-Boot

  1. Connect a terminal application to the serial port of the board.
  2. Power on or reset the board.
  3. Wait for the U-Boot sign-on message to appear. Key presses before this message appears may be ignored. (Hit any key to stop autoboot)
  4. Press any key to interrupt the automatic boot process.

Then, checking the value of boot_targets environment variable with the following command:

printenv boot_targets

image
image971×681 14.3 KB

As shown in the above figure, boot_targets value contains mmc1, mmc0, usb0, …

In the U-boot guide, each of the above values are explained:

image
image805×243 7.59 KB

Then running these commands according to U-boot guide, to change the boot_targets value:

env default -f -a
setenv boot_targets mmc0
saveenv

And finally check the boot_targets value again:

printenv boot_targets

image
image973×324 1.87 KB

After doing the above steps, Jetson TX2 no longer wait in the “Hit any key” stage for 8 extra seconds.

Thanks very much Wayne for your exact and to the point help.

Ali.

1 Like
14

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