Flashing Failed Due to Different SKU Error on Custom Jetson Orin Nano Board

Robotics & Edge Computing Jetson Systems Jetson Orin Nano
,
1

Hi Team,

We created an image for the NVIDIA Jetson Orin Nano EVK with the required changes for our custom board.

Now, while flashing the same image on our custom-designed board, we are getting below error.

root@AHMCPU2026:# ./initrd-flash
Starting at 2026-09-24T14:44:02+05:30
Machine:       jetson-orin-nano-devkit-nvme
Rootfs device: nvme0n1p1
Found Jetson device in recovery mode at USB 3-2
== Step 1: Signing binaries at 2026-09-24T14:44:02+05:30 ==
ERR: actual board SKU 0003 does not match expected board SKU 0005
ERR: signing failed at 2026-09-24T14:44:07+05:30

Could you please explain why the SKU mismatch occurs between the EVK and our custom board, even though our custom board uses the same NVIDIA Jetson Orin Nano SoM, and advise how we can overcome this issue to successfully build and flash the image for custom board?

Note:- We have quickly checked by exporting SKU value forcefully and then re-run command “./initrd-flash” in that case we are able to flash the custom-board with EVK image.

export BOARDSKU=0005
./initrd-flash

Log:-

root@AHMCPU2026:/test/untar# export BOARDSKU=0005
root@AHMCPU2026:/test/untar# ./initrd-flash
Starting at 2026-09-24T14:45:48+05:30
Machine:       jetson-orin-nano-devkit-nvme
Rootfs device: nvme0n1p1
Found Jetson device in recovery mode at USB 3-2
== Step 1: Signing binaries at 2026-09-24T14:45:48+05:30 ==
/home/einfochips/Nisarg-Temp/Customer-Repo-Build/test/untar/odmsign.func: line 161: [: : integer expression expected
/home/einfochips/Nisarg-Temp/Customer-Repo-Build/test/untar/odmsign.func: line 504: [: : integer expression expected
/home/einfochips/Nisarg-Temp/Customer-Repo-Build/test/untar/odmsign.func: line 510: [: : integer expression expected
/home/einfochips/Nisarg-Temp/Customer-Repo-Build/test/untar/odmsign.func: line 161: [: : integer expression expected
/home/einfochips/Nisarg-Temp/Customer-Repo-Build/test/untar/odmsign.func: line 504: [: : integer expression expected
/home/einfochips/Nisarg-Temp/Customer-Repo-Build/test/untar/odmsign.func: line 510: [: : integer expression expected
/home/einfochips/Nisarg-Temp/Customer-Repo-Build/test/untar/odmsign.func: line 300: [: : integer expression expected
== Step 2: Boot Jetson via RCM at 2026-09-24T14:46:14+05:30 ==
Found Jetson device in recovery mode at USB 3-2
== Step 3: Sending flash sequence commands at 2026-09-24T14:46:18+05:30 ==
Waiting for USB storage device flashpkg from 135c6097......[/dev/sdb]
Device size in blocks: 262144
Unmounted /dev/sdb.
== Step 4: Writing partitions on external storage device at 2026-09-24T14:46:37+05:30 ==
Waiting for USB storage device nvme0n1 from 135c6097...[/dev/sdb]
Creating partitions
  [03] name=A_kernel start=0 size=262144 sectors
  [04] name=A_kernel-dtb start=0 size=1536 sectors
  [05] name=A_reserved_on_user start=0 size=64768 sectors
  [06] name=B_kernel start=0 size=262144 sectors
  [07] name=B_kernel-dtb start=0 size=1536 sectors
  [08] name=B_reserved_on_user start=0 size=64768 sectors
  [09] name=recovery start=0 size=163840 sectors
  [10] name=recovery-dtb start=0 size=1024 sectors
  [11] name=esp start=0 size=131072 sectors
  [12] name=recovery_alt start=0 size=163840 sectors
  [13] name=recovery-dtb_alt start=0 size=1024 sectors
  [14] name=esp_alt start=0 size=131072 sectors
  [15] name=UDA start=0 size=819200 sectors
  [16] name=reserved start=0 size=982016 sectors
  [01] name=APP start=0 size=10485760 sectors
  [02] name=APP_b start=0 size=10485760 sectors
  [17] name=DATA start=0 size=204800 sectors
Writing partitions
  Writing boot.img (size=46764032) to /dev/sdb3 (size=134217728)...
  Writing kernel_tegra234-p3768-0000+p3767-0005-nv-super.dtb (size=249353) to /dev/sdb4 (size=786432)...
  Writing boot.img (size=46764032) to /dev/sdb6 (size=134217728)...
  Writing kernel_tegra234-p3768-0000+p3767-0005-nv-super.dtb (size=249353) to /dev/sdb7 (size=786432)...
  Writing esp.img (size=67108864) to /dev/sdb11 (size=67108864)...
  Writing hm-image.ext4 (size=5368709120) to /dev/sdb1 (size=5368709120)...
  Writing hm-image.ext4 (size=5368709120) to /dev/sdb2 (size=5368709120)...
[OK: /dev/sdb]
== Step 5: Waiting for final status from device at 2026-09-24T14:52:31+05:30 ==
Waiting for USB storage device flashpkg from 135c6097...[/dev/sdb]
Unmounted /dev/sdb.
Final status: SUCCESS
Successfully finished at 2026-09-24T14:52:34+05:30
Host-side log:              log.initrd-flash.2026-09-24-14.45.48
Device-side logs stored in: device-logs-2026-09-24-14.45.48
root@AHMCPU2026:/test/untar#

Thanks,
Nisarg

4

Hi team, Any update on this ? Please provide details on it.

5

Hi @nisarg.prajapati ,

The error indicates that the flash package expects module SKU 0005, while the device connected in recovery mode reports SKU 0003. BOARDSKU refers to the Jetson module, so the custom carrier board alone does not explain the mismatch. NVIDIA lists both SKUs as Orin Nano 8 GB modules, but they are distinct module variants.

Could you confirm the part number printed on the module installed on your custom board, and how the flash package was generated? That will establish which SKU the package should target. Setting BOARDSKU=0005 allowed flashing to complete, but the log shows that it wrote a p3767-0005 DTB; I would also verify that the resulting image boots and uses the intended configuration for your carrier board.

Once the module SKU is confirmed, regenerate the flash package for that module and your carrier board configuration. NVIDIA’s Orin NX/Nano adaptation guide covers the board changes. If you are building with Yocto, RidgeRun’s device tree customization guide explains how the selected DTB is included in the flash bundle.

6

Hi @juanignava , Please check below details we have found on SoM Packaging.

P/N:- 175-0877-000

Image-3
Image-34032×3024 949 KB

Please check above details and provide solution so we can use EVK changes directly flash into Custom design board (Using SoM).

Thanks,

Nisarg

8

Hi Team, any update on this ?

9

Thanks for the photo. I can see P/N: 175-0877-000 on the packaging, but I cannot determine the module SKU from that marking alone. Could you share the full part number from the label on the SoM, or the module EEPROM information reported by the flashing tools?

The current log shows that the connected device reports SKU 0003, while the flash package was prepared for 0005. Forcing BOARDSKU=0005 lets the flash finish, but the log still shows a p3767-0005 DTB being written. Could you also confirm whether the board boots and whether its NVMe and other interfaces work afterward?

10

Hi @juanignava , Below details we have found on SOM Module.

NVIDIA

S TW 2538A1

SNWA37.MOP (e2)

TE960M-A1

Please check above details; Also we have checked after flashing image we are able to boot the board and NVMe SSD working and able to access Linux-console.

11

Hi @juanignava , Any update on this ?