Flashing failure with Jetson Linux 36.5 on Orin Nano

rahul.pp · March 17, 2026, 12:52pm

Hi,
@JerryChang
I am trying to flash NVIDIA Jetson Linux 36.5 build on an NVIDIA Jetson Orin Nano custom board.I am using the following flash command:

sudo BOARDID=3767 BOARDSKU=0003 FAB=300 ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1
-c tools/kernel_flash/flash_l4t_t234_nvme.xml -p “-c bootloader/generic/cfg/flash_t234_qspi.xml”
–flash-only --showlogs --network usb0 jetson-orin-nano-devkit internal

We also tried flashing with another image (JetPack 5.0, as far as I recall). With that image, the flashing was successful, and I was able to boot and log into the device. In that case, the system showed approximately 8GB RAM (free -h showed around 7.2 GB total).

For the current setup, the flashing logs are attached below, and the debug UART log shows the following output.

ORIN_NANO_Debug_uart.txt (25.2 KB)

FLASHING_log.txt (7.8 KB)

Could you please review the command and both logs and let me know if there is any issue with the flashing process?additional is there any change in board SKU or FAB
we have applied the change in bootloader file (Linux_for_Tegra/bootloader/tegra234-mb2-bct-common.dtsi) ( cvb_eeprom_read_size = <0x0>)

I would appreciate your guidance on resolving this issue.

JerryChang · March 18, 2026, 2:24am

hello rahul.pp,

per your flash logs, it waiting for device boot into forced-recovery mode,
however, here shows fatal error, which seems you’re flashing with incorrect board spec.
for instance,
bpmp: firmware tag is 40c4ded2a7425760713a-68f126a8abf
FATAL ERROR [FILE=platform/top/bpmp/startup/sku.c, ERR_UID=598]: chip sku 0xd5 not in <nv>/sku/te980m_0

rahul.pp · March 18, 2026, 3:32am

Hi,
@JerryChang
Thank you for your reply.
The system shows 8 GB RAM, so I set the BOARDSKU value to 0003. Could you please confirm whether 0003 is the correct SKU for the Jetson Orin Nano 8GB variant?
I used the following command for flashing:

sudo BOARDID=3767 BOARDSKU=0003 FAB=300 ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_t234_nvme.xml -p “-c bootloader/generic/cfg/flash_t234_qspi.xml” --flash-only --showlogs --network usb0 jetson-orin-nano-devkit internal

However, when using the mass flash command,

sudo BOARDID=3767 BOARDSKU=0003 FAB=300 ./tools/kernel_flash/l4t_initrd_flash.sh --no-flash --massflash 1 --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml -p “-c bootloader/generic/cfg/flash_t234_qspi.xml” --showlogs --network usb0 jetson-orin-nano-devkit external

Could you please let me know if there is any problem with these commands or if any configuration needs to be changed?

JerryChang · March 18, 2026, 5:38am

hello rahul.pp,

this looks incorrect.

you may refer to ota_board_specs.conf,
let me re-cap as below..

        # orin-nano 8GB
        'boardid=3767;fab=000;boardsku=0003;boardrev=;fuselevel_s=1;chiprev=;chipsku=00:00:00:D5;board=jetson-orin-nano-devkit;rootdev=nvme0n1p1;bup_type=bl;signed_img_dir=images-R36-ToT'
        # orin-nano devkit 8GB
        'boardid=3767;fab=000;boardsku=0005;boardrev=;fuselevel_s=1;chiprev=;chipsku=00:00:00:D5;board=jetson-orin-nano-devkit;rootdev=nvme0n1p1;bup_type=bl;signed_img_dir=images-R36-ToT'

hence..
please try.. BOARDID=3767 BOARDSKU=0003 FAB=000 for your flash commanad-line.

rahul.pp · March 18, 2026, 6:27am

Hi
@junglist_94
I tried the suggested flashing command, but I am still encountering the same issue.
command:

sudo BOARDID=3767 BOARDSKU=0003 FAB=000 ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1
-c tools/kernel_flash/flash_l4t_t234_nvme.xml -p “-c bootloader/generic/cfg/flash_t234_qspi.xml”
–flash-only --showlogs --network usb0 jetson-orin-nano-devkit internal

And the logs are the same as the previous ones.

