I found from the flash logs that the configuration file is taken from the below path /Linux_for_Tegra/bootloader/t186ref/cfg/flash_l4t_t194_spi_emmc_p3668.xml
which does not include the APP_b partition , and the file flash_l4t_t194_spi_emmc_p3668_rootfs_ab.xml includes the details of APP_b partition , can i use this file while flashing , if so what is the process so that APP_b partition is created in order to solve the above error.
APP_b partition makes reference to AB partitioning support. Which means that you will have your normal A rootfs and a second rootfs called B. Not quite sure if this is what you want but to solve your issue you have to use the flash_l4t_t194_spi_emmc_p3668_rootfs_ab.xml partition file and flash the device. The issue should be solved.
The process to do this would be to change the EMMC_CFG propety on the jetson-xavier-nx-devkit-emmc.conf file as shown below:
RootfsA/B is disabled by default, please re-flash the target with ROOTFS_AB=1 flash option.
please refer to developer guide, Using initrd flash with Orin NX and Nano.
tar: etc/ssl/certs/SSL.com_EV_Root_Certification_Authority_RSA_R2.pem: Cannot create symlink to ‘/usr/share/ca-certificates/mozilla/SSL.com_EV_Root_Certification_Authority_RSA_R2.crt’: No space left on device
tar: etc/ssl/certs/HARICA_TLS_ECC_Root_CA_2021.pem: Cannot create symlink to ‘/usr/share/ca-certificates/mozilla/HARICA_TLS_ECC_Root_CA_2021.crt’: No space left on device
tar: etc/ssl/certs/Entrust.net_Premium_2048_Secure_Server_CA.pem: Cannot create symlink to ‘/usr/share/ca-certificates/mozilla/Entrust.net_Premium_2048_Secure_Server_CA.crt’: No space left on device
tar: etc/ssl/certs/DigiCert_Assured_ID_Root_G2.pem: Cannot create symlink to ‘/usr/share/ca-certificates/mozilla/DigiCert_Assured_ID_Root_G2.crt’: No space left on device
tar: etc/ssl/certs/emSign_ECC_Root_CA_-_G3.pem: Cannot create symlink to ‘/usr/share/ca-certificates/mozilla/emSign_ECC_Root_CA_-_G3.crt’: No space left on device
tar: etc/ssl/certs/OISTE_WISeKey_Global_Root_GB_CA.pem: Cannot create symlink to ‘/usr/share/ca-certificates/mozilla/OISTE_WISeKey_Global_Root_GB_CA.crt’: No space left on device
tar: etc/ssl/certs/DigiCert_Global_Root_G2.pem: Cannot create symlink to ‘/usr/share/ca-certificates/mozilla/DigiCert_Global_Root_G2.crt’: No space left on device
tar: etc/ssl/certs/Certum_Trusted_Network_CA.pem: Cannot create symlink to ‘/usr/share/ca-certificates/mozilla/Certum_Trusted_Network_CA.crt’: No space left on device
tar: etc/ssl/certs/Entrust_Root_Certification_Authority_-_G4.pem: Cannot create symlink to ‘/usr/share/ca-certificates/mozilla/Entrust_Root_Certification_Authority_-_G4.crt’: No space left on device
tar: etc/ssl/certs/T-TeleSec_GlobalRoot_Class_3.pem: Cannot create symlink to ‘/usr/share/ca-certificates/mozilla/T-TeleSec_GlobalRoot_Class_3.crt’: No space left on device
tar: etc/ssl/certs/Go_Daddy_Root_Certificate_Authority_-_G2.pem: Cannot create symlink to ‘/usr/share/ca-certificates/mozilla/Go_Daddy_Root_Certificate_Authority_-_G2.crt’: No space left on device
tar: etc/fonts/conf.d/89-tlwg-umpush-synthetic.conf: Cannot create symlink to ‘/usr/share/fontconfig/conf.avail/89-tlwg-umpush-synthetic.conf’: No space left on device
tar: etc/fonts/conf.d/61-urw-fallback-backwards.conf: Cannot create symlink to ‘/usr/share/fontconfig/conf.avail/urw-fallback-backwards.conf’: No space left on device
tar: etc/fonts/conf.d/61-urw-standard-symbols-ps.conf: Cannot create symlink to ‘/usr/share/fontconfig/conf.avail/urw-standard-symbols-ps.conf’: No space left on device
tar: etc/fonts/conf.d/89-tlwg-kinnari-synthetic.conf: Cannot create symlink to ‘/usr/share/fontconfig/conf.avail/89-tlwg-kinnari-synthetic.conf’: No space left on device
tar: etc/fonts/conf.d/89-tlwg-laksaman-synthetic.conf: Cannot create symlink to ‘/usr/share/fontconfig/conf.avail/89-tlwg-laksaman-synthetic.conf’: No space left on device
tar: etc/fonts/conf.d/89-tlwg-garuda-synthetic.conf: Cannot create symlink to ‘/usr/share/fontconfig/conf.avail/89-tlwg-garuda-synthetic.conf’: No space left on device
tar: etc/alternatives/gdm3-theme.gresource: Cannot create symlink to ‘/usr/share/gnome-shell/theme/Yaru/gnome-shell-theme.gresource’: No space left on device
tar: Exiting with failure status due to previous errors
Failed. Your APPSIZE might be too small.
can you confirm on my flashing command ?
And I am using XAVIER NX
NO i havenot changed anything to update the APP size
this is present in the file flash_l4t_t194_spi_emmc_p3668_rootfs_ab.xml
<partition name="APP" type="data">
<allocation_policy> sequential </allocation_policy>
<filesystem_type> basic </filesystem_type>
<size> APPSIZE </size>
<file_system_attribute> 0 </file_system_attribute>
<allocation_attribute> 0x8 </allocation_attribute>
<align_boundary> 4096 </align_boundary>
<percent_reserved> 0 </percent_reserved>
<filename> APPFILE </filename>
<unique_guid> APPUUID </unique_guid>
<description> **Required.** Contains the rootfs. This partition must be defined
after `primary_GPT` so that it can be accessed as the fixed known special device
`/dev/mmcblk0p1`. </description>
</partition>
<partition name="APP_b" type="data">
<allocation_policy> sequential </allocation_policy>
<filesystem_type> basic </filesystem_type>
<size> APPSIZE </size>
<file_system_attribute> 0 </file_system_attribute>
<allocation_attribute> 0x8 </allocation_attribute>
<align_boundary> 4096 </align_boundary>
<percent_reserved> 0 </percent_reserved>
<filename> APPFILE_b </filename>
<unique_guid> APPUUID_b </unique_guid>
<description> **Required.** Contains the rootfs. This partition must be defined
after `primary_GPT` so that it can be accessed as the fixed known special device
`/dev/mmcblk0p2`. </description>
</partition>
yes , i have gone through this ticket , i have the following partition in flash_l4t_t194_spi_emmc_p3668_rootfs_ab.xml , what size should use instead of 18432 ?
<partition name="UDA" type="data">
<allocation_policy> sequential </allocation_policy>
<filesystem_type> basic </filesystem_type>
<size> 18432 </size>
<file_system_attribute> 0 </file_system_attribute>
<allocation_attribute> 0x808 </allocation_attribute>
<percent_reserved> 0 </percent_reserved>
<description> **Required.** Automatically takes all remaining space on the device except that
occupied by the `secondary_gpt` partition. Allocation attribute must be set to 0x808.
May be mounted and used to store user data. </description>
</partition>
i have below details in jetson-xavier-nx-devkit-emmc.conf
I’m curious what’s the modification you’ve done, and, which image you’ve working with?
for instance,
is it a Xavier NX developer kit? did you flashing with the native Jetpack-5.1.4 public release?
After running the sudo ROOTFS_AB=1 ./flash.sh jetson-xavier-nx-devkit-emmc mmcblk0p1 command, I was able to flash the board correctly. Could you give us a bit of context of the modifications that were done on the rootfs? Your error might indicate that your rootfs size is bigger than expected by the partition layout file.
After flashing the device, the rootfs partitions seem to have 7GB available as shown below:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 16M 1 loop
mmcblk0 179:0 0 14.7G 0 disk
├─mmcblk0p1 179:1 0 7G 0 part /
├─mmcblk0p2 179:2 0 7G 0 part
├─mmcblk0p3 179:3 0 64M 0 part
├─mmcblk0p4 179:4 0 448K 0 part
├─mmcblk0p5 179:5 0 32.6M 0 part
├─mmcblk0p6 179:6 0 2.5M 0 part
├─mmcblk0p7 179:7 0 64K 0 part
├─mmcblk0p8 179:8 0 1M 0 part
├─mmcblk0p9 179:9 0 1M 0 part
├─mmcblk0p10 179:10 0 1M 0 part
├─mmcblk0p11 179:11 0 1.5M 0 part
├─mmcblk0p12 179:12 0 1M 0 part
├─mmcblk0p13 179:13 0 64M 0 part
├─mmcblk0p14 179:14 0 448K 0 part
├─mmcblk0p15 179:15 0 32.5M 0 part
├─mmcblk0p16 179:16 0 80M 0 part
├─mmcblk0p17 179:17 0 512K 0 part
├─mmcblk0p18 179:18 0 100M 0 part
├─mmcblk0p19 179:19 0 64M 0 part
├─mmcblk0p20 179:20 0 80M 0 part
├─mmcblk0p21 179:21 0 512K 0 part
├─mmcblk0p22 179:22 0 64M 0 part
└─mmcblk0p23 179:23 0 101M 0 part
Is it possible to share any context of your customizations made prior to flashing the device?