madisongh/test-distro

My old test distro setup

test-distro's Issues

Conditions for eks partition update from runtime?

I'm seeing the below problem writing the eks partition with the changes introduced by 6bacf26. When would this be expected to work? I don't have secureboot enabled, and I wonder if that has something to do with the failure.

root@jetson-tx2:~# nv_update_engine -i
Nvidia A/B-Redundancy Update tool Version 1.2
A/B has been disabled. Need to enable A/B.
root@jetson-tx2:~# nv_update_engine -e
Nvidia A/B-Redundancy Update tool Version 1.2
enabling A/B redundancy
A/B Redundancy has been enabled.
root@jetson-tx2:~# nv_update_engine -i
Nvidia A/B-Redundancy Update tool Version 1.2
current slot 0
Start updating slot 1
Tegra User Block Device: /dev/disk/by-partlabel
Tegra Boot Block Device: /dev/mmcblk0boot0
HEADER: MAGIC NVIDIA__BLOB__V2
HEX_VALUE 131072
BLOB_SIZE 50493333
HEADER_SIZE 48
NUMBER_OF_ELEMENTS 45
HEADER_TYPE 0
UNCOMP_SIZE 50493333
MB1_RATCHET_LV 0
MTS_RATCHET_LV 0
ROLLBACK_FUSE_LV 0
config COMPATIBLE_SPEC not found in /etc/nv_boot_control.conf
Device TN Spec: 3310-D00-1000-F.0-1-0-jetson-tx2-mmcblk0p1
config COMPATIBLE_SPEC not found in /etc/nv_boot_control.conf
Device TN Spec: 3310-D00-1000-F.0-1-0-jetson-tx2-mmcblk0p1
Device is fused board.
ENTRY_TABLE:
PART  POS  LEN  VER TNSPEC TYPE UPDATABLE
bpmp-fw  5448  533904  2    1  1
sce-fw  539352  125568  2    1  1
cpu-bootloader  664920  284688  2    1  1
mb2  949608  116832  2    0  1
spe-fw  1066440  95984  2    0  1
secure-os  1162424  249968  2    1  1
adsp-fw  1412392  108208  2    1  1
dram-ecc-fw  1520600  52368  2    0  1
badpage-fw  1572968  4496  2    0  1
eks  1577464  1440  2    1  1
mb1  1578904  99664  2    2  1
mts-bootpack  1678568  2082144  2    1  1
mts-preboot  3760712  63104  2    0  1
sc7  3823816  23632  2    1  1
bpmp-fw-dtb  3847448  605120  2  3310-B00-1000--1-0-jetson-tx2-mmcblk0p1  1  0
bpmp-fw-dtb  4452568  605120  2  3310-B02-1000--1-0-jetson-tx2-mmcblk0p1  1  0
bpmp-fw-dtb  5057688  605120  2  3310-C04-1000--1-0-jetson-tx2-mmcblk0p1  1  0
bpmp-fw-dtb  5662808  605120  2  3310-D00-1000--1-0-jetson-tx2-mmcblk0p1  1  1
bpmp-fw-dtb  6267928  605120  2  3310-D01-1000--1-0-jetson-tx2-mmcblk0p1  1  0
bootloader-dtb  6873048  371808  2  3310-B00-1000--1-0-jetson-tx2-mmcblk0p1  1  0
bootloader-dtb  7244856  371808  2  3310-B02-1000--1-0-jetson-tx2-mmcblk0p1  1  0
bootloader-dtb  7616664  371808  2  3310-C04-1000--1-0-jetson-tx2-mmcblk0p1  1  0
bootloader-dtb  7988472  371808  2  3310-D00-1000--1-0-jetson-tx2-mmcblk0p1  1  1
bootloader-dtb  8360280  371808  2  3310-D01-1000--1-0-jetson-tx2-mmcblk0p1  1  0
VER  8732088  102  2  3310-B00-1000--1-0-jetson-tx2-mmcblk0p1  0  0
VER  8732190  102  2  3310-B02-1000--1-0-jetson-tx2-mmcblk0p1  0  0
VER  8732292  102  2  3310-C04-1000--1-0-jetson-tx2-mmcblk0p1  0  0
VER  8732394  102  2  3310-D00-1000--1-0-jetson-tx2-mmcblk0p1  0  1
VER  8732496  101  2  3310-D01-1000--1-0-jetson-tx2-mmcblk0p1  0  0
BCT  8732597  3584  2  3310-B00-1000--1-0-jetson-tx2-mmcblk0p1  2  0
BCT  8736181  3584  2  3310-B02-1000--1-0-jetson-tx2-mmcblk0p1  2  0
BCT  8739765  3584  2  3310-C04-1000--1-0-jetson-tx2-mmcblk0p1  2  0
BCT  8743349  3584  2  3310-D00-1000--1-0-jetson-tx2-mmcblk0p1  2  1
BCT  8746933  3584  2  3310-D01-1000--1-0-jetson-tx2-mmcblk0p1  2  0
MB1_BCT  8750517  50096  2  3310-B00-1000--1-0-jetson-tx2-mmcblk0p1  0  0
MB1_BCT  8800613  50096  2  3310-B02-1000--1-0-jetson-tx2-mmcblk0p1  0  0
MB1_BCT  8850709  50096  2  3310-C04-1000--1-0-jetson-tx2-mmcblk0p1  0  0
MB1_BCT  8900805  50096  2  3310-D00-1000--1-0-jetson-tx2-mmcblk0p1  0  1
MB1_BCT  8950901  50096  2  3310-D01-1000--1-0-jetson-tx2-mmcblk0p1  0  0
kernel  9000997  39633296  2    1  1
kernel-dtb  48634293  371808  2  3310-B00-1000--1-0-jetson-tx2-mmcblk0p1  1  0
kernel-dtb  49006101  371808  2  3310-B02-1000--1-0-jetson-tx2-mmcblk0p1  1  0
kernel-dtb  49377909  371808  2  3310-C04-1000--1-0-jetson-tx2-mmcblk0p1  1  0
kernel-dtb  49749717  371808  2  3310-D00-1000--1-0-jetson-tx2-mmcblk0p1  1  1
kernel-dtb  50121525  371808  2  3310-D01-1000--1-0-jetson-tx2-mmcblk0p1  1  0
Saving Entry table to /opt/ota_package/entry_table
Writing 533904 bytes to /dev/disk/by-partlabel/bpmp-fw_b for bpmp-fw
Writing 125568 bytes to /dev/disk/by-partlabel/sce-fw_b for sce-fw
Writing 284688 bytes to /dev/disk/by-partlabel/cpu-bootloader_b for cpu-bootloader
mb2 write: slot = 1 offset = 1276928 bytes = 116832
spe-fw write: slot = 1 offset = 883712 bytes = 95984
Writing 249968 bytes to /dev/disk/by-partlabel/secure-os_b for secure-os
Writing 108208 bytes to /dev/disk/by-partlabel/adsp-fw_b for adsp-fw
dram-ecc-fw write: slot = 1 offset = 0 bytes = 52368
badpage-fw write: slot = 1 offset = 748032 bytes = 4496
Slot could not be opened eks
eks fail to write 
Writing to partitions failed.
OTA Blob update failed. Status: 5
/usr/sbin/nv_bootloader_payload_updater --no-dependent-partition failed.
Slot 1 update failed

