Jetson and edge boards

Jetson boards are two serialized things stacked together: the module (the SoM with the GPU and memory) and the carrier board it plugs into. A developer kit’s box carries a third number. They don’t have to match, and that trips people up.

From the running system

SSH into the board and read it out of the device tree:

tr -d '\0' < /proc/device-tree/serial-number; echo
tr -d '\0' < /proc/device-tree/model; echo

The tr strips the trailing NUL so the output doesn’t run into your prompt. model gives something like NVIDIA Jetson Orin Nano Developer Kit — that’s the Model field.

To confirm the JetPack/L4T version while you’re in there:

cat /etc/nv_tegra_release

The sticker

There’s a printed serial on the module label (visible once the heatsink/fan assembly is off, or on the module’s edge) and often a separate one on the carrier board and the dev-kit box.

The device-tree serial does not always match the S/N printed on the board or box — they’re EEPROM values from different components. Record the device-tree value as the Serial (it’s the one you can verify remotely at any time) and note the sticker number in the asset notes.

If /proc/device-tree/serial-number is missing on an older image, the value can be dumped from the carrier board’s EEPROM directly with i2cdump, but that’s a last resort — ask before poking at I²C on a running board.

Model field

Jetson Orin Nano Developer Kit, Jetson AGX Orin, and so on — use the name /proc/device-tree/model prints. Put the JetPack version and the carrier board in the notes; both matter when someone asks to borrow it for a project.

Practical notes

• These boards are usually headless and always on. Read the serial over SSH rather than pulling one out of a running setup.
• The power supply and the microSD/NVMe are part of the working unit. Note them on the asset — an Orin without its barrel-jack supply is a paperweight.