Skip to content

Instantly share code, notes, and snippets.

@j0ju
Created May 15, 2026 21:40
Show Gist options
  • Select an option

  • Save j0ju/281594da20d9e24a99f70ce6e5bc734d to your computer and use it in GitHub Desktop.

Select an option

Save j0ju/281594da20d9e24a99f70ce6e5bc734d to your computer and use it in GitHub Desktop.
Turing Pi2: Orin NX (node1) Flashing via RK1 (node4)

prerequisites

get from https://developer.nvidia.com/embedded/jetson-linux-r365

  • Jetson_Linux_R36.5.0_aarch64.tbz2
  • sdkmanager_2.4.0-13236_arm64.deb
  • Tegra_Linux_Sample-Root-Filesystem_R36.5.0_aarch64.tbz2

preperation

Turing Pi2

place RK1 or CM4 into Node4 place Nvidia Orin NX in node 1

packages

I am using Debian Trixie. I needed to install

  • qemu-user-static:arm64 - Jetpack is a mix of x86_64 and aarch64 binaries
  • uuid-runtime
  • lz4
  • zstd
  • squashfs-tools
  • cpio
  • device-tree-compiler
  • python3
  • lzop

SDK, images, flashing tools on node 4

  • extract Jetson_Linux_R36.5.0_aarch64.tbz2 to ./Linux_for_Tegra
  • extract Tegra_Linux_Sample-Root-Filesystem_R36.5.0_aarch64.tbz2 to ./Linux_for_Tegra/rootfs USE sudo
tar xf Jetson_Linux_R36.5.0_aarch64.tbz2
sudo tar xf Tegra_Linux_Sample-Root-Filesystem_R36.5.0_aarch64.tbz2 -C Linux_for_Tegra/rootfs/ --acl --xattrs

patch SDK for TuringPi2 which has no EEPROM

cd ./Linux_for_Tegra
sed -i 's/cvb_eeprom_read_size = <0x100>/cvb_eeprom_read_size = <0x0>/g' ./bootloader/generic/BCT/tegra234-mb2-bct-misc-p3767-0000.dts

patch SDK for newer ssh-keygen without DSA support

JetPack assumes a ssh-keygen which includes DSA support which was remove in noble and trixie. It will silently cause the image generation to fail, as the script uses the redirection 1> /dev/null 2>&1.

sed -i -e  '/ssh-keygen -t dsa/ d' ./tools/ota_tools/version_upgrade/ota_make_recovery_img_dtb.sh

prepare rootfs

cd ./Linux_for_Tegra
sudo ./apply_binaries.sh
sudo ./tools/l4t_flash_prerequisites.sh

add default user

sudo ./tools/l4t_create_default_user.sh -u orin -p orin -a -n orin

connection

For 2.4 Turing Pi2 Board

  • connect A-A USB cable from node 4 to node 1
  • run on BMC
tpi -p off             # (turns off all nodes)
tpi -u device -n 1     # put node1 into device mode
tpi -p on              # (turns on all nodes)

For 2.5.x Turing Pi2 Board

  • connect one USB A Port of Node 4 to USB-C Port of Node 1

flash

inspired by https://forums.developer.nvidia.com/t/jp5-1-5-how-to-enable-super-mode-on-orin-nx/345890/6

sudo ADDITIONAL_DTB_OVERLAY_OPT="BootOrderNvme.dtbo" ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -p "-c ./bootloader/generic/cfg/flash_t234_qspi.xml" -c ./tools/kernel_flash/flash_l4t_t234_nvme.xml --showlogs --network usb0  jetson-orin-nano-devkit-super internal

This flashes an Orin NX 16GB into "super" configuration with 40W and 157 TOPS

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment