…oot partition

The UEFI firmware which comes in Jetpack 6 is at
a newer revision and has symlinks support to load the
kernel and dtb from the non-flasher rootfs.

Thus, with an updated bootloader which looks
for the flasher flag in the boot partition,
we can provision the internal medium using the
existing firmware in the QSPI.

Signed-off-by: Alexandru Costache <[email protected]>

Signed-off-by: Alexandru Costache <[email protected]>

In order to run the migrate script succesfully, the tools
used by resin-init-flasher script need to exist in the initramfs.

Signed-off-by: Alexandru Costache <[email protected]>

…available

If the QSPI is not available, like in the case where the standard
uefi firmware is running and the board has not been started in
rcm-boot mode, don't attempt to write the qspi.

Also cleanup unused variable.

Signed-off-by: Alexandru Costache <[email protected]>

We now check for the flasher flag in the boot partition and
boot the device with the flasher root partition set,
without relying on the rcm-boot script to set the kernel
command line.

Signed-off-by: Alexandru Costache <[email protected]>

Signed-off-by: Alexandru Costache <[email protected]>

…ges for QSPI updating

Signed-off-by: Alexandru Costache <[email protected]>

This package provides the means for triggering
UEFI updates if the QSPI is not accessible - that
is when a board has been previously flashed with
the reference OS.

This simplifies the use of flasher images because
the board no longer needs to be put in recovery
mode to be provisioned.

Signed-off-by: Alexandru Costache <[email protected]>

…f QSPI is inaccessible

This allows for flasher images to be booted even if
the device isn't in recovery mode, as long as the
vanilla firmware in the QSPI is in sync with the hostOS
L4T version.

Signed-off-by: Alexandru Costache <[email protected]>

…capsule updates

This package consists of a systemd service and helper scripts
which prepare an UEFI capsule update, when the QSPI
is not already flashed with the UEFI firmware patched
in balenaOS.

Signed-off-by: Alexandru Costache <[email protected]>

… can settle

Signed-off-by: Alexandru Costache <[email protected]>

…rin Flash scripts

So that provisioning doesn't take longer than needed
neither trough USB key, nor during migration in the
initramfs.

We also drop clearing of the eMMC when the NVME is flashed,
and leave the initramfs scripts relocate the end GPT,
since this no longer appears to be needed during provisioning.

Signed-off-by: Alexandru Costache <[email protected]>

... and determine the internal device during HUP, as this
would allow to boot the flasher Orins from multiple targets,
depending on the flasher config.json settings.

Signed-off-by: Alexandru Costache <[email protected]>

…s on accessible QSPIs

... so that the provisioning time is decreased even when
balenaOS was already running on the device.

Signed-off-by: Alexandru Costache <[email protected]>

…ing artifacts

... and also drop the NVME wait script, as increasing the roottimeout
from the kernel cmdline should allow more time for it to settle.

Signed-off-by: Alexandru Costache <[email protected]>

... even if the device was flashed with NewDeviceHierarchy { data = [00]..
so that it can boot a flasher image when a USB key is inserted.

Not setting this would prevent the UEFI bootloader from the
USB key to be loaded by the UEFI firmware. This is done for the
AGX 64GB only, since it's the only flasher DT which has NewDeviceHierarchy
disabled.

NOTE: Setting the flasher rootfs label from extlinux wouldn't
work as an alternative, because the extlinux.conf file
would be loaded from the eMMC as well.

Signed-off-by: Alexandru Costache <[email protected]>

... so that the UEFI capsule update can be triggered based
on the actual device type.

Signed-off-by: Alexandru Costache <[email protected]>

Changelog-entry: layers/meta-balena: Update to v6.1.16
Signed-off-by: Alexandru Costache <[email protected]>

... to ensure that during boot, newly inserted devices like USB
keys or NVMEs are added to the top of the boot list. This allows
for the UEFI bootloader to be loaded from the newly inserted media
so that the flasher image can be booted first.

Changelog-entry: recipes-bsp/tegra-binaries: Update AGX 64 boot blob and UEFI capsule
Signed-off-by: Alexandru Costache <[email protected]>

Signed-off-by: Alexandru Costache <[email protected]>

Signed-off-by: Alexandru Costache <[email protected]>

Signed-off-by: Alexandru Costache <[email protected]>

to allow for builds to run.

Signed-off-by: Alexandru Costache <[email protected]>

We replaced waiting for the NVME to settle with
an increased root timeout.

Signed-off-by: Alexandru Costache <[email protected]>