> For the complete documentation index, see [llms.txt](https://docs.holybro.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.holybro.com/autopilot/pixhawk-baseboards/pixhawk-jetson-baseboard/flashing-guide.md).

# Flashing guide

{% hint style="info" %}
Note: There are scripts to help you do the necessary basic setup after flashing Jetson on Holybro's Github page:

&#x20;<https://github.com/Holybro/holybro-jetson-companion>
{% endhint %}

{% hint style="info" %}
Currently, the Holybro Jetson baseboard only supports Jetpack versions 5.1.2 to 6.0 and 6.2.2.
{% endhint %}

Two methods to flash the board:

## SDK Manager:

This is a GUI-based solution by Nvidia which can be found from the link below:\
\
<https://docs.nvidia.com/sdk-manager/install-with-sdkm-jetson/index.html>

**Note:** Keep in mind that at the time of writing this document, we chose to install Jetpack 5.1.2.

#### Extra procedure for Jetpack 6.2.2

For Jetpack version 6.2.2, a patch is required to install on the host computer.

Download the .rar file below and move/replace the existing file in **nvidia->nvidia\_sdk->JetPack\_6.2.2\_Linux\_JETSON\_ORIN\_NX\_TARGETS.**

{% file src="/files/OXY1UMOFTYiWFeh8HgCa" %}

{% hint style="info" %}
If the folder is not present, try flashing the Jetson once, and the SDK should create the folder
{% endhint %}

## Command Line:

You could benefit from [Nvidia flash guide](https://docs.nvidia.com/jetson/archives/r35.3.1/DeveloperGuide/text/IN/QuickStart.html#to-flash-the-jetson-developer-kit-operating-software) .&#x20;

{% hint style="info" %}
The difference here is you need to change the DIP switch on the carrier board to REC to boot in recovery mode.&#x20;

<img src="https://2367252986-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLIgtGDAvVGkCKGOJb1bR%2Fuploads%2F3OV1ODpUhk3RJ04U8Fl9%2Fimage.png?alt=media&amp;token=faa581b9-0c08-47bc-95da-4dd643a1c481" alt="" data-size="original">![](https://2367252986-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLIgtGDAvVGkCKGOJb1bR%2Fuploads%2F2nRPtcWBtR7krSQiitPX%2FCleanShot%202024-05-31%20at%2018.27.04.png?alt=media\&token=f726c613-9426-459c-884a-de7a45d17a27)
{% endhint %}

### Patched Jetpack 6.2.2 Command Line Procedure

{% file src="/files/CMw2Rc9DuMdfiFUHwqP8" %}

1. Connect the Jetson to an Ubuntu 20.04/22.04 PC
2. Download the system image package with the following command

   ***wget <https://developer.nvidia.com/downloads/embedded/l4t/r36\\_release\\_v5.0/release/Jetson\\_Linux\\_r36.5.0\\_aarch64.tbz2>***

   ***wget <https://developer.nvidia.com/downloads/embedded/l4t/r36\\_release\\_v5.0/release/Tegra\\_Linux\\_Sample-Root-Filesystem\\_r36.5.0\\_aarch64.tbz2>***
3. Execute the following commands to extract and assemble the flash package:

   ***tar xf Jetson\_Linux\_r36.5.0\_aarch64.tbz2***

   ***sudo tar xpf Tegra\_Linux\_Sample-Root-Filesystem\_r36.5.0\_aarch64.tbz2 -C Linux\_for\_Tegra/rootfs/***

   ***cd Linux\_for\_Tegra/***&#x20;

   ***sudo ./tools/l4t\_flash\_prerequisites.sh***

   ***sudo ./apply\_binaries.sh***

   ***sudo tar xf holybro\_jp622***      #copy holybro\_jp622 to the Linux\_for\_Tegra/ directory before excution
4. Put the device in Recovery mode
   1. If the device ID is (7323/7423/7523/7623) when executing the ***lsusb*** command, the device is in recovery mode
5. Flash to SSD using the command below

   ***sudo ./tools/kernel\_flash/l4t\_initrd\_flash.sh --external-device nvme0n1p1***\
   ***-c tools/kernel\_flash/flash\_l4t\_t234\_nvme.xml -p "-c bootloader/generic/cfg/flash\_t234\_qspi.xml"***\
   ***--showlogs --network usb0 jetson-orin-nano-devkit-super internal***
6. System Backup and Recovery
   1. Backup image (enter Recovery mode):&#x20;

      ***sudo ./tools/backup\_restore/l4t\_backup\_restore.sh -e nvme0n1 -b jetson-orin-nano-devkit-super***
   2. Flash the device using the backup image (enter Recovery mode):&#x20;

      ***sudo ./tools/backup\_restore/l4t\_backup\_restore.sh -e nvme0n1 -r jetson-orin-nano-devkit-super***

## Important procedure if the SSD has preinstalled Jetpack

After the system is cloned to a new SSD, we connect the SSD and Jetson module to the baseboard, enter the force recovery mode, and connect to the computer.\
On the computer used to flash the firmware with the SDK manager, navigate to the folder: nvidia ->nvidia\_sdk, find the target version Jetpack folder, open it, and open the terminal at the folder location.

<figure><img src="https://2367252986-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLIgtGDAvVGkCKGOJb1bR%2Fuploads%2F8EdvPUazZY4VHvFSxjuD%2F%E5%9B%BE%E7%89%87.png?alt=media&amp;token=fc74207f-6705-4124-8e72-83872a475d12" alt=""><figcaption></figcaption></figure>

<figure><img src="https://2367252986-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLIgtGDAvVGkCKGOJb1bR%2Fuploads%2FdIX8w7LmPefzqIp7pomK%2F%E5%9B%BE%E7%89%87.png?alt=media&amp;token=5df2f876-fa9c-4e74-b322-e4f28e481f8d" alt=""><figcaption></figcaption></figure>

Once in the terminal, enter the command below:\
sudo ./flash.sh --no-systemimg -c bootloader/t186ref/cfg/flash\_t234\_qspi.xml jetson-orin-nano-devkit  mmcblk0p1

{% hint style="info" %}
In the latest Jetpack, the file path is bootloader/generic/cfg/flash\_t234\_qspi.xml
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.holybro.com/autopilot/pixhawk-baseboards/pixhawk-jetson-baseboard/flashing-guide.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
