How to do os recovery for Jetson board?

Preparing a Jetson Developer Kit for Use

This section explains how to prepare a Jetson developer kit for use by flashing it with the appropriate software.

Assumptions

• You have a Jetson developer kit.

For the Jetson Nano Developer Kit, you can skip this guide and simply download and use the supported microSD card image. Alternatively, you can follow these instructions to flash the QSPI-NOR, or flash the QSPI-NOR and a microSD card inserted on the Jetson Nano module.

• Your Jetson developer kit is powered off, and is connected as follows. (Note that your Jetson developer kit may not come with the devices and cables listed below.)

• A USB cable connects the correct USB port on your Jetson developer kit to your Linux host for flashing.

For the NVIDIA Jetson AGX Xavier Developer Kit, use the USB-C port next to the power button. For the other Jetson developer kits, use the micro USB port.

• Any required USB peripherals such as keyboard and mouse are connected to the Jetson developer kit, possibly through a USB hub.

• A wired Ethernet connection is available for installing optional software on the Jetson developer kit after L4T is installed and running.

• Either a display device or a serial console is connected to the Jetson developer kit.

• The qemu-user-static package has been installed on the Linux host:

sudo apt-get install qemu-user-static

The installation process needs this package to install certain NVIDIA software components onto the Jetson developer kit.

Environment Variables

The directions that follow assume that:

• ${L4T_RELEASE_PACKAGE} contains the L4T release package’s name.

• For Jetson Nano and Jetson TX1 modules: Jetson-210_Linux_r32.4.2_aarch64.tbz2

• For Jetson Xavier NX, Jetson AGX Xavier series, and Jetson TX2 series modules: Jetson_Linux_L4T r32.4.2_aarch64.tbz2

• ${SAMPLE_FS_PACKAGE} contains the filename of the sample filesystem package:

Tegra_Linux_Sample-Root-Filesystem_L4TRELEASEVERSION.tbz2

• ${BOARD} contains the name of a configuration supported for your specific Jetson module and carrier board.

Some examples are:

• jetson-nano-devkit

• jetson-tx2-devkit

• jetson-xavier-nx-devkit

Recent and future configuration files’ names follow this format:

<board_part_number>+<module_part_number>[-<modifier>].conf

• <board_part_number> is the P‑number (the full part number) for the NVIDIA carrier board that the .conf file supports.

• <module_part_number> is the P‑number for the Jetson module that the .conf file supports.

• <modifier> is an optional string that indicates which of several configurations the .conf file applies; for example, on a module that may have either eMMC or microSD card memory, which one it uses to flash the operating software.

Older configuration files’ name generally follow this format:

<config_name>[-<modifier>].conf

Where <config_name> is a name that represents the carrier board and module that the .conf file supports.

To flash Jetson Developer Kit operating software

1. Download the latest L4T release package and sample file system for your Jetson developer kit from:

https://developer.nvidia.com/linux-tegra

2. Enter these commands to untar the files and assemble the rootfs:

$ tar xf ${L4T_RELEASE_PACKAGE} or tar xf Tegra186_Linux_R32.4.3_aarch64.tbz2

$ cd Linux_for_Tegra/rootfs/

$ sudo tar xpf ../../${SAMPLE_FS_PACKAGE} or sudo tar xpf Tegra_Linux_Sample-Root-Filesystem_R32.4.3_aarch64.tbz2

$ cd ..

$ sudo ./apply_binaries.sh

3. Ensure that your Jetson developer kit is configured and connected to your Linux host as described in Assumptions.

4. Put your Jetson developer kit into Force Recovery Mode (RCM).

 

For other Jetson developer kits that have hardware buttons:

1) Ensure that the developer kit is powered off.

2) Press and hold down the Force Recovery button.

3) Press, then release the Power button.

4) Release the Recovery button.

5) Continue the software installation.

You can confirm that your developer kit is in Force Recovery mode by following the procedure in To determine whether the developer kit is in Force Recovery mode.

5. Enter this command on your Linux host to flash (install) the L4T release onto the Jetson developer kit:

sudo ./flash.sh ${BOARD} mmcblk0p1

sudo ./flash.sh jetson-xavier-nx-devkit-emmc mmcblk0p1

The value of the environment variable $(BOARD) determines the configuration that the flashing script applies. The table at the end of this section describes the configurations available for each Jetson module with its respective Jetson developer kit carrier board.

There is a configuration file that corresponds to each value of $(BOARD). Its name is the value of $(BOARD) with the filename $(BOARD).conf. For example, the configuration file that corresponds to jetson-nano-devkit is jetson-nano-devkit.conf.

Flashing L4T takes about 10 minutes, or more with a slow host computer.

 

Boot into Jetson OS

sudo apt update

sudo apt upgrade

sudo apt install nvidia-jetpack

 

 

Check Cuda, Tensorrt, CUDNN Status

sudo apt install python-pip

sudo pip install jetson-stats

jtop

Look at the page info (6)

 

All Done!

references:-

https://developer.nvidia.com/embedded/linux-tegra
https://developer.nvidia.com/embedded/L4T/r32_Release_v4.3/t186ref_release_aarch64/Tegra186_Linux_R32.4.3_aarch64.tbz2
https://developer.nvidia.com/embedded/L4T/r32_Release_v4.3/t186ref_release_aarch64/Tegra_Linux_Sample-Root-Filesystem_R32.4.3_aarch64.tbz2

recovery instructions:-
https://docs.nvidia.com/jetson/l4t/index.html#page/Tegra%2520Linux%2520Driver%2520Package%2520Development%2520Guide%2Fquick_start.html%23wwpID0E0BE0HA

How to boot from SSD after sdcard flash

https://www.seeedstudio.com/blog/2020/06/22/boot-jetson-xavier-from-m-2-ssd/ 

 

Step 1. Format the SSD you have installed

Install your and SSD and boot, then open the menu and search disk.

Step 2. Copy the rootfs from SD card to SSD

Firstly, clone the project.

git clone https://github.com/jetsonhacks/rootOnNVMe.git
cd rootOnNVMe

Then copy rootfs file to your SSD

./copy-rootfs-ssd.sh

Step 3. Enable booting from SSD

Run ./setup-service.sh and reboot to make the service come into effect.