[35.3.1] rootfs folder in the tar.gz file generated by --massflash argument

Hi, I use the argument --massflash to generate *.tar.gz that can be flashed to the device.
I found this tar.gz file includes rootfs folder in 35.3.1; however the file created by 35.2.1 doesn’t have rootfs folder.
Is there any way to have the tar.gz file that doesn’t have rootfs folder in 35.3.1?
If it is necessary to have rootfs folder, is there any way to reduce the size of the tar.gz file?

Thanks a lot.

您好,我使用–massflash參數來build code產生tar.gz檔案,且能成功燒到裝置上面。
我發現到35.3.1的tar.gz檔案有包含rootfs資料夾,但是在35.2.1卻沒有。
我想問的是,在35.3.1有機會不包含rootfs資料夾嗎?
或者有其他方式可以縮小tar.gz檔案的大小嗎?

感謝。

Hi fengying_chu,

the rootfs is necessary for the board to be flashed.
Do you mean the mfi package too large for you in R35.3.1?
What’s current size and what’s your desired size?

Hi Kevin,
We use Orin NX 16GB SOM with Xavier NX Devkit(NVMe).
In 35.3.1, the tar.gz file is around 4.5GB. In 35.2.1, the tar.gz file is around 2.42GB.
There is a huge size difference between 35.3.1 and 35.2.1.
Therefore, we are wondering that is there any way to reduce the size of the tar.gz file?

您好,在35.3.1,我們使用–massflash生成的tar.gz約4.5 GB, 使用35.2.1則有2.42 GB。
解壓縮後,發現35.3.1有包含rootfs資料夾,此rootfs資料夾超過30 GB。然而35.2.1沒有此rootfs資料夾。
所以,我們想知道,在不影響效能的情況下,35.3.1有沒有機會能減少tar.gz解壓縮後的大小呢?

感謝。

Do you run the same command to generate mfi package?
Could you help to provide the detailed steps and command you use to generate the package(.tar.gz)?

Hi Kevin,
The commands I use in 35.3.1 are as following:

  1. ls -la mfi*
    ls: cannot access ‘mfi*’: No such file or directory
  2. sudo BOARDID=3767 BOARDSKU=0000 ./tools/kernel_flash/l4t_initrd_flash.sh --no-flash --massflash 10 --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml -p “-c bootloader/t186ref/cfg/flash_t234_qspi.xml” --showlogs --network usb0 jetson-orin-nano-devkit internal
  3. ls -la mfi*
    -rw-r–r-- 1 root root 4715848296 四 28 14:50 mfi_jetson-orin-nano-devkit.tar.gz

As the result, the tar.gz file is around 4.39GB.
The log is attached.

log_20230428.txt (14.8 MB)

Thanks a lot.

Could you help to use the following command instead to generate mfi package for Orin NX?

$sudo ./tools/kernel_flash/l4t_initrd_flash.sh --no-flash --external-device nvme0n1p1 -p "-c bootloader/t186ref/cfg/flash_t234_qspi.xml --no-systemimg" -c ./tools/kernel_flash/flash_l4t_external.xml --massflash 10 --showlogs --network usb0 jetson-orin-nano-devkit-nvme nvme0n1p1

Hi Kevin,
I use your command. The tar.gz file is still about 4.39 GB.

  1. ls -la mfi*
    ls: cannot access ‘mfi*’: No such file or directory
  2. sudo ./tools/kernel_flash/l4t_initrd_flash.sh --no-flash --external-device nvme0n1p1 -p “-c bootloader/t186ref/cfg/flash_t234_qspi.xml --no-systemimg” -c ./tools/kernel_flash/flash_l4t_external.xml --massflash 10 --showlogs --network usb0 jetson-orin-nano-devkit-nvme nvme0n1p1
  3. ls -la mfi*
    -rw-r–r-- 1 root root 4716286241 四 28 16:35 mfi_jetson-orin-nano-devkit-nvme.tar.gz

The log is attached.

log_v2_20230428.txt (15.6 MB)

有沒有機會在35.3.1上使用–massflash生成的mfi*.tar.gz,其解壓縮後,內容大小能縮小。

It seems 4.x GB is the expected size of mfi package for Orin NX.

Sorry, we don’t have related method to minimize the size of mfi package.
May I know what’s the purpose or use case for you to get lower size of mfi package?

Hi Kevin,
Currently, we do not have any use case for us to get lower size of mfi package.
We just see that difference between 35.2.1 and 35.3.1, and are interested in why the 35.3.1 package is much larger than that of 35.2.1.
If possible, may we know the reason?

Thank you.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.