NVIDIA Jetson Orin Nano

For supported Jetson Orin Nano developer kits, current recovery releases install the boot firmware and OS together over USB. An NVMe-to-USB adapter is needed only for the separate rootfs-only workflow below.

For AGX Orin developer kits, choose jetson-agx-orin and select NVMe or eMMC. Custom robot carriers need their vendor's procedure. For Unitree G1 PC2, follow Install Wendy Agent on Unitree G1 and keep its vendor Ubuntu installation.

Full USB recovery

You need the developer kit and power supply, an NVMe SSD installed in the Orin Nano, a USB data cable, and a development machine with the current Wendy CLI (install it). AGX Orin can use its onboard eMMC instead of NVMe.

First inspect a read-only installation plan:

wendy install plan --device-type jetson-orin-nano --carrier developer-kit --storage nvme

For AGX Orin, pass --device-type jetson-agx-orin and explicitly choose --storage nvme or --storage emmc. The plan resolves the release and published recovery artifact. If the selected release has no recovery artifact, choose a recovery release or deliberately use compatible rootfs-only media; do not treat an old raw image as a full firmware recovery.

Full recovery erases QSPI and all partitions on the selected OS storage, including /data. Review that scope before running the returned command.

1. Connect the computer to the Jetson's recovery USB-C port using a data cable. On AGX Orin, use the USB-C port next to the 40-pin header.
2. On Orin Nano, disconnect power, bridge FC REC to GND (pins 9–10 on the button header under the module), then reconnect power. Remove the jumper after recovery mode is entered. Check the header labels for your board revision. On AGX Orin, hold Force Recovery, tap Reset/Power, then release Force Recovery.
3. Keep only the intended recovery-mode Jetson attached for unattended flashing. Run the planned command, or start wendy install and select full recovery. The CLI handles download, verification, host privileges and flash progress.
4. Keep power and USB attached through final success. Follow the installer’s reboot or power-cycle instruction to leave recovery mode.

Choose a first-boot device name and networking during setup. For explicit flags, use --device-name, WiFi preseed options, or --no-wifi for Ethernet. Optional --pre-enroll requires the intended Wendy Cloud login. See the installation command reference.

On macOS, the terminal may need Full Disk Access. wendy claims the flashing disks so macOS neither mounts them nor asks about unreadable disks; if such a prompt still appears, choose Ignore, not Initialize or Eject. On Windows, allow the installer's required driver/elevation step and cancel any request to format the newly attached raw disk. The installer reports these platform-specific steps.

Rootfs-only SD/NVMe imaging

Use this when the Jetson already has boot firmware compatible with the selected WendyOS release. This path does not update QSPI. Writing an image successfully does not prove the existing firmware can boot it.

Connect the SSD with an NVMe-to-USB adapter (or an SD card reader for a supported Orin Nano SD artifact), then inspect the host drives:

wendy os list-drives --all --json
wendy install plan --device-type jetson-orin-nano --carrier developer-kit \
  --rootfs-only --storage nvme --drive <confirmed-drive-path>

Review the path, model and capacity, then run the planned command. For AGX Orin, rootfs-only imaging supports NVMe; eMMC uses recovery. A recovery release must publish an explicit rootfs-only artifact for the requested storage.

After writing and ejecting, insert the SSD/card in the Jetson and power it on. The older NVMe adapter walkthrough illustrates physical media handling; it is not the full USB recovery procedure.

Verify first boot

Allow the board to boot, then discover it:

wendy discover --json
wendy install verify --address <expected-name-or-IP> \
  --expected-os-version <planned-version> --expected-device-type jetson-orin-nano

Use jetson-agx-orin for an AGX installation. Match the expected name/address, not an unrelated device from the discovery results. Record the returned public key for subsequent identity checks. Add --require-enrollment if cloud enrollment was requested. See agent-assisted setup for the equivalent MCP tools and a complete verification flow.

Continue with step 3 of the quickstart to create and run your first app, then inspect its container and logs and test its output. Flash completion, first boot and application readiness are separate checks.