How can we pxe boot jetson agx thor. I want to flash a lot of thors together and I can use massflash but I want to do it through network easily since massflash has physical limitations like flashing 20 devices or 50 devices together etc. I tried pxe booting for which I created unzipped the jetpack 7.x iso and created the tftp dir in this way
├── casper
│ ├── Image
│ └── initrd
├── efi
│ └── grubnetaa64.efi.signed
└── grub
└── grub.cfg
now when I turn pxeclient on, it does download grub binary but doesnt even request for grub config file and lands into grub shell.
In grub shell , I checked the `prefix=(tftp,172.16.1.1)/grub` and similarly checked the nic too. everything seems to be fine but then when I try to do cat tftp,172.16.1.1)/grub/grub.cfg , it outputs couldn’t send network packet which if I understand is that grub is losing network connectivity after it hands the control over to grub. I am not able to understand why whats happening so if anyone can help and suggest solutions
If your network and switch can handle the load; you could try --network eth0
instead of usb
./l4t_initrd_flash.sh --help
--massflash [<max_devices>] Flash multiple device. specify <max_devices> to limit the number of devices supported. Default is 10 if not specified in board config file
--showlogs Spawn gnome-terminal to show individual flash process logs. Applicable
for --massflash only.
--erase-all Erase all storage devices before flashing.
--initrd Stop after device boot into initrd.
--network <netargs> Flash through Ethernet protocal using initrd flash. <netargs> can be "usb0" to flash through the USB Flashing cable
or "eth0:<target-ip>/<subnet>:<host-ip>[:<gateway>]" to flash through the LAN cable
For examples:
--network usb0
--network eth0:192.168.0.17/24:192.168.0.21
--network eth0:192.168.0.17/24:192.168.1.2:192.168.0.1
l4t_backup_restore.sh: --network <netargs> -------- Specifying the network protocol to use. <netargs> can be "usb0" to backup through the USB Flashing cable
l4t_backup_restore.sh: --network usb0
l4t_backup_restore.sh: --network eth0:192.168.0.17/24:192.168.0.21
l4t_backup_restore.sh: --network eth0:192.168.0.17/24:192.168.1.2:192.168.0.1
l4t_backup_restore.sh: network)
l4t_backup_restore.sh: network="${!OPTIND}";
l4t_backup_restore.sh:# Use network mounted directory for backup and restore
l4t_backup_restore.sh:"${INITRD_FLASH_SCRIPT}" --initrd --boot-rootfs --showlogs "${cmd[@]}" --network "${network}" "${target_board}" internal
l4t_backup_restore.sh:enable_nfs_for_folder "${nfs_folder}" "${network}"
l4t_backup_restore.sh:IFS=':' read -r -a arr <<< "${network}"
l4t_backup_restore.sh:if [[ "${network}" == eth0* ]]; then
grep -ir -C5 network tools/ota_tools/version_upgrade/Image_based_OTA_Examples.txt
Case 12: rootfs A/B disabled, disk encryption disabled:
a. Put the target device into recovery mode.
b. Boot the device to initrd by running the following command:
$ sudo ./tools/kernel_flash/l4t_initrd_flash.sh --initrd <target board> mmcblk0p1
c. Enter bash shell on the target device.
d. Mount a USB drive or network storage on the target device.
e. Generate golden image in the mounted storage device by running the
following command:
$ sudo dd if=<rootfs partition> of=<mount ponint>/golden.img.raw
The "<rootfs partition>" is /dev/mmcblk0p1 for the internal eMMC storage device
or /dev/nvme0n1p1 for the external NVMe storage device.
--
Case 13: rootfs A/B enabled, disk encryption disabled:
a. Put the target device into recovery mode.
b. Boot the device to initrd by running the following command:
$ sudo ./tools/kernel_flash/l4t_initrd_flash.sh --initrd <target board> mmcblk0p1
c. Enter bash shell on the target device.
d. Mount a USB drive or network storage on the target device.
e. Generate golden images in the mounted storage device by running the
following commands:
$ sudo dd if=<rootfs partition A> of=<mount ponint>/golden_a.img.raw
$ sudo dd if=<rootfs partition B> of=<mount ponint>/golden_b.img.raw
The "<rootfs partition A>" is /dev/mmcblk0p1 for the internal eMMC storage
--
Case 14: rootfs A/B disabled, disk encryption enabled:
a. Put the target device into recovery mode.
b. Boot the device to initrd by running the following command:
$ sudo ./tools/kernel_flash/l4t_initrd_flash.sh --initrd <target board> mmcblk0p1
c. Enter bash shell on the target device.
d. Mount a USB drive or network storage on the target device.
e. Generate golden image in the mounted storage device by running the
following command:
$ sudo dd if=<rootfs partition> of=<mount ponint>/golden.img.raw
The "<rootfs partition>" is /dev/mmcblk0p2 for the internal eMMC storage device
or /dev/nvme0n1p2 for the external NVMe storage device.
--
Case 15: rootfs A/B enabled, disk encryption enabled:
a. Put the target device into recovery mode.
b. Boot the device to initrd by running the following command:
$ sudo ./tools/kernel_flash/l4t_initrd_flash.sh --initrd <target board> mmcblk0p1
c. Enter bash shell on the target device.
d. Mount a USB drive or network storage on the target device.
e. Generate golden images in the mounted storage device by running the
following commands:
$ sudo dd if=<rootfs partition A> of=<mount ponint>/golden_a.img.raw
$ sudo dd if=<rootfs partition B> of=<mount ponint>/golden_b.img.raw