Reading board ID, fab, SKU, and rev

Robotics & Edge Computing Jetson Systems Jetson Orin NX
1

I have an Orin NX module on a ConnectTech Hadron carrier board. I’m trying to follow the instructions in README_initrd_flash.txt:

Without device connected (offline mode):
Run this command from the Linux_for_Tegra folder to generate flash images:

$ sudo BOARDID=<BOARDID> FAB=<FAB> BOARDSKU=<BOARDSKU> > BOARDREV=<BOARDREV> \
./tools/kernel_flash/l4t_initrd_flash.sh --no-flash <board-name> <rootdev>

I would like to determine the value of BOARDID etc. from the attached device so that I can produce images for it offline in the future.

Notably, there is an appendix in this file that lists the values for some boards, but jetson-agx-orin-devkit appears 3 times.

Board Name BOARDID BOARDSKU FAB BOARDREV
jetson-agx-xavier-industrial 2888 0008 600 A.0
clara-agx-xavier-devkit 3900 0000 001 C.0
jetson-xavier-nx-devkit 3668 0000 100 N/A
jetson-xavier-nx-devkit-emmc 3668 0001 100 N/A
jetson-xavier-nx-devkit-emmc 3668 0003 N/A N/A
jetson-agx-xavier-devkit (16GB) 2888 0001 400 H.0
jetson-agx-xavier-devkit (32GB) 2888 0004 400 K.0
jetson-agx-orin-devkit 3701 0001 TS1 C.2
jetson-agx-orin-devkit 3701 0000 TS4 A.0
jetson-agx-xavier-devkit (64GB) 2888 0005 402 B.0
holoscan-devkit 3701 0002 TS1 A.0
jetson-agx-orin-devkit 3701 0004 TS4 A.0

But I cannot figure out how to query it directly. For example:

$ sudo ./nvautoflash.sh --print-boardid
*** Checking ONLINE mode ... OK.
*** Checking target board connection ... 1 connections found.
*** Reading ECID ... *** Error: ECID read failed.
Put the target board in RCM mode and retry.

(The read fails because tegrarcm_v2 --uid --new_session --chip 0x23 returns exit code 16.)

When I run l4t_initrd_flash.sh --showlogs it outputs blanks:

Board ID() version() sku() revision()
Chip SKU() ramcode() fuselevel(fuselevel_production) board_FAB()

Some previous discussion here concluded that BOARDREV is not important, but doesn’t explain how the device’s EEPROM was read.

2

./nvautoflash.sh --print-boardid is the correct command, however I am running on ARM and the L4T binaries are only provided for x86_64, so they were running under QEMU emulation.

$ sudo QEMU_GUEST_BASE=0 ./nvautoflash.sh --print-boardid
...
Parsing module EEPROM:
--- Parsing board ID (3767) succeeded.
--- Parsing board version (500) succeeded.
--- Parsing board SKU (0000) succeeded.
./nvautoflash.sh: line 505: warning: command substitution: ignored null byte in input
--- Parsing board REV () succeeded.

There is an inconsistency here, “version” in the above response is the same as FAB.