Not sure if this belongs here or purely in the installer, but the firmware side of it lives in this repo so filing it here too. Forum post with full details: https://forums.developer.nvidia.com/t/jetpack-7-2-1-iso-on-a-new-agx-thor-devkit-after-fixing-unsupported-board-install-fails-again-at-dtb-matching-and-leaves-nvme-unbootable-workaro/380595
New AGX Thor devkits ship with factory UEFI whose device tree identity predates the final product naming:
model: NVIDIA Jetson Thor Developer Kit (no "AGX")
compatible: nvidia,p4071-0080+p3834-0008 nvidia,p4071-0089+p3834-0008 nvidia,p3834-0008 nvidia,tegra264
The JetPack 7.2.1 ISO (r39.2.1) matches board identity by exact string comparison in two places, and both fail against this firmware:
detect_board_type() in jetsoniso_setup.bash expects exactly NVIDIA Jetson AGX Thor Developer Kit -> "Unsupported board!", install aborts. (Known: forum threads 373157, 374193.)- A late-command selects the kernel DTB by requiring fdtget model AND compatible of a shipped
/boot/*-nv*.dtb to equal the running DT. The only Thor devkit DTB in r39.2.1 is tegra264-p4071-0000+p3834-0008-nv.dtb (carrier p4071-0000), so it never matches p4071-0080/0089 -> "No matching -nv DTB found for running board" -> install dies after the rootfs is already written, leaving the NVMe unbootable. I believe this second one is unreported.
The module compat (p3834-0008) is identical on both sides, so it's a naming/SKU skew between firmware generations, not a hardware difference.
Worked around by patching the case statement and the DTB fallback in the live installer (details in the forum post); after that everything installed and boots fine.
Would it make sense to either (a) publish a capsule update so factory units report the current identity before OS install, or (b) have the installer match on module compat / EEPROM board ID instead of full exact strings? Right now a stock devkit plus the latest ISO cannot install without shell surgery.
Not sure if this belongs here or purely in the installer, but the firmware side of it lives in this repo so filing it here too. Forum post with full details: https://forums.developer.nvidia.com/t/jetpack-7-2-1-iso-on-a-new-agx-thor-devkit-after-fixing-unsupported-board-install-fails-again-at-dtb-matching-and-leaves-nvme-unbootable-workaro/380595
New AGX Thor devkits ship with factory UEFI whose device tree identity predates the final product naming:
The JetPack 7.2.1 ISO (r39.2.1) matches board identity by exact string comparison in two places, and both fail against this firmware:
detect_board_type()injetsoniso_setup.bashexpects exactlyNVIDIA Jetson AGX Thor Developer Kit-> "Unsupported board!", install aborts. (Known: forum threads 373157, 374193.)/boot/*-nv*.dtbto equal the running DT. The only Thor devkit DTB in r39.2.1 istegra264-p4071-0000+p3834-0008-nv.dtb(carrier p4071-0000), so it never matches p4071-0080/0089 -> "No matching -nv DTB found for running board" -> install dies after the rootfs is already written, leaving the NVMe unbootable. I believe this second one is unreported.The module compat (p3834-0008) is identical on both sides, so it's a naming/SKU skew between firmware generations, not a hardware difference.
Worked around by patching the case statement and the DTB fallback in the live installer (details in the forum post); after that everything installed and boots fine.
Would it make sense to either (a) publish a capsule update so factory units report the current identity before OS install, or (b) have the installer match on module compat / EEPROM board ID instead of full exact strings? Right now a stock devkit plus the latest ISO cannot install without shell surgery.