Unable to boot with microSD. Log shows the MMC device is detected later on

Robotics & Edge Computing Jetson & Embedded Systems Jetson Orin Nano
1

Hi, I’m using the Jetson Orin Nano Developer Kit and I have followed the Getting Started Guide. After formatting and flashing the microSD card with JetPack 5.1.3 using Balena Etcher I can’t get a visual output (last thing I see is “L4TLauncher: Attempting Recovery Boot" "EFI stub: Booting Linux Kernel…”, then the screen goes black), and the fan stops after a few seconds. I’m flashing JetPack5 because the firmware version reported when booting without a microSD in the UEFI console is “Jetson UEFI firmware (version 3.0-32616947 built on 2023-02-21T18:13:46+00:00)”.

I connected a USB-TTL cable to the board and I get a root console. The latest messages in the log before getting there are the following ones:

[ 7.714221] Run /init as init process
[ 7.731031] Root device found: initrd
modprobe: FATAL: Module r8168 not found in directory /lib/modules/5.10.192-tegra

[ 7.733683] Mount initrd as rootfs and enter recovery mode
Finding OTA work dir on external storage devices

Checking whether device /dev/mmcblk?p1 exist

Device /dev/mmcblk?p1 does not exist

Checking whether device /dev/sd?1 exist

Device /dev/sd?1 does not exist

Checking whether device /dev/nvme?n1p1 exist

Device /dev/nvme?n1p1 does not exist

Finding OTA work dir on internal storage device

mount /dev/mmcblk0p1 /mnt

mount: /mnt: special device /dev/mmcblk0p1 does not exist.

Failed to mount /dev/mmcblk0p1 on the /mnt

Failed to run “mount_ota_work_partition /dev/mmcblk0p1 /mnt”

OTA work directory is not found on internal and external storage devices

bash: cannot set terminal process group (-1): Inappropriate ioctl for device

bash: no job control in this shell

bash-5.0# [ 8.329548] mmc1: SDHCI controller on 3400000.sdhci [3400000.sdhci] using ADMA 64-bit
[ 8.693317] mmc1: new ultra high speed SDR104 SDXC card at address 0001
[ 8.694234] mmcblk1: mmc1:0001 FE4S9 239 GiB
[ 8.697158] mmcblk1: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12 p13 p14 p15

bash-5.0#

See the full log here: log.log (83.0 KB)

After this I can use the board for a while, but it becomes very hot soon after.

This seems to suggest that the MMC device is started after the boot process already failed to use it. Is that the issue? Is there a way of solving it? I’m using a 256GB Samsung PRO, U3, V30, A2. Balena Etcher is able to flash it and the verification process does not report any issue.

Thank you.

2

Recovery boot is something telling you that “this board tried to boot up multiple times but all failed” so it boot into a recovery image then. (to prevent you stucking in a boot loop forever)

This boot log is identical to all the people here so does not have much value to review.

To recover from it, please check this post.

However, the reason that makes your board enters recovery boot was not resolved thus you might enter it again.

To avoid that, after you go back to normal boot, check the log again and share if any crash happened.

3

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