Rootfs size overrides maxsize for core-image-sato

Hi,

I have been testing mender with the Jetson TX2. But I am unable to build the core-image-sato. I followed the demo tutorial for the tegra and I have a working example with core-image-base. but I can’t managed to follow this testing step

What I am doing wrong ?

Best regards,

Here is the output :
$ bitbake core-image-sato
Parsing recipes: 100% |#############################################################################################################################################################################| Time: 0:00:14
Parsing of 913 .bb files complete (0 cached, 913 parsed). 1395 targets, 79 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION           = "1.40.0"
BUILD_SYS            = "x86_64-linux"
NATIVELSBSTRING      = "universal"
TARGET_SYS           = "aarch64-poky-linux"
MACHINE              = "jetson-tx2"
DISTRO               = "poky"
DISTRO_VERSION       = "2.6.2"
TUNE_FEATURES        = "aarch64"
TARGET_FPU           = ""
meta                 
meta-poky            
meta-yocto-bsp       = "HEAD:2dd610cc27c606f731f83047b4766787aab6e6b2"
meta-tegra           = "HEAD:da90b42297f5d14d362015be1c5a888f5cac946a"
meta-mender-core     
meta-mender-demo     = "HEAD:0bbcde208ebb071b5e2268f0c1256fc468a61464"
meta-mender-tegra    = "HEAD:a9c746a09770051e0c9d35f4ddf30376f90ed5e8"

Initialising tasks: 100% |##########################################################################################################################################################################| Time: 0:00:05
Sstate summary: Wanted 455 Found 436 Missed 19 Current 1708 (95% match, 99% complete)
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: core-image-sato-1.0-r0 do_image_dataimg: The rootfs size 502780(K) overrides IMAGE_ROOTFS_MAXSIZE: 237436(K)
ERROR: core-image-sato-1.0-r0 do_image_dataimg: Function failed: set_image_size
ERROR: Logfile of failure stored in: /home/ubuntu/tegra/build/tmp/work/jetson_tx2-poky-linux/core-image-sato/1.0-r0/temp/log.do_image_dataimg.27368
ERROR: Task (/home/ubuntu/tegra/build/../sources/poky/meta/recipes-sato/images/core-image-sato.bb:do_image_dataimg) failed with exit code '1'
ERROR: core-image-sato-1.0-r0 do_image_ext4: The rootfs size 502780(K) overrides IMAGE_ROOTFS_MAXSIZE: 237436(K)
ERROR: core-image-sato-1.0-r0 do_image_ext4: Function failed: set_image_size
ERROR: Logfile of failure stored in: /home/ubuntu/tegra/build/tmp/work/jetson_tx2-poky-linux/core-image-sato/1.0-r0/temp/log.do_image_ext4.27369
ERROR: Task (/home/ubuntu/tegra/build/../sources/poky/meta/recipes-sato/images/core-image-sato.bb:do_image_ext4) failed with exit code '1'
NOTE: Tasks Summary: Attempted 6868 tasks of which 6565 didn't need to be rerun and 2 failed.

Summary: 2 tasks failed:
  /home/ubuntu/tegra/build/../sources/poky/meta/recipes-sato/images/core-image-sato.bb:do_image_dataimg
  /home/ubuntu/tegra/build/../sources/poky/meta/recipes-sato/images/core-image-sato.bb:do_image_ext4
Summary: There were 4 ERROR messages shown, returning a non-zero exit code.

The default settings assume that only 1024 MB is available for total storage, and this means that core-image-sato will probably not fit.

You need to adjust MENDER_STORAGE_TOTAL_SIZE_MB accordingly.

Thank you for your feedback.

I added in the local.conf
MENDER_STORAGE_TOTAL_SIZE_MB = 20000

The image builds properly. But the flashing fails now and stays stuck on Writing partition APP with core-image-sato.img

I tried rolling back to the default value + core-image-minimal and the flash works.

Best Regards

Archive:  core-image-sato-jetson-tx2--20190801081135.tegraflash.zip
  inflating: tegra186-a02-bpmp-quill-p3310-1000-c00-00-te770d-ucm2.dtb  
  inflating: emmc.cfg                
  inflating: warmboot.bin            
  inflating: tegra186-mb1-bct-pmic-quill-p3310-1000-c04.cfg  
  inflating: cboot.bin               
  inflating: tegra186-a02-bpmp-storm-p3489-evt-00-ta795sa-ucm1.dtb  
  inflating: tegra186-mb1-bct-pmic-quill-p3310-1000-c03.cfg  
  inflating: tegra186-a02-bpmp-storm-p3489-evt-00-ta795sa-ecc-disabled-ucm2.dtb  
  inflating: tegra186-mb1-bct-pinmux-quill-p3489-1000-a00.cfg  
  inflating: tegra186-mb1-bct-prod-quill-p3310-1000-a00.cfg  
  inflating: tegra186-mb1-bct-pmic-quill-p3310-1000-c01.cfg  
  inflating: tegra186-a02-bpmp-quill-p3310-1000-c01-00-te770d-ucm2.dtb  
  inflating: flash.xml.in            
  inflating: tegra186-mb1-bct-pmic-quill-p3310-1000-c02.cfg  
  inflating: tegra186-a02-bpmp-quill-p3310-1000-a00-00.dtb  
  inflating: tegra186-a02-bpmp-quill-p3310-1000-c04-00.dtb  
  inflating: bmp.blob                
  inflating: slot_metadata.bin       
  inflating: camera-rtcpu-sce.bin    
  inflating: mb1_prod.bin            
  inflating: minimal_scr.cfg         
  inflating: u-boot-jetson-tx2.bin   
  inflating: nvtboot_recovery_cpu.bin  
  inflating: tegra186-mb1-bct-bootrom-quill-p3310-1000-c03.cfg  
  inflating: tegra186-mb1-bct-prod-storm-p3489-1000-a00.cfg  
  inflating: tegra186-a02-bpmp-storm-p3489-a00-00-ta795sa-ucm1.dtb  
  inflating: tegra186-mb1-bct-pmic-quill-p3310-1000-a00.cfg  
  inflating: tegra186-mb1-bct-pinmux-quill-p3310-1000-c00.cfg  
  inflating: nvtboot_cpu.bin         
  inflating: tegra186-mb1-bct-pmic-quill-p3489-1000-a00.cfg  
  inflating: bpmp.bin                
  inflating: tegra186-a02-bpmp-quill-p3310-1000-c00-00.dtb  
  inflating: tegra186-mb1-bct-pad-quill-p3310-1000-c03.cfg  
  inflating: tegra186-mb1-bct-pinmux-quill-p3310-1000-a00.cfg  
  inflating: mb1_recovery_prod.bin   
  inflating: tegra186-a02-bpmp-quill-p3310-1000-c04-00-te770d-ucm2.dtb  
  inflating: tegra186-mb1-bct-prod-quill-p3310-1000-c03.cfg  
  inflating: mobile_scr.cfg          
  inflating: tegra186-mb1-bct-bootrom-quill-p3310-1000-a00.cfg  
  inflating: tos.img                 
  inflating: tegra186-mb1-bct-prod-quill-p3310-1000-c00.cfg  
  inflating: core-image-sato.img     
  inflating: tegra186-mb1-bct-pad-quill-p3489-1000-a00.cfg  
  inflating: tegra186-mb1-bct-pinmux-quill-p3310-1000-c03.cfg  
  inflating: tegra186-a02-bpmp-quill-p3310-1000-c01-00.dtb  
  inflating: tegra186-mb1-bct-misc-si-l4t.cfg  
  inflating: nvtboot.bin             
  inflating: tegra186-mb1-bct-pad-quill-p3310-1000-a00.cfg  
  inflating: tegra186-mb1-bct-bootrom-quill-p3310-1000-c00.cfg  
  inflating: tegra186-quill-p3310-1000-c03-00-base.dtb  
  inflating: tegra186-a02-bpmp-storm-p3489-evt-00-ta795sa-ucm2.dtb  
  inflating: tegra186-mb1-bct-pmic-quill-p3310-1000-c00.cfg  
  inflating: mce_mts_d15_prod_cr.bin  
  inflating: tegra186-a02-bpmp-quill-p3310-1000-a00-00-te770d-ucm2.dtb  
  inflating: jetson-tx2.cfg          
  inflating: core-image-sato-jetson-tx2.dataimg  
  inflating: tegra186-a02-bpmp-storm-p3489-a00-00-ta795sa-ucm2.dtb  
  inflating: tegra186-a02-bpmp-storm-p3489-a00-00-ta795sa-ecc-disabled-ucm2.dtb  
  inflating: nvtboot_recovery.bin    
  inflating: preboot_d15_prod_cr.bin  
  inflating: tegra186-a02-bpmp-storm-p3489-a00-00-ta795sa-ecc-disabled-ucm1.dtb  
  inflating: eks.img                 
   creating: tegra186-flash/
  inflating: tegra186-flash/tegrarcm_v2  
  inflating: tegra186-flash/tegra186-flash-helper.sh  
  inflating: tegra186-flash/tegraparser_v2  
  inflating: tegra186-flash/mkbootimg  
  inflating: tegra186-flash/rollback_parser.py  
  inflating: tegra186-flash/tegrasign_v2  
  inflating: tegra186-flash/nv_smd_generator  
  inflating: tegra186-flash/tegrabct_v2  
  inflating: tegra186-flash/tegradevflash_v2  
  inflating: tegra186-flash/mksparse  
  inflating: tegra186-flash/chkbdinfo  
  inflating: tegra186-flash/BUP_generator.py  
  inflating: tegra186-flash/mkgpt    
  inflating: tegra186-flash/tegraflash.py  
  inflating: tegra186-flash/tegrahost_v2  
  inflating: tegra186-flash/tegraflash_internal.py  
  inflating: doflash.sh              
  inflating: tegra186-a02-bpmp-storm-p3489-evt-00-ta795sa-ecc-disabled-ucm1.dtb  
  inflating: tegra186-mb1-bct-bootrom-quill-p3489-1000-a00.cfg  
  inflating: tegra186-mb1-bct-pad-quill-p3310-1000-c00.cfg  
  inflating: spe.bin                 
Welcome to Tegra Flash
version 1.0.0
Type ? or help for help and q or quit to exit
Use ! to execute system commands
 
[   0.0031 ] Generating RCM messages
[   0.0069 ] tegrarcm_v2 --listrcm rcm_list.xml --chip 0x18 --download rcm mb1_recovery_prod.bin 0 0
[   0.0077 ] RCM 0 is saved as rcm_0.rcm
[   0.0083 ] RCM 1 is saved as rcm_1.rcm
[   0.0083 ] List of rcm files are saved in rcm_list.xml
[   0.0083 ] 
[   0.0083 ] Signing RCM messages
[   0.0090 ] tegrasign_v2 --key None --list rcm_list.xml --pubkeyhash pub_key.key
[   0.0097 ] Assuming zero filled SBK key
[   0.0133 ] 
[   0.0133 ] Copying signature to RCM mesages
[   0.0196 ] tegrarcm_v2 --chip 0x18 --updatesig rcm_list_signed.xml
[   0.0208 ] 
[   0.0208 ] Boot Rom communication
[   0.0216 ] tegrarcm_v2 --chip 0x18 --rcm rcm_list_signed.xml
[   0.0223 ] BR_CID: 0x818010016430b8830400000008000240
[   0.0234 ] RCM version 0X180001
[   0.0397 ] Boot Rom communication completed
[   1.0458 ] 
[   1.0469 ] tegrarcm_v2 --isapplet
[   1.0477 ] Applet version 01.00.0000
[   1.0651 ] 
[   1.0661 ] Retrieving EEPROM data
[   1.0662 ] tegrarcm_v2 --oem platformdetails eeprom cvm /tmp/tmp.FMgGY8Yn6v/cvm.bin
[   1.0669 ] Applet version 01.00.0000
[   1.1010 ] Saved platform info in /tmp/tmp.FMgGY8Yn6v/cvm.bin
[   1.1989 ] 
Welcome to Tegra Flash
version 1.0.0
Type ? or help for help and q or quit to exit
Use ! to execute system commands
 
