Orin Nano emulation exits booting

Hello Nvidia Developer forum,

when trying to emulate an Orin 4GB or Orin 8GB on an AGX Orin my device exits before the boot process with the exact display as shown in this thread ([IMG_6810.HEIC]):

My Setup:
Host:
- Ubuntu 20.04
- SDK Manager 2.0.0.11405 x86_64
- JetPack 5.0.2 (rev. 2) and Jetpack 5.0.2 Runtime (rev. 2) (tried both)
AGX Orin:
- Jetson AGX Orin 32GB developer kit (P3737 carrier board)

Steps:

  1. Flashed default image with SDK Manager - works well
  2. Followed these steps:
    https://developer.download.nvidia.com/embedded/L4T/r35_Release_v1.0/README.txt?t=eyJscyI6ImdzZW8iLCJsc2QiOiJodHRwczovL3d3dy5nb29nbGUuY29tLyJ9
    and downloaded Orin_Nano_Overlay_35.1.tbz2 from this page:
    https://developer.nvidia.com/embedded/jetson-linux-r351

The flash process concludes with the following lines:
[ 650.9402 ] Writing partition B_MEM_BCT with mem_coldboot_sigheader.bct.encrypt [ 243712 bytes ]
[ 650.9406 ] […] 100%
[ 653.9421 ] Flashing completed

[ 653.9422 ] Coldbooting the device
[ 653.9438 ] tegrarcm_v2 --chip 0x23 0 --ismb2
[ 653.9452 ] MB2 version 01.00.0000
[ 654.1485 ] Coldbooting the device
[ 654.1501 ] tegrarcm_v2 --chip 0x23 0 --reboot coldboot
[ 654.1514 ] MB2 version 01.00.0000
*** The target t186ref has been flashed successfully. ***
Reset the board to boot from internal eMMC.

Afterwards, the device exits with the messages mentioned at the beginning and shown in the image.

Moreover , i tried to flash with the “sudo ./flash.sh jetson-agx-orin-devkit-as-nx-8gb mmcblk0p1”
command but after setting up the ubuntu account, the screen turned black. I waited for 30 minutes and pushed the reset button on the AGX Orin. After that, the device did also exit as in the case above.

Dump the serial console log, please.

Hello Dave and thanks for your quick reply!

Attached you may find the Logfile
logfile.txt (490.7 KB)

So it keeps rebooting without getting into the Ubuntu prompt?
Can you please verify with a newer version?

Yes, exactly.

For the sake of completeness: I installed and ran Jetpack 5.1.2 successfully, documented with the following log:
AgxOrinJetPack5.1.2Successfull.txt (62.8 KB)