Output of .mender image file for the test-distro

Hi Matt,

I'm trying to build the zeus-mender branch of the test-distro and I'm not able to find the .mender image file for the Xavier. The tegra-flash image is built successfully (containing the 2 root images) and also boots properly on the Xavier. Is this a known issue?

Regards,
Boris.

Moving gpu burn to meta tegra

Hi!

I think that the gpu burn can be in meta tegra. What do you think? Is it okay if I send a patch?

mender l4t-r32.4.3 and test-distro

Hi Matt,

Atharva and I have been working on the mender dunfell r32.4.2 port this week with the goal of putting together a base image that supports mender on 32.4.2. I wondered if it would make sense to test it here on test-distro instead of using the repo tool deployment scheme used by other meta-mender-community packages. This might make it easier to demonstrate, deploy, and test support of different branches both here and in meta-tegra. I’ve started a branch at here with work in progress changes for dunfell-l4t-r32.4.2 and I’m wondering if you would be interested in ultimately bringing it in to test-distro as a follow-on to your existing zeus-mender branches.

I’ve noticed the uboot sources from nvidia used on the dunfell-l4t-r32.4.2 branch don’t include fw_printenv/setenv support. For this reason I’ve started by attempting to get jetson-tx2-cboot working on core-image-base. Build succeeds but tegraflash isn't working yet, presumably because there's something wrong with the jetson tx2 cboot conf and the partition setup you've got in test-distro which I don't understand yet.

I needed to make one change to support turning off signing support in order to build locally, see this commit.

Let me know what you think about making test-distro the supported way to test mender updates for new branches going forward and if you have any feedback on what I’ve done so far, which is rebasing everything you had in zeus-mender-l4t-r32.3.1 on test-distro over top of dunfell-l4t-r32.4.2 and putting a few hacks on top to get the build working.

Thanks for your help!

kernel-bup-payload

Hi @madisongh

Where can I find the original kernel-bup-payload recipe referenced in tegra-bup-payload_1.0.bb?

Thanks