I> Task: Trigger mailbox for PSC-BL1 exit
I> Sending opcode 0x4d420802 to psc
I> Received ACK from psc
I> Task: Trigger load FSI keyblob
I> Task: Complete load FSI keyblob
I> Task: MB2-PSC_FW Key Manager Init
I> Sending opcode OP_PSC_KEY_MANAGER to psc-fw
I> Sending opcode 0x4b45594d to psc
I> Received ACK from psc
I> Task: Unhalt FSI
I> FSI unhalt s��
��kipped
I> ��hwwdt_init: WDT boot cfg 0x710010 sts 0x10
bpmp: socket 0
bpmp: base binary md5 is 68f126a8abf720445275b10ce9dac080
bpmp: combined binary md5 is 40c4ded2a7425760713ad44d43893afd
bpmp: firmware tag is 40c4ded2a7425760713a-68f126a8abf

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

Is there any configuration mismatch? We have already worked with one Orin Nano where JetPack 5.1 (L4T 35.3.1) was flashed successfully on the same hardware. This issue is occurring only with the latest SDK version (36.5).

JerryChang · March 18, 2026, 11:03am

hello rahul.pp,

may I know what’s the command you used to flash that target before?

rahul.pp · March 18, 2026, 12:12pm

@JerryChang

sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml -p “-c bootloader/t186ref/cfg/flash_t234_qspi.xml” --flash-only --showlogs --massflash 1 --network usb mfi_jetson-orin-nano-devkit internal

I used the same flashing command with the latest SDK build, but it is not working.

JerryChang · March 18, 2026, 1:45pm

hello rahul.pp,

FYI,
board name has changed to generic for JP-6 public release version,
for instance, $OUT/Linux_for_Tegra/bootloader/generic

besides.. you should have image creation and then running with --flash-only
please refer to readme file, tools/kernel_flash/README_initrd_flash.txt for [Workflow 2: How to generate images first and flash the target later]

rahul.pp · March 24, 2026, 5:12am

Hi @JerryChang

Thank you for your support.

I downloaded the SDK 36.5 build on my personal laptop and successfully flashed the image to the SOM. It is working fine.

I used the following command:

sudo BOARDID=3767 BOARDSKU=0003 FAB=100 BOARDREV=A.0 ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_t234_nvme.xml -p “-c bootloader/generic/cfg/flash_t234_qspi.xml” --showlogs --network usb0 jetson-orin-nano-devkit internal

Now, we need to create a mass-flash build (image package) so that we can transfer the generated images from the VM to a personal PC and flash multiple devices.

I tried the following command:

sudo BOARDID=3767 BOARDSKU=0003 FAB=100 BOARDREV=A.0 ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1
-c tools/kernel_flash/flash_l4t_t234_nvme.xml -p “-c bootloader/generic/cfg/flash_t234_qspi.xml”
–no-flash --showlogs --network usb0 --massflash 1 jetson-orin-nano-devkit internal

However, it is not working. I am encountering the following error:

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

I also faced the same issue previously when attempting to create the mass-flash package.
Could you please guide me on the correct steps or command to generate and use the mass-flash build?
Thanks in advance.

JerryChang · March 24, 2026, 6:13am

hello rahul.pp,

let me double check your rootdev, where is your root file system?
if you flash an NVMe SSD and use APP partition on it as root filesystem, you should use nvme0n1p1 as your rootdev.
you may see-also README_initrd_flash.txt, please check [Workflow 4].

abhiram.m · March 24, 2026, 10:20am

Hi @JerryChang ,

the rootdev is in NVME ,

we have tried to generate the image in 2 different ways

