Problem installing a built image for Orin Nano on nvme.

[didima7777]

I built the image with the following settings

. setup-env --machine jetson-orin-nano-devkit-nvme build_orin

After building the

bitbake core-image-minimal image

The build was successful and I got the image archive.
I put the board into Force Recovery Mode.

I have flashed the board with the encourage command.
I get the following output during the flashing process:

Machine: jetson-orin-nano-devkit-nvme
Rootfs device: nvme0n1p1
Found Jetson device in recovery mode at USB 1-2.1
== Step 1: Signing binaries at 2024-04-05T11:21:21:27+03:00 ==
== Step 2: Boot Jetson via RCM at 2024-04-05T11:21:44+03:00 ==
Found Jetson device in recovery mode at USB 1-2.1
== Step 3: Sending flash sequence commands at 2024-04-05T11:21:47+03:00 ==
Waiting for USB storage device flashpkg from ab340003..............

At the same time the output in UART console:

FATAL ERROR [FILE=platform/top/bpmp/startup/sku.c, ERR_UID=598]: chip sku 0xd5 not in <nv>/sku/te980m_0

 Jetson UEFI firmware (version v35.5.0 built on 2024-02-26T13:44:31+00:00)

▒▒ERROR: camera-ip/isp5/isp5.c:1980 [isp5_pm_init] "ERROR: Failed to turn isp power on"
BUG: core/init/init.c:85 [init_all] "*** FIRMWARE INIT FAILED AT LEVEL 95 ***"

And the flashing process freezes.

Any advice on what could be wrong?

[madisongh]

Looks like the wrong BPMP firmware got loaded. What hardware are you using, exactly, and which branch did you build off of? There was an issue I found during R35.5.0 testing with the initrd-flash script not using the right BPMP firmware for some Orin Nano/NX targets, but that should be fixed in the latest on both the kirkstone and master branches.

[didima7777]

I am using Orin Nano 8G.

All repositories in the master branch:

Entering '../repos/meta-openembedded'
* (HEAD detached from a6bcdca5b)
  master
Entering '../repos/meta-tegra'
* (HEAD detached from 95456f2f)
  master
Entering '../repos/meta-tegra-community'
* (HEAD detached at 7152b2f)
  master
Entering '../repos/meta-virtualization'
* (HEAD detached at 7a3b0b7a)
  master
Entering '../repos/poky'
* (HEAD detached from 110ee701b3)
  master

[didima7777]

I chechout all branches to kirkstone.

meta = "kirkstone:b6f6c729453cb88961488e3332046517e2fe99bb"
meta-tegra = "kirkstone:c106a81d515ba9d1aff2f9b9fb28e972e93fa97e"
meta-oe
meta-python
meta-networking
meta-filesystems = "kirkstone:8bb16533532b6abc2eded7d9961ab2a108fd7a5b"
meta-virtualization = "kirkstone:cb2bc17e96552cdfc141d27bd9f4dbd95a872846"
meta-tegra-community = "kirkstone:190add0d9106e98e33fcc24160a65b7a650124eb"
meta-tegra-support
meta-demo-ci
meta-tegrademo = "kirkstone:08c443dd9133e1dbd9aaf8f1e4c5c5f688117300"

Checked what is exposed in BOOTDEV with bitbake -e core-image-minimal | grep ^BOOT.
Got the following output:

BOOTPART_SIZE="8388608"
BOOT_PARTITIONS_ON_EMMC="0"
BOOTCONTROL_OVERLAYS="L4TConfiguration.dtbo"
BOOTDEV="nvme0n1p1"

Tried installing the image with sudo ./initrd-flash --skip-bootloader.
The result of the command execution:

Starting at 2024-04-08-08T11:24:53+03:00
Machine: jetson-orin-nano-devkit-nvme
Rootfs device: nvme0n1p1
Found Jetson device in recovery mode at USB 1-2.1
== Step 1: Signing binaries at 2024-04-08T11:24:53+03:00 ==
== Step 2: Boot Jetson via RCM at 2024-04-08-08T11:25:09+03:00 ==
Found Jetson device in recovery mode at USB 1-2.1
== Step 3: Sending flash sequence commands at 2024-04-08-08T11:25:12+03:00 ==
Waiting for USB storage device flashpkg from ab340003........[/dev/sdc]
Device size in blocks: 262144
Unmounted /dev/sdc.
== Step 4: Writing partitions on external storage device at 2024-04-08-08T11:25:38+03:00 ==
Waiting for USB storage device nvme0n1 from ab340003...[/dev/sdc].
Creating partitions
  [02] name=A_kernel start=0 size=262144 sectors
  [03] name=A_kernel-dtb start=0 size=1536 sectors
  [04] name=A_reserved_on_user start=0 size=64768 sectors
  [05] name=B_kernel start=0 size=262144 sectors
  [06] name=B_kernel-dtb start=0 size=1536 sectors
  [07] name=B_reserved_on_user start=0 size=64768 sectors
  [08] name=recovery start=0 size=163840 sectors
  [09] name=recovery-dtb start=0 size=1024 sectors
  [10] name=esp start=0 size=131072 sectors
  [11] name=recovery_alt start=0 size=163840 sectors
  [12] name=recovery-dtb_alt start=0 size=1024 sectors
  [13] name=esp_alt start=0 size=131072 sectors
  [14] name=UDA start=0 size=819200 sectors
  [15] name=reserved start=0 size=982016 sectors
  [01] name=APP (fills to end)
Writing partitions
  Writing boot.img (size=35491840) to /dev/sdc2 (size=134217728)...
  Writing kernel_tegra234-p3767-0003-p3768-0000-a0.dtb (size=347486) to /dev/sdc3 (size=786432)...
  Writing boot.img (size=35491840) to /dev/sdc5 (size=134217728)...
ERR: cannot locate block device /dev/sdc6
ERR: write failure to external storage at 2024-04-08-08T11:25:53+03:00

The boot up to selection of device boot, but nothing happens when selecting nvme.

[madisongh]

Sounds like something happened to the USB connection to the device part of the way through the process. Are there any errors in the kernel log on your host? And if you have a serial console connection on your dev kit, was there anything logged there during the process that might point to the problem?

[didima7777]

The following helped in solving the problem:

1. switch all repositories to kirkstone.
2. Rebuild the image
3. reboot the computer from which the flashing was done (PC had a uptime of more than 120 days).
   The operating system log showed USB buffer errors when accessing some disk partitions on Orin.

[madisongh]

If you were using our demo distro, I just noticed that I hadn't updated the master branch there with the latest commits in the meta-tegra layer. I've just done that and verified that an initrd-flash of my jetson-orin-nano-devkit-nvme works there now, too.