Flashing fails-Board ID not found

Robotics & Edge Computing Jetson Systems Jetson Orin NX
1

We have a Jetson Orin NX 16GB module that can be recognized as an Nvidia APX device. However, when we start the flashing process, the board ID and SKU information cannot be detected.

What could be the possible causes of this issue? Is there any way to recover it?

image
image1020×580 40.5 KB

QSPI_flash_log.txt (13.8 KB)

5

Hi,

It seems you’re not using our official script. Are you working with a developer kit or a custom board?
If you’re using a developer kit, please install the SDK Manager to flash the device.

Thanks

6

Hi, David

We are using our custom board. The NVIDIA script needs to be executed with additional parameters.
We have wrapped it with our own layer, but in the end it still executes the NVIDIA script.

7

Hi, David

Our flashing command shows below

sudo ./flash.sh --read-info jetson-orin-nano-devkit-super internal

Additionally, we have attached the logs from both the host and the device.

Flashing_Log_Host.txt (10.4 KB)

Flashing_Log_Device.txt (4.1 KB)

8

Hi,

Please refer to the section and run related commands to check the board ID.

Thanks

9

Hi, David

I followed the instructions from the link above and used the command below to perform the flashing.

sudo ./flash.sh jetson-orin-nano-devkit mmcblk0p1

However, the issue is the same as before. It gets stuck after the following log and then keeps waiting indefinitely.

[ 0.4478 ] Sending applet
[ 0.5529 ] completed
[ 0.5545 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet

This Orin module showed this behavior after testing—would it be possible to recover it through software methods?

flash_log_20260415.txt (12.5 KB)

10

Hi,

Have you put the device in recovery mode before running commands?

Thanks

11

Hi, David

I do. If the device is not under recovery mode, probing target board will be failed.

image
image840×273 70.8 KB

12

Hi,

Please follow the steps below and capture the serial console log if the system still hangs.

  1. Place the Jetson target into recovery mode.
  2. Run this command to generate bootloader/cvm.bin and bootloader/chip_info.bin_bak:
$ sudo ./flash.sh --no-flash --no-systemimg  jetson-orin-nano-devkit mmcblk0p1
  1. Retrieve the environment variables above using these commands:
$ cd bootloader
$ BOARDID=$(./chkbdinfo -i cvm.bin)
$ BOARDSKU=$(./chkbdinfo -k cvm.bin)
$ FAB=$(./chkbdinfo -f cvm.bin)
$ BOARDREV=$(./chkbdinfo -r cvm.bin)
$ CHIP_SKU=$(./chkbdinfo -C chip_info.bin_bak)
$ RAMCODE_ID=$( ./chkbdinfo -R chip_info.bin_bak)
$ RAMCODE=$(echo "ibase=2; ${RAMCODE_ID//:/}" | bc)

To record the serial log, please refer

Thanks