[   0.0057 ] tegrasign_v2 --key None --getmode mode.txt
[   0.0097 ] Assuming zero filled SBK key
[   0.0097 ] 
[   0.0098 ] Generating RCM messages
[   0.0137 ] tegrarcm_v2 --listrcm rcm_list.xml --chip 0x18 --download rcm mb1_recovery_prod.bin 0 0
[   0.0145 ] RCM 0 is saved as rcm_0.rcm
[   0.0148 ] RCM 1 is saved as rcm_1.rcm
[   0.0148 ] List of rcm files are saved in rcm_list.xml
[   0.0148 ] 
[   0.0148 ] Signing RCM messages
[   0.0157 ] tegrasign_v2 --key None --list rcm_list.xml --pubkeyhash pub_key.key
[   0.0223 ] Assuming zero filled SBK key
[   0.0262 ] 
[   0.0262 ] Copying signature to RCM mesages
[   0.0272 ] tegrarcm_v2 --chip 0x18 --updatesig rcm_list_signed.xml
[   0.0283 ] 
[   0.0283 ] Parsing partition layout
[   0.0292 ] tegraparser_v2 --pt flash.xml.tmp
[   0.0303 ] 
[   0.0303 ] Creating list of images to be signed
[   0.0310 ] tegrahost_v2 --chip 0x18 --partitionlayout flash.xml.bin --list images_list.xml zerosbk
[   0.0530 ] 
[   0.0530 ] Generating signatures
[   0.0539 ] tegrasign_v2 --key None --list images_list.xml --pubkeyhash pub_key.key
[   0.0546 ] Assuming zero filled SBK key
[   0.2686 ] 
[   0.2687 ] Generating br-bct
[   0.2701 ] Updating dev and MSS params in BR BCT
[   0.2702 ] tegrabct_v2 --dev_param emmc.cfg --sdram jetson-tx2.cfg --brbct br_bct.cfg --chip 0x18
[   0.2961 ] 
[   0.2962 ] Updating bl info
[   0.3023 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x18 --updateblinfo flash.xml.bin --updatesig images_list_signed.xml
[   0.3036 ] 
[   0.3036 ] Updating smd info
[   0.3045 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x18 --updatesmdinfo flash.xml.bin
[   0.3054 ] 
[   0.3054 ] Updating Odmdata
[   0.3061 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x18 --updatefields Odmdata =0x1090000
[   0.3103 ] 
[   0.3103 ] Get Signed section bct
[   0.3110 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x18 --listbct bct_list.xml
[   0.3118 ] 
[   0.3118 ] Signing BCT
[   0.3131 ] tegrasign_v2 --key None --list bct_list.xml --pubkeyhash pub_key.key
[   0.3138 ] Assuming zero filled SBK key
[   0.3140 ] 
[   0.3140 ] Updating BCT with signature
[   0.3147 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x18 --updatesig bct_list_signed.xml
[   0.3157 ] 
[   0.3157 ] Generating coldboot mb1-bct
[   0.3164 ] tegrabct_v2 --chip 0x18 --mb1bct mb1_cold_boot_bct.cfg --sdram jetson-tx2.cfg --misc tegra186-mb1-bct-misc-si-l4t.cfg --scr mobile_scr.cfg --pinmux tegra186-mb1-bct-pinmux-quill-p3310-1000-c03.cfg --pmc tegra186-mb1-bct-pad-quill-p3310-1000-c03.cfg --pmic tegra186-mb1-bct-pmic-quill-p3310-1000-c04.cfg --brcommand tegra186-mb1-bct-bootrom-quill-p3310-1000-c03.cfg --prod tegra186-mb1-bct-prod-quill-p3310-1000-c03.cfg
[   0.3171 ] MB1-BCT version: 0xe
[   0.3177 ] Copying Sdram info from 2 to 3 set
[   0.3403 ] Packing sdram param for instance[0]
[   0.3405 ] Packing sdram param for instance[1]
[   0.3407 ] Packing sdram param for instance[2]
[   0.3409 ] Packing sdram param for instance[3]

[   0.3411 ] Parsing config file :tegra186-mb1-bct-pinmux-quill-p3310-1000-c03.cfg 
[   0.3416 ] Appending platform config data of size :- 2904

[   0.3418 ] Parsing config file :mobile_scr.cfg 
[   0.3421 ] Appending platform config data of size :- 12240

[   0.3429 ] Parsing config file :tegra186-mb1-bct-pad-quill-p3310-1000-c03.cfg 
[   0.3433 ] Appending platform config data of size :- 24
[   0.3433 ] 
[   0.3433 ] Parsing config file :tegra186-mb1-bct-pmic-quill-p3310-1000-c04.cfg 
[   0.3433 ] Appending platform config data of size :- 708
[   0.3433 ] 
[   0.3433 ] Parsing config file :tegra186-mb1-bct-bootrom-quill-p3310-1000-c03.cfg 
[   0.3433 ] Appending platform config data of size :- 64
[   0.3433 ] 
[   0.3433 ] Parsing config file :tegra186-mb1-bct-prod-quill-p3310-1000-c03.cfg 
[   0.3433 ] Appending platform config data of size :- 1652
[   0.3433 ] 
[   0.3434 ] Updating mb1-bct with firmware information
[   0.3442 ] tegrabct_v2 --chip 0x18 --mb1bct mb1_cold_boot_bct_MB1.bct --updatefwinfo flash.xml.bin
[   0.3449 ] MB1-BCT version: 0xe
[   0.3453 ] 
[   0.3453 ] Updating mb1-bct with storage information
[   0.3460 ] tegrabct_v2 --chip 0x18 --mb1bct mb1_cold_boot_bct_MB1.bct --updatestorageinfo flash.xml.bin
[   0.3467 ] MB1-BCT version: 0xe
[   0.3471 ] 
[   0.3480 ] tegrahost_v2 --align mb1_cold_boot_bct_MB1.bct
[   0.3486 ] 
[   0.3493 ] tegrahost_v2 --appendsigheader mb1_cold_boot_bct_MB1.bct zerosbk
[   0.3501 ] 
[   0.3511 ] tegrasign_v2 --key None --list mb1_cold_boot_bct_MB1_sigheader.bct_list.xml
[   0.3517 ] Assuming zero filled SBK key
[   0.3532 ] 
[   0.3542 ] tegrahost_v2 --updatesigheader mb1_cold_boot_bct_MB1_sigheader.bct.encrypt mb1_cold_boot_bct_MB1_sigheader.bct.hash zerosbk
[   0.3550 ] 
[   0.3551 ] Generating recovery mb1-bct
[   0.3558 ] tegrabct_v2 --chip 0x18 --mb1bct mb1_bct.cfg --sdram jetson-tx2.cfg --misc tegra186-mb1-bct-misc-si-l4t.cfg --scr minimal_scr.cfg --pinmux tegra186-mb1-bct-pinmux-quill-p3310-1000-c03.cfg --pmc tegra186-mb1-bct-pad-quill-p3310-1000-c03.cfg --pmic tegra186-mb1-bct-pmic-quill-p3310-1000-c04.cfg --brcommand tegra186-mb1-bct-bootrom-quill-p3310-1000-c03.cfg --prod tegra186-mb1-bct-prod-quill-p3310-1000-c03.cfg
[   0.3571 ] MB1-BCT version: 0xe
[   0.3573 ] Copying Sdram info from 2 to 3 set
[   0.3817 ] Packing sdram param for instance[0]
[   0.3818 ] Packing sdram param for instance[1]
[   0.3818 ] Packing sdram param for instance[2]
[   0.3818 ] Packing sdram param for instance[3]
[   0.3818 ] 
[   0.3818 ] Parsing config file :tegra186-mb1-bct-pinmux-quill-p3310-1000-c03.cfg 
[   0.3818 ] Appending platform config data of size :- 2904
[   0.3818 ] 
[   0.3818 ] Parsing config file :minimal_scr.cfg 
[   0.3818 ] Appending platform config data of size :- 12240
[   0.3818 ] 
[   0.3818 ] Parsing config file :tegra186-mb1-bct-pad-quill-p3310-1000-c03.cfg 
[   0.3818 ] Appending platform config data of size :- 24
[   0.3818 ] 
[   0.3818 ] Parsing config file :tegra186-mb1-bct-pmic-quill-p3310-1000-c04.cfg 
[   0.3818 ] Appending platform config data of size :- 708
[   0.3819 ] 
[   0.3819 ] Parsing config file :tegra186-mb1-bct-bootrom-quill-p3310-1000-c03.cfg 
[   0.3819 ] Appending platform config data of size :- 64
[   0.3819 ] 
[   0.3819 ] Parsing config file :tegra186-mb1-bct-prod-quill-p3310-1000-c03.cfg 
[   0.3819 ] Appending platform config data of size :- 1652
[   0.3819 ] 
[   0.3820 ] Updating mb1-bct with firmware information
[   0.3829 ] tegrabct_v2 --chip 0x18 --mb1bct mb1_bct_MB1.bct --updatefwinfo flash.xml.bin
[   0.3836 ] MB1-BCT version: 0xe
[   0.3840 ] 
[   0.3841 ] Updating mb1-bct with storage information
[   0.3851 ] tegrabct_v2 --chip 0x18 --mb1bct mb1_bct_MB1.bct --updatestorageinfo flash.xml.bin
[   0.3860 ] MB1-BCT version: 0xe
[   0.3867 ] 
[   0.3875 ] tegrahost_v2 --align mb1_bct_MB1.bct
[   0.3882 ] 
[   0.3889 ] tegrahost_v2 --appendsigheader mb1_bct_MB1.bct zerosbk
[   0.3898 ] 
[   0.3907 ] tegrasign_v2 --key None --list mb1_bct_MB1_sigheader.bct_list.xml
[   0.3914 ] Assuming zero filled SBK key
[   0.3931 ] 
[   0.3942 ] tegrahost_v2 --updatesigheader mb1_bct_MB1_sigheader.bct.encrypt mb1_bct_MB1_sigheader.bct.hash zerosbk
[   0.3951 ] 
[   0.3952 ] Copying signatures
[   0.3960 ] tegrahost_v2 --chip 0x18 --partitionlayout flash.xml.bin --updatesig images_list_signed.xml
[   0.4242 ] 
[   0.4243 ] Boot Rom communication
[   0.4252 ] tegrarcm_v2 --chip 0x18 --rcm rcm_list_signed.xml
[   0.4259 ] BootRom is not running
[   1.4622 ] 
[   1.4632 ] tegrarcm_v2 --isapplet
[   1.4640 ] Applet version 01.00.0000
[   1.4799 ] 
[   1.4799 ] Retrieving board information
[   1.4809 ] tegrarcm_v2 --oem platformdetails chip chip_info.bin
[   1.4816 ] Applet version 01.00.0000
[   1.5159 ] Saved platform info in chip_info.bin
[   1.5173 ] Chip minor revision: 2
[   1.5296 ] 
[   1.5297 ] Sending BCTs
[   1.5309 ] tegrarcm_v2 --download bct_bootrom br_bct_BR.bct --download bct_mb1 mb1_bct_MB1_sigheader.bct.encrypt
[   1.5316 ] Applet version 01.00.0000
[   1.5481 ] Sending bct_bootrom
[   1.5482 ] [................................................] 100%
[   1.5580 ] Sending bct_mb1
[   1.5641 ] [................................................] 100%
[   1.9207 ] 
[   1.9207 ] Generating blob
[   1.9216 ] tegrahost_v2 --align blob_nvtboot_recovery_cpu.bin
[   1.9223 ] 
[   1.9228 ] tegrahost_v2 --appendsigheader blob_nvtboot_recovery_cpu.bin zerosbk
[   1.9237 ] 
[   1.9244 ] tegrasign_v2 --key None --list blob_nvtboot_recovery_cpu_sigheader.bin_list.xml
[   1.9249 ] Assuming zero filled SBK key
[   1.9287 ] 
[   1.9295 ] tegrahost_v2 --updatesigheader blob_nvtboot_recovery_cpu_sigheader.bin.encrypt blob_nvtboot_recovery_cpu_sigheader.bin.hash zerosbk
[   1.9303 ] 
[   1.9309 ] tegrahost_v2 --align blob_nvtboot_recovery.bin
[   1.9315 ] 
[   1.9321 ] tegrahost_v2 --appendsigheader blob_nvtboot_recovery.bin zerosbk
[   1.9328 ] 
[   1.9335 ] tegrasign_v2 --key None --list blob_nvtboot_recovery_sigheader.bin_list.xml
[   1.9341 ] Assuming zero filled SBK key
[   1.9357 ] 
[   1.9365 ] tegrahost_v2 --updatesigheader blob_nvtboot_recovery_sigheader.bin.encrypt blob_nvtboot_recovery_sigheader.bin.hash zerosbk
[   1.9371 ] 
[   1.9377 ] tegrahost_v2 --align blob_preboot_d15_prod_cr.bin
[   1.9383 ] 
[   1.9388 ] tegrahost_v2 --appendsigheader blob_preboot_d15_prod_cr.bin zerosbk
[   1.9394 ] 
[   1.9401 ] tegrasign_v2 --key None --list blob_preboot_d15_prod_cr_sigheader.bin_list.xml
[   1.9406 ] Assuming zero filled SBK key
[   1.9419 ] 
[   1.9426 ] tegrahost_v2 --updatesigheader blob_preboot_d15_prod_cr_sigheader.bin.encrypt blob_preboot_d15_prod_cr_sigheader.bin.hash zerosbk
[   1.9432 ] 
[   1.9439 ] tegrahost_v2 --align blob_mce_mts_d15_prod_cr.bin
[   1.9444 ] 
[   1.9450 ] tegrahost_v2 --appendsigheader blob_mce_mts_d15_prod_cr.bin zerosbk
[   1.9481 ] 
[   1.9489 ] tegrasign_v2 --key None --list blob_mce_mts_d15_prod_cr_sigheader.bin_list.xml
[   1.9495 ] Assuming zero filled SBK key
[   2.0168 ] 
[   2.0182 ] tegrahost_v2 --updatesigheader blob_mce_mts_d15_prod_cr_sigheader.bin.encrypt blob_mce_mts_d15_prod_cr_sigheader.bin.hash zerosbk
[   2.0220 ] 
[   2.0232 ] tegrahost_v2 --align blob_bpmp.bin
[   2.0240 ] 
[   2.0248 ] tegrahost_v2 --appendsigheader blob_bpmp.bin zerosbk
[   2.0265 ] 
[   2.0276 ] tegrasign_v2 --key None --list blob_bpmp_sigheader.bin_list.xml
[   2.0295 ] Assuming zero filled SBK key
[   2.0441 ] 
[   2.0454 ] tegrahost_v2 --updatesigheader blob_bpmp_sigheader.bin.encrypt blob_bpmp_sigheader.bin.hash zerosbk
[   2.0469 ] 
[   2.0478 ] tegrahost_v2 --align blob_tegra186-a02-bpmp-quill-p3310-1000-c04-00-te770d-ucm2.dtb
[   2.0485 ] 
[   2.0493 ] tegrahost_v2 --appendsigheader blob_tegra186-a02-bpmp-quill-p3310-1000-c04-00-te770d-ucm2.dtb zerosbk
[   2.0509 ] 
[   2.0520 ] tegrasign_v2 --key None --list blob_tegra186-a02-bpmp-quill-p3310-1000-c04-00-te770d-ucm2_sigheader.dtb_list.xml
[   2.0530 ] Assuming zero filled SBK key
[   2.0667 ] 
[   2.0684 ] tegrahost_v2 --updatesigheader blob_tegra186-a02-bpmp-quill-p3310-1000-c04-00-te770d-ucm2_sigheader.dtb.encrypt blob_tegra186-a02-bpmp-quill-p3310-1000-c04-00-te770d-ucm2_sigheader.dtb.hash zerosbk
[   2.0737 ] 
[   2.0749 ] tegrahost_v2 --align blob_tos.img
[   2.0756 ] 
[   2.0764 ] tegrahost_v2 --appendsigheader blob_tos.img zerosbk
[   2.0772 ] 
[   2.0783 ] tegrasign_v2 --key None --list blob_tos_sigheader.img_list.xml
[   2.0789 ] Assuming zero filled SBK key
[   2.0810 ] 
[   2.0821 ] tegrahost_v2 --updatesigheader blob_tos_sigheader.img.encrypt blob_tos_sigheader.img.hash zerosbk
[   2.0830 ] 
[   2.0838 ] tegrahost_v2 --align blob_eks.img
[   2.0846 ] 
[   2.0853 ] tegrahost_v2 --appendsigheader blob_eks.img zerosbk
[   2.0861 ] 
[   2.0870 ] tegrasign_v2 --key None --list blob_eks_sigheader.img_list.xml
[   2.0876 ] Assuming zero filled SBK key
[   2.0878 ] 
[   2.0888 ] tegrahost_v2 --updatesigheader blob_eks_sigheader.img.encrypt blob_eks_sigheader.img.hash zerosbk
[   2.0896 ] 
[   2.0904 ] tegrahost_v2 --align blob_tegra186-quill-p3310-1000-c03-00-base.dtb
[   2.0911 ] 
[   2.0918 ] tegrahost_v2 --appendsigheader blob_tegra186-quill-p3310-1000-c03-00-base.dtb zerosbk
[   2.0929 ] 
[   2.0939 ] tegrasign_v2 --key None --list blob_tegra186-quill-p3310-1000-c03-00-base_sigheader.dtb_list.xml
[   2.0946 ] Assuming zero filled SBK key
[   2.1033 ] 
[   2.1046 ] tegrahost_v2 --updatesigheader blob_tegra186-quill-p3310-1000-c03-00-base_sigheader.dtb.encrypt blob_tegra186-quill-p3310-1000-c03-00-base_sigheader.dtb.hash zerosbk
[   2.1057 ] 
[   2.1067 ] tegrahost_v2 --generateblob blob.xml blob.bin
[   2.1073 ] number of images in blob are 9
[   2.1076 ] blobsize is 3749304
[   2.1078 ] Added binary blob_nvtboot_recovery_cpu_sigheader.bin.encrypt of size 190048
[   2.1094 ] Added binary blob_nvtboot_recovery_sigheader.bin.encrypt of size 79600
[   2.1099 ] Added binary blob_preboot_d15_prod_cr_sigheader.bin.encrypt of size 63024
[   2.1104 ] Added binary blob_mce_mts_d15_prod_cr_sigheader.bin.encrypt of size 2076832
[   2.1109 ] Added binary blob_bpmp_sigheader.bin.encrypt of size 529440
[   2.1113 ] Added binary blob_tegra186-a02-bpmp-quill-p3310-1000-c04-00-te770d-ucm2_sigheader.dtb.encrypt of size 466160
[   2.1119 ] Added binary blob_tos_sigheader.img.encrypt of size 62976
[   2.1123 ] Added binary blob_eks_sigheader.img.encrypt of size 1488
[   2.1127 ] Added binary blob_tegra186-quill-p3310-1000-c03-00-base_sigheader.dtb.encrypt of size 279584
[   2.1176 ] 
[   2.1177 ] Sending bootloader and pre-requisite binaries
[   2.1187 ] tegrarcm_v2 --download blob blob.bin
[   2.1194 ] Applet version 01.00.0000
[   2.1364 ] Sending blob
[   2.1365 ] [................................................] 100%
[   2.5435 ] 
[   2.5445 ] tegrarcm_v2 --boot recovery
[   2.5452 ] Applet version 01.00.0000
[   2.5663 ] 
[   2.5672 ] tegrarcm_v2 --isapplet
[   3.2246 ] 
[   3.2255 ] tegradevflash_v2 --iscpubl
[   3.2262 ] CPU Bootloader is not running on device.
[   3.2265 ] 
[   4.4720 ] Retrieving storage infomation
[   4.4729 ] tegrarcm_v2 --oem platformdetails storage storage_info.bin
[   4.4736 ] Applet is not running on device. Continue with Bootloader
[   4.5297 ] 
[   4.5314 ] tegradevflash_v2 --oem platformdetails storage storage_info.bin
[   4.5325 ] Bootloader version 01.00.0000
[   4.5343 ] Saved platform info in storage_info.bin
[   4.5392 ] 
[   4.5393 ] Flashing the device
[   4.5403 ] tegraparser_v2 --storageinfo storage_info.bin --generategpt --pt flash.xml.bin
[   4.5414 ] 
[   4.5421 ] tegradevflash_v2 --pt flash.xml.bin --create
[   4.5428 ] Bootloader version 01.00.0000
[   4.5445 ] Erasing sdmmc_boot: 3 ......... [Done]
[   4.5876 ] Writing partition secondary_gpt with gpt_secondary_0_3.bin
[   4.5878 ] [................................................] 100%

[   4.6497 ] Erasing sdmmc_user: 3 ......... [Done]
[   5.1834 ] Writing partition master_boot_record with mbr_1_3.bin
[   5.1836 ] [................................................] 100%
[   5.1913 ] Writing partition primary_gpt with gpt_primary_1_3.bin
[   5.1957 ] [................................................] 100%
[   5.2039 ] Writing partition secondary_gpt with gpt_secondary_1_3.bin
[   5.2192 ] [................................................] 100%

[   5.2432 ] Writing partition mb1 with mb1_prod.bin.encrypt
[   5.2434 ] [................................................] 100%
[   5.2539 ] Writing partition mb1_b with mb1_prod.bin.encrypt
[   5.2776 ] [................................................] 100%
[   5.2882 ] Writing partition spe-fw with spe_sigheader.bin.encrypt
[   5.3140 ] [................................................] 100%
[   5.3243 ] Writing partition spe-fw_b with spe_sigheader.bin.encrypt
[   5.3369 ] [................................................] 100%
[   5.3476 ] Writing partition mb2 with nvtboot_sigheader.bin.encrypt
[   5.3554 ] [................................................] 100%
[   5.3664 ] Writing partition mb2_b with nvtboot_sigheader.bin.encrypt
[   5.4082 ] [................................................] 100%
[   5.4192 ] Writing partition mts-preboot with preboot_d15_prod_cr_sigheader.bin.encrypt
[   5.4670 ] [................................................] 100%
[   5.4776 ] Writing partition mts-preboot_b with preboot_d15_prod_cr_sigheader.bin.encrypt
[   5.5238 ] [................................................] 100%
[   5.5345 ] Writing partition SMD with slot_metadata.bin
[   5.5897 ] [................................................] 100%
[   5.5977 ] Writing partition SMD_b with slot_metadata.bin
[   5.6069 ] [................................................] 100%
[   5.6151 ] Writing partition master_boot_record with mbr_1_3.bin
[   5.6673 ] [................................................] 100%
[   5.6753 ] Writing partition APP with core-image-sato.img
[   5.6797 ] [                                                ] 000%

Here is my local.conf

#

# This file is your local configuration file and is where all local user settings

# are placed. The comments in this file give some guide to the options a new user

# to the system might want to change but pretty much any configuration option can

# be set in this file. More adventurous users can look at local.conf.extended

# which contains other examples of configuration which can be placed in this file

# but new users likely won't need any of them initially.

#

# Lines starting with the '#' character are commented out and in some cases the

# default values are provided as comments to show people example syntax. Enabling

# the option is a question of removing the # character and making any change to the

# variable as required.

#

# Machine Selection

#

# You need to select a specific machine to target the build with. There are a selection

# of emulated machines available which can boot and run in the QEMU emulator:

#

#MACHINE ?= "qemuarm"

#MACHINE ?= "qemuarm64"

#MACHINE ?= "qemumips"

#MACHINE ?= "qemumips64"

#MACHINE ?= "qemuppc"

#MACHINE ?= "qemux86"

#MACHINE ?= "qemux86-64"

#

# There are also the following hardware board target machines included for

# demonstration purposes:

#

#MACHINE ?= "beaglebone-yocto"

#MACHINE ?= "genericx86"

#MACHINE ?= "genericx86-64"

#MACHINE ?= "mpc8315e-rdb"

#MACHINE ?= "edgerouter"

#

# This sets the default machine to be qemux86 if no other machine is selected:

MACHINE ??= "qemux86"

#

# Where to place downloads

#

# During a first build the system will download many different source code tarballs

# from various upstream projects. This can take a while, particularly if your network

# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you

# can preserve this directory to speed up this part of subsequent builds. This directory

# is safe to share between multiple builds on the same machine too.

#

# The default is a downloads directory under TOPDIR which is the build directory.

#

#DL_DIR ?= "${TOPDIR}/downloads"

#

# Where to place shared-state files

#

# BitBake has the capability to accelerate builds based on previously built output.

# This is done using "shared state" files which can be thought of as cache objects

# and this option determines where those files are placed.

#

# You can wipe out TMPDIR leaving this directory intact and the build would regenerate

# from these files if no changes were made to the configuration. If changes were made

# to the configuration, only shared state files where the state was still valid would

# be used (done using checksums).

#

# The default is a sstate-cache directory under TOPDIR.

#

#SSTATE_DIR ?= "${TOPDIR}/sstate-cache"

#

# Where to place the build output

#

# This option specifies where the bulk of the building work should be done and

# where BitBake should place its temporary files and output. Keep in mind that

# this includes the extraction and compilation of many applications and the toolchain

# which can use Gigabytes of hard disk space.

#

# The default is a tmp directory under TOPDIR.

#

#TMPDIR = "${TOPDIR}/tmp"

#

# Default policy config

#

# The distribution setting controls which policy settings are used as defaults.

# The default value is fine for general Yocto project use, at least initially.

# Ultimately when creating custom policy, people will likely end up subclassing

# these defaults.

#

DISTRO ?= "poky"

# As an example of a subclass there is a "bleeding" edge policy configuration

# where many versions are set to the absolute latest code from the upstream

# source control systems. This is just mentioned here as an example, its not

# useful to most new users.

# DISTRO ?= "poky-bleeding"

#

# Package Management configuration

#

# This variable lists which packaging formats to enable. Multiple package backends

# can be enabled at once and the first item listed in the variable will be used

# to generate the root filesystems.

# Options are:

# - 'package_deb' for debian style deb files

# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager)

# - 'package_rpm' for rpm style packages

# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk"

# We default to rpm:

PACKAGE_CLASSES ?= "package_rpm"

#

# SDK target architecture

#

# This variable specifies the architecture to build SDK items for and means

# you can build the SDK packages for architectures other than the machine you are

# running the build on (i.e. building i686 packages on an x86_64 host).

# Supported values are i686 and x86_64

#SDKMACHINE ?= "i686"

#

# Extra image configuration defaults

#

# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated

# images. Some of these options are added to certain image types automatically. The

# variable can contain the following options:

# "dbg-pkgs" - add -dbg packages for all installed packages

# (adds symbol information for debugging/profiling)

# "dev-pkgs" - add -dev packages for all installed packages

# (useful if you want to develop against libs in the image)

# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages

# (useful if you want to run the package test suites)

# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.)

# "tools-debug" - add debugging tools (gdb, strace)

# "eclipse-debug" - add Eclipse remote debugging support

# "tools-profile" - add profiling tools (oprofile, lttng, valgrind)

# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.)

# "debug-tweaks" - make an image suitable for development

# e.g. ssh root access has a blank password

# There are other application targets that can be used here too, see

# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details.

# We default to enabling the debugging tweaks.

EXTRA_IMAGE_FEATURES ?= "debug-tweaks"

#

# Additional image features

#

# The following is a list of additional classes to use when building images which

# enable extra features. Some available options which can be included in this variable

# are:

# - 'buildstats' collect build statistics

# - 'image-mklibs' to reduce shared library files size for an image

# - 'image-prelink' in order to prelink the filesystem image

# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink

# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended

USER_CLASSES ?= "buildstats image-mklibs image-prelink"

#

# Runtime testing of images

#

# The build system can test booting virtual machine images under qemu (an emulator)

# after any root filesystems are created and run tests against those images. It can also

# run tests against any SDK that are built. To enable this uncomment these lines.

# See classes/test{image,sdk}.bbclass for further details.

#IMAGE_CLASSES += "testimage testsdk"

#TESTIMAGE_AUTO_qemuall = "1"

#

# Interactive shell configuration

#

# Under certain circumstances the system may need input from you and to do this it

# can launch an interactive shell. It needs to do this since the build is

# multithreaded and needs to be able to handle the case where more than one parallel

# process may require the user's attention. The default is iterate over the available

# terminal types to find one that works.

#

# Examples of the occasions this may happen are when resolving patches which cannot

# be applied, to use the devshell or the kernel menuconfig

#

# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none

# Note: currently, Konsole support only works for KDE 3.x due to the way

# newer Konsole versions behave

#OE_TERMINAL = "auto"

# By default disable interactive patch resolution (tasks will just fail instead):

PATCHRESOLVE = "noop"

#

# Disk Space Monitoring during the build

#

# Monitor the disk space during the build. If there is less that 1GB of space or less

# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully

# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort

# of the build. The reason for this is that running completely out of space can corrupt

# files and damages the build in ways which may not be easily recoverable.

# It's necesary to monitor /tmp, if there is no space left the build will fail

# with very exotic errors.

BB_DISKMON_DIRS ??= "\

STOPTASKS,${TMPDIR},1G,100K \

STOPTASKS,${DL_DIR},1G,100K \

STOPTASKS,${SSTATE_DIR},1G,100K \

STOPTASKS,/tmp,100M,100K \

ABORT,${TMPDIR},100M,1K \

ABORT,${DL_DIR},100M,1K \

ABORT,${SSTATE_DIR},100M,1K \

ABORT,/tmp,10M,1K"

#

# Shared-state files from other locations

#

# As mentioned above, shared state files are prebuilt cache data objects which can

# used to accelerate build time. This variable can be used to configure the system

# to search other mirror locations for these objects before it builds the data itself.

#

# This can be a filesystem directory, or a remote url such as http or ftp. These

# would contain the sstate-cache results from previous builds (possibly from other

# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the

# cache locations to check for the shared objects.

# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH

# at the end as shown in the examples below. This will be substituted with the

# correct path within the directory structure.

#SSTATE_MIRRORS ?= "\

#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \

#file://.* file:///some/local/dir/sstate/PATH"

#

# Yocto Project SState Mirror

#

# The Yocto Project has prebuilt artefacts available for its releases, you can enable

# use of these by uncommenting the following line. This will mean the build uses

# the network to check for artefacts at the start of builds, which does slow it down

# equally, it will also speed up the builds by not having to build things if they are

# present in the cache. It assumes you can download something faster than you can build it

# which will depend on your network.

#

#SSTATE_MIRRORS ?= "file://.* http://sstate.yoctoproject.org/2.5/PATH;downloadfilename=PATH"

#

# Qemu configuration

#

# By default qemu will build with a builtin VNC server where graphical output can be

# seen. The two lines below enable the SDL backend too. By default libsdl2-native will

# be built, if you want to use your host's libSDL instead of the minimal libsdl built

# by libsdl2-native then uncomment the ASSUME_PROVIDED line below.

PACKAGECONFIG_append_pn-qemu-native = " sdl"

PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl"

#ASSUME_PROVIDED += "libsdl2-native"

# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to

# track the version of this file when it was generated. This can safely be ignored if

# this doesn't mean anything to you.

CONF_VERSION = "1"

# Appended fragment from meta-mender-community/templates

# This really saves a lot of disk space!

INHERIT += "rm_work"

# The name of the disk image and Artifact that will be built.

# This is what the device will report that it is running, and different updates

# must have different names because Mender will skip installation of an Artifact

# if it is already installed.

MENDER_ARTIFACT_NAME = "release-3"

INHERIT += "mender-full"

DISTRO_FEATURES_append = " systemd"

VIRTUAL-RUNTIME_init_manager = "systemd"

DISTRO_FEATURES_BACKFILL_CONSIDERED = "sysvinit"

VIRTUAL-RUNTIME_initscripts = ""

# Build for Hosted Mender

#

# To get your tenant token:

# - log in to https://hosted.mender.io

# - click your email at the top right and then "My organization"

# - press the "COPY TO CLIPBOARD"

# - assign content of clipboard to MENDER_TENANT_TOKEN

#

MENDER_SERVER_URL = "https://hosted.mender.io"

MENDER_TENANT_TOKEN = ""

#MENDER_TENANT_TOKEN = ""

# Build for Mender demo server

#

# https://docs.mender.io/getting-started/create-a-test-environment

#

# Uncomment below and update IP address to match the machine running the

# Mender demo server

#MENDER_DEMO_HOST_IP_ADDRESS = "192.168.0.100"

# Build for Mender production setup (on-prem)

#

# https://docs.mender.io/artifacts/building-for-production

#

# Uncomment below and update the URL to match your configured domain

# name and provide the path to the generated server.crt file.

#

# NOTE! It is recommend that you provide below information in your custom

# Yocto layer and this is only for demo purposes. See linked documentation

# for additional information.

#MENDER_SERVER_URL = "https://docker.mender.io"

#FILESEXTRAPATHS_prepend_pn-mender := "<DIRECTORY-CONTAINING-server.crt>:"

#SRC_URI_append_pn-mender = " file://server.crt"

# Appended fragment from meta-mender-community/meta-mender-tegra/templates

MACHINE ?= "jetson-tx2"

# meta-tegra and tegraflash requirements

IMAGE_CLASSES += "image_types_mender_tegra"

IMAGE_FSTYPES += "tegraflash"

# Drive size 31268536320

# MENDER_STORAGE_TOTAL_SIZE_MB = "31268"

MENDER_STORAGE_TOTAL_SIZE_MB = "16384"

ARTIFACTIMG_FSTYPE = "ext4"

# Generate dataimg for use with tegraflash

IMAGE_TYPEDEP_tegraflash += " dataimg"

IMAGE_FSTYPES += "dataimg"

# Additional mender settings, See discussion in VS-68

EXTRA_IMAGECMD_ext4 = " -b 2048"

PREFERRED_PROVIDER_u-boot-fw-utils = "u-boot-fw-utils-tegra"

PREFERRED_RPROVIDER_u-boot-fw-utils = "u-boot-fw-utils-tegra"

# Note: this isn't really a boot file, just put it here to keep the mender build from

# complaining about empty IMAGE_BOOT_FILES. We won't use the full image anyway, just the mender file

IMAGE_BOOT_FILES = "u-boot-dtb.bin"

# Mender customizations to support jetson tx2. This needs to match up with flash_l4t_t186.custom.xml scheme

# We don't use a boot partition

MENDER_BOOT_PART = ""

MENDER_DATA_PART = "${MENDER_STORAGE_DEVICE_BASE}30"

MENDER_ROOTFS_PART_A = "${MENDER_STORAGE_DEVICE_BASE}1"

MENDER_ROOTFS_PART_B = "${MENDER_STORAGE_DEVICE_BASE}29"

# See setting in meta-tegra/conf/machine

# Need to oversize this to make sure IMAGE_ROOTFS_SIZE is less than this, however any change

# will mean you need to change the offsets below as well.

ROOTFSPART_SIZE = "3000000000"

# Assumes a default partition layout for jetson with partition 28 reserved for uboot environment

# At LBA 0x68b170. 0x68b170 = 6861168 blocks and 6861168 blocks *512 bytes/block = 3512918016 byte offset

# This will need to be modified whenever flash layout changes

# Use mmc part command in u-boot to find partition start for any new platforms

MENDER_UBOOT_ENV_STORAGE_DEVICE_OFFSET = "3512918016"

MENDER_RESERVED_SPACE_BOOTLOADER_DATA = "262144"

# Use a 4096 byte alignment for support of tegraflash scheme and default partition locations

MENDER_PARTITION_ALIGNMENT = "4096"

# Not required, gives you access via SSH by default

EXTRA_IMAGE_FEATURES += " ssh-server-dropbear"

# See https://hub.mender.io/t/yocto-thud-release-and-mender/144

# Default for thud and later is grub integration but we need to use u-boot integration already included.

# Leave out sdimg since we don't use this with tegra (instead use tegraflash)

MENDER_FEATURES_ENABLE_append = " mender-uboot"

MENDER_FEATURES_DISABLE_append = " mender-grub mender-image-uefi"

Unfortunately I am not familiar with how tegraflash works.

Maybe @dwalkes has some additional insights as he has done the integration, or you can check with the meta-tegra folks.

@Austriker and @mirzak,
The instructions for growing rootfs on tegra are different and not well documented.
I was in the process of cleaning up the rootfs size calculations for tegra to make growing the rootfs easier when I found the issue described in U-boot environment located past 0xFFFFFFFF fails which I think will block you as well if you need a rootfs size > 4G. I haven’t tried sato yet but will try after I get these changes working, and will push a working branch this morning in case you want to try the latest or help with changes.

@dwalkes Yes you are right. Just tried with MENDER_STORAGE_TOTAL_SIZE_MB = "3800" and I managed to flash the jetson with image-core-sato and it’s running.

But I am not sure 4G will be enough for us since we use a lot of big libraries. So if you have something I can test I will.

@Austriker thanks for the offer to help test. I’ve posted a link to my working changes in U-boot environment located past 0xFFFFFFFF fails. They probably don’t work yet but I thought I’d get them out there in case you are blocked on this today. I should have more time to look at them tonight.

1 Like