According to the development documentation, I tried to use flash.sh to flash the Thor devkit with ROOTFS_AB=1, but it reported an error saying that the configuration file could not be found. I checked the bootloader/generic/cfg directory and found that it only contains XML files for t234, not t264. This is very confusing — R38.2 now claims to support only Thor, yet most parts of the documentation still describe Orin or NX, and Thor cannot actually be used.
To flash redundant root file systems on an external storage device, refer to the Workflow #4 in Linux_for_Tegra/tools/kernel_flash/README_initrd_flash.txt.
Error: Return value 4
Command tegraparser_v2 --generategpt --pt flash.xml.bin
cp: cannot stat ‘signed/*’: No such file or directory
cp: cannot stat ‘signed/flash.xml.tmp’: No such file or directory
./tegraflash.py --bl _sigheaderencrypt. --bct br_bct_BR.bct --bldtb tegra264-p3740-0002+p3834-0008-qspi-nvme.dtb --applet applet_t264.bin --cmd “secureflash;reboot” --cfg secureflash.xml --chip 0x26 --coldboot_bct_cfg bct_cfg.xml --rcmboot_bct_cfg rcmboot_bct_cfg.xml --minratchet_config tegra264-mb1-bct-ratchet-p3834-xxxx-p3971-0000.dts --bct_flags_file platform_config_profile.yaml --bins “mb2_bootloader mb2_t264_sigheader.bin.encrypt; xusb_fw xusb_t264_prod_sigheader.bin.encrypt; pva_fw nvpva_030_sigheader.fw.encrypt; dce_fw display-t264-dce_sigheader.bin.encrypt; bpmp_fw bpmp_t264-TA1090SA-A1_prod_sigheader.bin.encrypt; fsi_fw fsi-fw-t264_sigheader.bin.encrypt; bpmp_fw_dtb tegra264-bpmp-3834-0008-3740-xxxx_sigheader.dtb.encrypt; rce_fw camera-rtcpu-t264-rce_sigheader.img.encrypt; eks eks_t264_sigheader.img.encrypt; bootloader_dtb tegra264-p3740-0002+p3834-0008-qspi-nvme_sigheader.dtb.encrypt”
saving flash command in flashcmd.txt
*** no-flash flag enabled. Exiting now… ***
User can run above saved command in factory environment without
providing pkc and sbk keys to flash a device
Example:
$ cd bootloader
$ sudo bash ./flashcmd.txt
Error: /home/wpces/Downloads/Linux_for_Tegra/bootloader/signed/flash.idx is not found
Error: failed to relocate images to /home/wpces/Downloads/Linux_for_Tegra/tools/kernel_flash/images
Cleaning up…
root@wpces:/home/wpces/Downloads/Linux_for_Tegra#
root@wpces:/home/wpces/Downloads/Linux_for_Tegra/bootloader# bash flashcmd.txt
Welcome to Tegra Flash
version 1.0.0
Type ? or help for help and q or quit to exit
Use ! to execute system commands
Traceback (most recent call last):
File “/home/wpces/Downloads/Linux_for_Tegra/bootloader/./tegraflash.py”, line 1479, in
tegraflash_run_commands()
File “/home/wpces/Downloads/Linux_for_Tegra/bootloader/./tegraflash.py”, line 1293, in tegraflash_run_commands
interpreter.onecmd(command)
File “/usr/lib/python3.12/cmd.py”, line 217, in onecmd
return func(arg)
^^^^^^^^^
File “/home/wpces/Downloads/Linux_for_Tegra/bootloader/./tegraflash.py”, line 342, in do_secureflash
self.chip_inst.tegraflash_secureflash(exports)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: ‘TFlashT264’ object has no attribute ‘tegraflash_secureflash’. Did you mean: ‘tegraflash_flash’?
root@wpces:/home/wpces/Downloads/Linux_for_Tegra/bootloader#
AGX Thor does not support root file system redundancy at JP-7.0 release version.
we’ve changes merge into rel-38 code-line to enable that, please expect next JP-7.1 public release will support Rootfs-A/B.
The news I heard before was that it would be released in early December.
Now why has it been delayed to 2026?
In the meantime, will there be any 7.0 version patches, for example some updates merged in from 7.1, or will there be nothing at all…
Can you please clarify whether the bootloader and rootfs slots are not supposed to correspond one-to-one? I’ve noticed that after successfully upgrading the bootloader, the rootfs didn’t switch. The current slot is B, but the rootfs is still nvme0n1p1.
root@tegra-ubuntu:~# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/nvme0n1p1 177G 28G 140G 17% /
tmpfs 62G 140K 62G 1% /dev/shm
tmpfs 25G 23M 25G 1% /run
tmpfs 5.0M 8.0K 5.0M 1% /run/lock
efivarfs 256K 12K 245K 5% /sys/firmware/efi/efivars
/dev/nvme0n1p5 505M 78K 505M 1% /boot/efi
tmpfs 13G 112K 13G 1% /run/user/121
tmpfs 13G 96K 13G 1% /run/user/0
root@tegra-ubuntu:~# nvbootctrl dump-slots-info
Current version: 38.4.0
Capsule update status: 1
Current bootloader slot: B
Active bootloader slot: B
num_slots: 2
slot: 0, status: normal
slot: 1, status: normal
