Re-imaging with CRL's Jetpack-Tools

TABLE OF CONTENTS

• Overview
• Key Features
• Usage Summary
• Example

Overview

CRL’s JETPACK-TOOLS is a convenient wrapper around NVIDIA’s Jetpack SDKs that simplifies the process of generating and flashing images for Carnegie Robotics’ Jetson-based systems. The primary tool in this repository is the jetpack-flash.sh script, which automates the image generation and flashing procedures.

Note!
To obtain the JETPACK-TOOLS, please contact Carnegie Robotics. Reach out via email at support@carnegierobotics.com.

Key Features

Automated Image Generation and Flashing: Easily generate system images with configurable options for Jetpack, CUDA, cuDNN, and TensorRT versions.

Flexible Configuration: Set custom download and output directories, board IDs, user credentials, network settings, and more.

BSP Support: Select the appropriate Board Support Package (BSP) for your system (e.g., Cardshark in this example).

Usage Summary

The core script, jetpack-flash.sh, is executed with a series of command-line options. Below is a simplified usage summary:

./jetpack-flash.sh

    --output-dir {PATH}

    --configure

    --clean

    --no-flash

    --flash-only

    --oldconfig

• –output-dir {PATH} configures a directory where the image will be constructed. This defaults to the current directory, and all image artifacts will be stored under output-dir/Linux_for_Tegra.
• –configure may be used to launch the configuration UI. This will launch a kconfig driven UI system; further help for navigating and selecting configuration options is provided inside the configuration tool.
• –clean may be used to clear the entire output-dir/Linux_for_Tegra directory and restart the image generation from scratch. This is useful if you encounter errors during the image generation process
• –no-flash may be used to only generate an image without attempting to flash a system.
• –flash-only may be used to skip the entire image generation process and only flash a system. This option should only be used if you have successfully generated an image or have already flashed a system.
• –oldconfig may be used to silently upgrade the configuration file to the latest version. If this option is not included, the configurator UI will be launched whenever jetpack-tools is updated to a newer version.
  
  

Example

For example, a typical first-time build might look like:

./jetpack-flash.sh --configure --clean --no-flash --output-dir /myJetpackToolsDir

./jetpack-flash.sh --flash-only --output-dir /myJetpackToolsDir