Afterwards, I ran the following commands to run the Orin Nano 4GB emulation:
cd ~/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_AGX_ORIN_TARGETS
wget https://developer.nvidia.com/embedded/l4t/r35_release_v1.0/release/jetson_linux_r35.1.0_aarch64.tbz2
wget https://developer.nvidia.com/embedded/l4t/r35_release_v1.0/release/tegra_linux_sample-root-filesystem_r35.1.0_aarch64.tbz2
sudo tar -xpf jetson_linux_r35.1.0_aarch64.tbz2
cd Linux_for_Tegra/rootfs
sudo tar -xpf ~/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_AGX_ORIN_TARGETS/tegra_linux_sample-root-filesystem_r35.1.0_aarch64.tbz2
cd …/
sudo ./apply_binaries.sh
cd …/
[Download Orin_Nano_Overlay_35.1.tbz2 from https://developer.nvidia.com/embedded/jetson-linux-r351 into ~/Downloads]
sudo tar -xpf ~/Downloads/Orin_Nano_Overlay_35.1.tbz2
cd Linux_for_Tegra
sudo ./flash.sh jetson-agx-orin-devkit-as-nano4gb mmcblk0p1

same result, log:
OrinNano4GBJetpack5.1.2.txt (248.0 KB)

I just tried the same setup on my side, and there is not booting issue.

nvidia@tegra-ubuntu:~$ cat /etc/nv_boot_control.conf 
TNSPEC 3701-500-0000-J.0-1-1-jetson-agx-orin-devkit-as-nano4gb-
COMPATIBLE_SPEC 3701-300-0000--1--jetson-agx-orin-devkit-as-nano4gb-
TEGRA_LEGACY_UPDATE false
TEGRA_BOOT_STORAGE mmcblk0
TEGRA_EMMC_ONLY false
TEGRA_CHIPID 0x23
TEGRA_OTA_BOOT_DEVICE /dev/mtdblock0
TEGRA_OTA_GPT_DEVICE /dev/mtdblock0

Maybe you should first check if it’s working with the default jetson-agx-orin-devkit flashing config.

I tried the default flashing using the following commands:
export JETPACK=$HOME/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_AGX_ORIN_TARGETS/Linux_for_Tegra
cd $JETPACK/tools
sudo ./l4t_create_default_user.sh -u agxorin -p agxorin
cd …
sudo ./flash.sh jetson-agx-orin-devkit mmcblk0p1

→ worked well.
AgxOrin32GBJetpack5.1.2Successfull.txt (98.5 KB)

Moreover I tried the following (changes in *.tbz2 files), which resulted in a login screen on serial console but my predefined user didnt work for (“localhost”) login:
export JETPACK=$HOME/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_AGX_ORIN_TARGETS/Linux_for_Tegra
cd $JETPACK/tools
sudo ./l4t_create_default_user.sh -u agxorin -p agxorin
cd ~/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_AGX_ORIN_TARGETS
[Download https://developer.nvidia.com/embedded/l4t/r35_release_v4.1/release/jetson_linux_r35.4.1_aarch64.tbz2]
[Download https://developer.nvidia.com/downloads/embedded/l4t/r35_release_v4.1/release/tegra_linux_sample-root-filesystem_r35.4.1_aarch64.tbz2]
sudo tar -xpf ~/Downloads/Jetson_Linux_R35.4.1_aarch64.tbz2
cd Linux_for_Tegra/rootfs
sudo tar -xpf ~/Downloads/JetPack_5.1.2_Linux_JETSON_AGX_ORIN_TARGETS/Tegra_Linux_Sample-Root-Filesystem_R35.4.1_aarch64.tbz2
cd …/
sudo ./apply_binaries.sh
cd …/
[Download Orin_Nano_Overlay_35.1.tbz2 from https://developer.nvidia.com/embedded/jetson-linux-r351 into ~/Downloads]
sudo tar -xpf ~/Downloads/Orin_Nano_Overlay_35.1.tbz2
cd Linux_for_Tegra
sudo ./flash.sh jetson-agx-orin-devkit-as-nano4gb mmcblk0p1

I don’t know why you are downloading and extracting the BSP again.
You should run l4t_create_default_user.sh after apply_binaries.sh.

You don’t need this if you use 35.2.1 or later versions. The overlay is only required on 35.1.

Thanks for clarification!

Then I’ll give it a try with Jetpack 5.1 and Jetson Linux 35.2.1 like the following:
export JETPACK=$HOME/nvidia/nvidia_sdk/JetPack_5.1_Linux_JETSON_AGX_ORIN_TARGETS/Linux_for_Tegra
cd $JETPACK/tools
sudo ./l4t_create_default_user.sh -u agxorin -p agxorin
cd …/
sudo ./flash.sh jetson-agx-orin-devkit-as-nano4gb mmcblk0p1

One more question:
Does this table https://developer.nvidia.com/embedded/jetson-linux-archive mean the AGX Orin Developement Kit 32 GB works only with Jetson Linux 35.1 and 35.2.1?

It’s specifically stated just because AGX Orin 64GB is supported starting from 35.3.1, so in 35.1 and 35.2.1, only AGX Orin 32GB is supported, and it is also supported in later versions.

This one worked for me. Thanks for your continuous help and quick replies!

1 Like

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