Install-script

Flashing Jetson devices

Requirements:

• A Linux computer
• USB cable to connect to the Jetson device
• Jumper cable (for devices without reset button)

Run the script jetson_flash.sh on your own computer. The script will download the necessary files (BSP and root filesystem) and flash them to the Jetson device.

The script will prompt you for the exact version of Jetson Linux you want to install. Available versions are listed here: https://developer.nvidia.com/embedded/jetson-linux-archive. You can find the links to the BSP and root filesystem by clicking on the desired version and on the next page copying the links for "Driver Package (BSP) and Sample Root Filesystem".

The script will also ask you whether you want to keep the temporary files after flashing. If you need to flash multiple devices then select yes to avoid re-downloading them. A separate directory will be created for each version of Jetson Linux, my default at $HOME/jetson_flash_tmp_VERSION/. In case you change your mind you can always delete the entire directory. The size of this directory is about 75 GB.

After the script completes, you can continue configuration on the Jetson device by cloning this repository and running the setup_utility.sh script.

Configuration utility

• Run the script with "setup_utility.sh" in the root directory of the repository.
• The menu items will be automatically generated from the subscripts folder
• Scripts and folders will appear in the menu as items or folders.
• You can easily add new functionality by putting new scripts into the subscripts folder. See examples of menus in the examples_whiptail folder.

Non-interactive configuration

Use setup_utility_auto.sh to run setup non-interactively from a profile file, which contains all the necessary information and toggles for the configuration. This is useful for automating the setup process or for running it on multiple devices with the same configuration.

./setup_utility_auto.sh profiles/sample.conf

Profile files are located in profiles/ directly. They contain a list of toggles and variables for guiding the configuration. A new profile can be created by copying and modifying the sample.conf file as needed.

Note that not all functionality of the manual setup utilities is available in the non-interactive version. Most notably:

• Switching from networkd back to NetworkManager, since it is only there for debugging purposes
• Installation and uninstallation of ROS without docker (directly with apt). This can be implemented in the future.
• MRS internal only configuration. Can be implemented in the future.
• Disregarded scripts