Tags

Prepare v2025.04-rc5

qcom-next-20230324

take 2

Qualcomm patches for U-Boot next 2025-03-17

Prepare v2025.04-rc4

Prepare v2025.04-rc3

Prepare v2025.04-rc2

Prepare v2025.04-rc1

Prepare v2025.01

Prepare v2025.01-rc6

Prepare v2025.01-rc5

Prepare v2025.01-rc4

Two fixes for the EFI subsystem coming via the TPM tree as agreed by Heinrich

The LMB patch fixes a failure in SystemReady testing. Nothing bad happens
without the patch in the device operation, but the return values are wrong
and SCT tests fail for MemoryAllocationServicesTest category.

The second is a shielding the device against mistakes in the definition of
struct fields needed by the capsule update mechanism. Instead of crashing,
print a humna readable message of what's wrong.

Prepare v2025.01-rc3

RB3 Gen 2 LAA build 1

Download the U-Boot build attached.

## Flashing:

Install EDL tool by following the guide in the README:
https://github.com/bkerler/edl/blob/master/README.md

Download and unzip the bootloader firmware from
https://artifacts.codelinaro.org/artifactory/qli-ci/software/chip/qualcomm_linux-spf-1-0/qualcomm-linux-spf-1-0_test_device_public/r1.0_00039.2/QCM6490.LE.1.0/common/build/ufs/bin/QCM6490_bootbinaries.zip

Note the path to the prog_firehose_ddr.elf file.

Enter EDL mode by powering up the board while holding the EDL button
(it's on the bottom of the PCB next to side with the micro-usb ports).
It should appear as qcserial in dmesg on a Linux host.

Now flash with

edl.py --loader /path/to/prog_firehose_ddr.elf w uefi_a u-boot-rb3gen.mbn

## Usage

Only the type-c port is functional, a *powered* USB hub must be used
with a USB 2.0 drive OR USB 2.0 port on the hub.

U-Boot will automatically boot from a USB drive that has an EFI system
partition on it.

If attaching the drive after booting the board, run

=> usb reset
...

Boot with

=> bootefi bootmgr

Two changes from Heinrich.
One is adding some missing TPM files for proper maintenance.
The second addresses Coverity-ID: 356664 replacing a mempcy()
which has undefined behavior with memmove()

Prepare v2025.01-rc2

Prepare v2025.01-rc1

Prepare v2024.10

Prepare v2024.10-rc6

This PR contains various improvements in the A/B update logic for EFI

- Read both copies of metadata, in case one of the is corrupted
- Check the metadata version against the running firmware to make sure it's
  allowed
- Limit the use of a revert capsule if the board is on a trial state and
  make sure it's not applied if the max counter has expired