03.06 NVMe

3.6NVMe Storage

This procedure details the cloning steps for Advantech devices using NVMe storage. This method utilizes a two-step process: initializing the NVMe and then using the rsync protocol to clone the filesystem.

3.6.1Step 1: Initialize the NVMe Device

This step runs a special flash command to initialize the NVMe partition, load a recovery ramdisk, and establish a network connection for cloning.

1. Prepare Device and Connect: Extract the correct BSP on the host PC. Put the MIC device into Recovery Mode and connect it to the host PC using a Micro-USB cable.
2. Execute Initialization Command: Run the command corresponding to your device from the BSP root directory. This command will output an SSH connection string (e.g., ssh root@fc00:1:1:0::2) that you will need for the next step.

Device	Initialization Command
MIC-733	sudo ./tools/kernel_flash/l4t_initrd_flash.sh --initrd jetson-agx-orin-devkit nvme0n1p1
MIC-715	sudo ./tools/kernel_flash/l4t_initrd_flash.sh --initrd p3509-a02-p3767-0000 nvme0n1p1

3.6.2Step 2: Prepare for rsync (Mount and Copy Tools)

1. Mount NVMe Partition: Use the noted SSH address to remotely mount the NVMe partition (/dev/nvme0n1p1) to the mount point (/mnt) on the target device:

   ssh root@fc00:1:1:0::2 "mount /dev/nvme0n1p1 /mnt"

2. Copy rsync Dependencies: Copy the rsync executable and its required libraries from the host BSP's rootfs to the device's temporary environment to enable the cloning operation.

   scp -6 rootfs/usr/bin/rsync root@[\fc00:1:1:0::2\]:/bin
   scp -6 rootfs/usr/lib/aarch64-linux-gnu/libpopt.so.0.0.1 root@[\fc00:1:1:0::2\]:/usr/lib/libpopt.so.0
   scp -6 rootfs/usr/lib/aarch64-linux-gnu/libxxhash.so.0.8.1 root@[\fc00:1:1:0::2\]:/usr/lib/libxxhash.so.0

3.6.3Step 3: Create the System Image (Clone)

1. Prepare SSH Access: Temporarily switch to the root user on the host PC and establish an SSH connection to the device for key generation, then exit back to your normal host account.

   sudo su
   ssh root@fc00:1:1:0::2
   exit
   exit

2. Execute rsync Clone: Run the rsync command to clone the master device's configured root filesystem (mounted at /mnt) back to the host PC's BSP rootfs/ directory.

   sudo rsync -avtxHAWX --delete root@[\fc00:1:1:0::2\]:/mnt/ rootfs/

3.6.4Step 4: Prepare and Flash the Cloned Image (Restore)

1. Modify fstab: Navigate to the rootfs/etc directory within your BSP and modify the fstab file to correctly specify the boot partition on the NVMe device (/dev/nvme0n1p10).

Device	fstab Modification Command
MIC-733	sudo sed -i "s|^UUID.*|/dev/nvme0n1p10 /boot/efi vfat defaults 0 1|g" ./rootfs/etc/fstab
MIC-715	Manually edit: sudo vim MIC-715_OrinNX_6.0_V1.0.3_SDK/rootfs/etc/fstab and ensure the last string is: /dev/nvme0n1p10 /boot/efi vfat defaults 0 1

2. Set Boot Priority (MIC-733 only): For the MIC-733, run this command to set the default boot priority to NVMe.

   sudo fdtput -t s ./kernel/dtb/L4TConfiguration.dtbo /fragment@0/__overlay__/firmware/uefi/variables/gNVIDIATokenSpaceGuid/DefaultBootPriority data "nvme,emmc,usb,sd,ufs"

3. Execute Final Flash Command: Put the new target device into Recovery Mode again. Run the flash command corresponding to your device. This command uses the customized rootfs/ data you cloned.

Device	Flash Command (Restores Cloned rootfs)
MIC-733	sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml -p "-c bootloader/generic/cfg/flash_t234_qspi.xml" --showlogs --network usb0 jetson-agx-orin-devkit internal
MIC-715	Do Normal Flash again by SOP

⬆️ Top