Using AGX Orin Devkit Image on a 32GB Module

Robotics & Edge Computing Jetson Systems Jetson AGX Orin
,
1

Hello, I designed my own AGX Orin carrier board. When I insert the devkit’s pre-flashed module, all the USB ports, DisplayPort, and the debug port work as expected.

However, the company I’m working with supplied a standalone production module (not a devkit) with 32GB. I want to load the same image that comes on the devkit module onto this 32GB production module. What is the correct procedure to do this, and what steps should we follow?

2

*** Please note that this reply is generated by LLM automatically ***

To load the same image that comes on the devkit module onto the 32GB production module, you’ll need to follow a series of steps. Before we dive into the procedure, it’s essential to understand the differences between the devkit module and the standalone production module.

The devkit module comes pre-flashed with the necessary software and configurations, whereas the standalone production module is a blank slate. The production module has a Thermal Transfer Plate (TTP) that is ready to accept a customer-provided thermal solution, whereas the devkit module has a thermal solution designed specifically for the devkit.

Here’s a step-by-step guide to help you load the same image onto the 32GB production module:

Step 1: Prepare the necessary tools and software

  • You’ll need a Linux host machine with the necessary tools and software installed. The recommended Linux distribution is Ubuntu 18.04 or later.
  • Download the Jetson Linux Driver Package (L4T) from the NVIDIA website. This package includes the necessary software and tools for flashing the production module.
  • Make sure you have the correct USB cable and a power supply for the production module.

Step 2: Flash the production module

  • Connect the production module to the Linux host machine using the USB cable.
  • Open a terminal on the Linux host machine and navigate to the directory where you extracted the L4T package.
  • Run the following command to flash the production module:
sudo ./flash.sh -k APP -G /dev/sdX

Replace /dev/sdX with the actual device name of the production module (e.g., /dev/sdb).

Step 3: Configure the production module

  • After flashing the production module, you’ll need to configure it to match the devkit module’s configuration.
  • Run the following command to configure the production module:
sudo ./flash.sh -k APP -G /dev/sdX -c

This command will configure the production module to use the same partition layout and configuration as the devkit module.

Step 4: Load the devkit image onto the production module

  • Once the production module is configured, you can load the devkit image onto it.
  • Run the following command to load the devkit image:
sudo ./flash.sh -k APP -G /dev/sdX -r

This command will load the devkit image onto the production module.

Step 5: Verify the production module

  • After loading the devkit image, verify that the production module is working as expected.
  • Connect the production module to your custom carrier board and test the USB ports, DisplayPort, and debug port to ensure they are functioning correctly.

Comparison with the devkit module

  • The main difference between the devkit module and the standalone production module is the thermal solution. The devkit module has a thermal solution designed specifically for the devkit, whereas the production module has a TTP that is ready to accept a customer-provided thermal solution.
  • The production module also requires configuration and flashing before it can be used, whereas the devkit module comes pre-flashed and configured.

By following these steps, you should be able to load the same image that comes on the devkit module onto the 32GB production module. Make sure to verify the production module’s functionality after loading the image to ensure it is working as expected.

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***

3

First of all, the answers seemed absurd because it was created with artificial intelligence. It wasn’t clearly stated which one would be done on the host side and which one would be done on the origin.
I want to implement the devkit’s device tree as a device tree to standalone orin module.

6

It seems to be duplicated with Agx orin custom carrier board ,standalone module configurations - #9 by proventusnova

Could we close the topic?

Thanks