From personal laptop using the command
sudo BOARDID=3767 BOARDSKU=0003 FAB=100 BOARDREV=A.0 ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_t234_nvme.xml -p “-c bootloader/generic/cfg/flash_t234_qspi.xml” --showlogs --network usb0 jetson-orin-nano-devkit internal
which will generate the system image and starts flashing to device where i was able to flash the device.
We tried to create a tar file using the below command in a VM server , scp the tar package to our PC
sudo BOARDID=3767 BOARDSKU=0003 FAB=100 BOARDREV=A.0 ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1
-c tools/kernel_flash/flash_l4t_t234_nvme.xml -p “-c bootloader/generic/cfg/flash_t234_qspi.xml”
–no-flash --showlogs --network usb0 --massflash 1 jetson-orin-nano-devkit internal
then we tried flashing the firmware using the below command
sudo BOARDID=3767 BOARDSKU=0003 FAB=100 BOARDREV=A.0 ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1
-c tools/kernel_flash/flash_l4t_t234_nvme.xml -p “-c bootloader/generic/cfg/flash_t234_qspi.xml”
–-flash-only --showlogs --network usb0 jetson-orin-nano-devkit internal
which ended up in same issue
FATAL ERROR [FILE=platform/top/bpmp/startup/sku.c, ERR_UID=598]: chip sku 0xd5 not in /sku/te980m_0
COuld you please look into it and provide further step by step instruction and procedure as we are stuck here .

rahul.pp · March 26, 2026, 6:20am

Hi @JerryChang

Gentle reminder : kindly provide your guidance on the above query…

JerryChang · March 30, 2026, 2:33am

hello abhiram.m,

that should be an issue with your environment setup, FYI, we usually works with native ubuntu host for image flashing.

you should based-on your 1st approach (from personal laptop) by adding --massflash commands to create a mass-flash build (image package).

abhiram.m · March 30, 2026, 4:36am

HI @JerryChang ,

We have tried in our personal laptp by adding –massflash 1

sudo BOARDID=3767 BOARDSKU=0003 FAB=100 ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1
-c tools/kernel_flash/flash_l4t_t234_nvme.xml -p “-c bootloader/generic/cfg/flash_t234_qspi.xml”
–no-flash --showlogs --network usb0 --massflash 1 jetson-orin-nano-devkit internal

where i was ale to get a .tar file ,
but the flashing to image ends up in failure when i used
sudo BOARDID=3767 BOARDSKU=0003 FAB=100 BOARDREV=A.0 ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1
-c tools/kernel_flash/flash_l4t_t234_nvme.xml -p “-c bootloader/generic/cfg/flash_t234_qspi.xml”
–-flash-only --showlogs --network usb0 jetson-orin-nano-devkit internal

**FATAL ERROR [FILE=platform/top/bpmp/startup/sku.c, ERR_UID=598]: chip sku 0xd5 not in /sku/te980m_0
**
seems its not issue with build environment as the local PC was able to flash directly to board by using
**sudo BOARDID=3767 BOARDSKU=0003 FAB=100 BOARDREV=A.0 ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_t234_nvme.xml -p “-c bootloader/generic/cfg/flash_t234_qspi.xml” --showlogs --network usb0 jetson-orin-nano-devkit internal

**
but when tried to create a .tar file … while flashing the issue raises

what can be done in order to bypass this issue

JerryChang · March 30, 2026, 4:45am

hello abhiram.m,

there should flashcmd.txt within the massflash package.
please try extract the mfi package, (i.e. mfi_jetson-orin-nano-devkit.tar.gz), and then running flash commands directly.

Topic		Replies	Views
NVIDIA flashing issue Jetson Orin Nano reflash	3	116	April 17, 2026
Orin Nano doesn't boot after flashing Jetson Orin Nano boot , board-design	9	283	August 28, 2025
Flash only flashing method to flash Jetson Orin nano Jetson Orin Nano jetson , flash	3	205	September 4, 2025
Jetson orin nano p3767-0003 flash failed Jetson Orin Nano reflash	2	160	September 8, 2025
Can not flash or boot Orin Nano 8gb developer kit to SD or nvme Jetson Orin Nano reflash	19	1176	February 24, 2024
Jetson Linux 36.3 : after flashing Orin Nano，It turns out to be Orin NX Jetson Orin Nano boot	11	265	May 19, 2025
Jetson orin nano - Flashing with initrd Jetson Orin Nano reflash	7	372	September 19, 2025
Problems flashing Orin Nano to NVME Jetson Orin Nano reflash	7	495	May 21, 2024
Jetson Nano Orin wont Flash Jetson Orin Nano reflash	3	105	November 11, 2025
Flashing L4T 36.2 on orin Nano/NX Jetson Orin Nano reflash	2	1133	January 5, 2024

Flashing failure with Jetson Linux 36.5 on Orin Nano

Related topics