NVIDIA flashing issue

Robotics & Edge Computing Jetson Systems Jetson Orin Nano
1

Hi @JerryChang
I was trying to flash the 36.5 SDK for Orin nano, I was able to compile successfully
I tried to flash the device using
sudo BOARDID=3767 BOARDSKU=0003 FAB=300 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 was not able to flash the board
sudo BOARDID=3767 BOARDSKU=0003 FAB=300 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
Please install the Secureboot package to use initrd flash for fused board

Entry added by NVIDIA initrd flash tool

/home/abalu/36.5/Linux_for_Tegra/tools/kernel_flash/tmp 127.0.0.1(rw,nohide,insecure,no_subtree_check,async,no_root_squash)
rpcbind: another rpcbind is already running. Aborting
Export list for localhost:
/home/abalu/36.5/Linux_for_Tegra/tools/kernel_flash/tmp 127.0.0.1
12:50:08.500 - Debug: Checking UFW status and NFS port rules…
12:50:08.774 - Debug: UFW is not active. NFS port is accessible.
12:50:08.775 - Debug: Checking VPN connections…
12:50:08.779 - Debug: IPSec service is not running.
12:50:08.780 - Debug: VPN routes none in tun|tap|ppp|vpn|gpd.
12:50:08.781 - Debug: No VPN connection detected.
/home/abalu/36.5/Linux_for_Tegra/tools/kernel_flash/l4t_initrd_flash_internal.sh --no-flash --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

  •                              *

  • Step 1: Generate flash packages *

  •                              *

Create folder to store images to flash
Generate image for internal storage devices
/home/abalu/36.5/Linux_for_Tegra/tools/kernel_flash/l4t_create_images_for_kernel_flash.sh: line 517: [: : integer expression expected
Generate images to be flashed
ADDITIONAL_DTB_OVERLAY=“” /home/abalu/36.5/Linux_for_Tegra/flash.sh --no-flash --sign -c bootloader/generic/cfg/flash_t234_qspi.xml jetson-orin-nano-devkit internal

###############################################################################

L4T BSP Information:

R36 , REVISION: 5.0

User release: 0.0

###############################################################################
ECID is 0x80012344705DE7468C00000010008300
Board ID(3767) version(300) sku(0003) revision(A.0)
Preset RAMCODE is
Parsing chip_info.bin information failed.
Error: failed to generate images
Cleaning up…

could you please help in this case?

What is causing this issue

3

*** Please note that this reply is generated by LLM automatically ***

The issue you’re experiencing is due to the fact that the Jetson Orin Nano board you’re trying to flash is fused, and the initrd flash tool requires the Secureboot package to be installed in order to work with fused boards.

The error message you’re seeing, “Please install the Secureboot package to use initrd flash for fused board,” is a clear indication of this requirement.

To resolve this issue, you’ll need to install the Secureboot package on your host machine. The Secureboot package is a set of tools and utilities that enable secure boot on NVIDIA Jetson devices.

Here are the steps to install the Secureboot package:

  1. Download the Secureboot package from the NVIDIA website.
  2. Extract the package to a directory on your host machine.
  3. Follow the instructions in the package’s README file to install the Secureboot tools.

Once you’ve installed the Secureboot package, you should be able to use the initrd flash tool to flash your Jetson Orin Nano board.

Additionally, you may need to update your flash command to include the Secureboot options. For example:

sudo BOARDID=3767 BOARDSKU=0003 FAB=300 BOARDREV=A0 \
  ./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 --secureboot \
  jetson-orin-nano-devkit internal

The --secureboot option tells the initrd flash tool to use the Secureboot package to flash the board.

If you’re still experiencing issues after installing the Secureboot package and updating your flash command, you may want to try resetting the board to its default state by running the following command:

sudo ./tools/kernel_flash/l4t_initrd_flash.sh --reset \
  jetson-orin-nano-devkit internal

This will reset the board to its default state, and you can then try flashing it again using the initrd flash tool.

In comparison to other flash commands, the one you’re using is specific to the Jetson Orin Nano board and includes options for flashing the board with a specific configuration file (flash_l4t_t234_nvme.xml) and using the Secureboot package.

For example, the flash command for the Jetson AGX Orin board would be different and would not include the --secureboot option:

sudo BOARDID=<board_id> FAB=<fab> BOARDSKU=<sku_number> BOARDREV=<reversion> \
  ./flash.sh --no-flash -u pv_priv.pem -k A_cpu-bootloader \
  jetson-agx-orin-devkit internal

Similarly, the flash command for the Jetson Orin NX board would be different and would not include the --secureboot option:

sudo ./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-nx-devkit internal

In summary, the issue you’re experiencing is due to the fact that the Jetson Orin Nano board you’re trying to flash is fused, and the initrd flash tool requires the Secureboot package to be installed in order to work with fused boards. Installing the Secureboot package and updating your flash command to include the --secureboot option should resolve the issue.

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***

5

hello abhiram.m,

here shows the failure.

it might be something wrong with your flash commands,
please refer to developer guide, To Flash the Jetson Developer Kit Operating Software.

BTW,
is it a customize board?
if yes.. please try modify the MB2 BCT file.
for instance, $OUT/Linux_for_Tegra/bootloader/tegra234-mb2-bct-common.dtsi

- cvb_eeprom_read_size = <0x100> 
+ cvb_eeprom_read_size = <0x0>
7

That line is an issue in nvidia’s script.
[ “${hsm_enable}” -eq 1 ]

if you don’t supply --hsm to the script, then the variable is not initialized, making the expression [ “” -eq 1 ], which fails with the “integer expression expected” error.

You just need to fix it by actually initializing the variable to zero.
Add hsm_enable=0 on line 567 (right after gen_read_ramcode=0 on line 566)