Skip to content

firmware-qcom-boot: update to 00095.0#886

Merged
lumag merged 3 commits intoqualcomm-linux:masterfrom
vkraleti:bootbins_85
Jul 2, 2025
Merged

firmware-qcom-boot: update to 00095.0#886
lumag merged 3 commits intoqualcomm-linux:masterfrom
vkraleti:bootbins_85

Conversation

@vkraleti
Copy link
Copy Markdown
Contributor

@vkraleti vkraleti commented May 14, 2025

A new firmware drop 00095.0 is available. Migrate to it for qcs6490, qcs9100, qcs8300 based machines.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 14, 2025

Test Results

  6 files  ±0   12 suites  ±0   11m 37s ⏱️ ±0s
 45 tests ±0   45 ✅ ±0  0 💤 ±0  0 ❌ ±0 
132 runs  ±0  132 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit a77a3b8. ± Comparison against base commit a91a98a.

♻️ This comment has been updated with latest results.

@github-actions
Copy link
Copy Markdown

Test jobs for commit cf9a8972096d0fd8732ba0e80bae5f85e9455328

@ricardosalveti
Copy link
Copy Markdown
Contributor

@vkraleti what are the other changes done as part of this update besides having contents.xml?

At least on QCM6490_bootbinaries:

-c298d6072c62aea5f954f2e19a57700288addecd37c2839bde04ddc2ddc2ef53  multi_image.mbn
+826daa66daa1551e6f14171f9c87b629cdf63138f1edfdc15e611cbaa9ba3325  multi_image.mbn

I also don't like having contents.xml provided by the boot firmware recipe, as in the end it has no direct relation to it (not used by the boot stack at all). Maybe better to have a separated recipe to provide such file (and have it as part of meta-axiom or similar, as discussed at #849).

@koenkooi
Copy link
Copy Markdown
Contributor

@vkraleti what are the other changes done as part of this update besides having contents.xml?

At least on QCM6490_bootbinaries:


-c298d6072c62aea5f954f2e19a57700288addecd37c2839bde04ddc2ddc2ef53  multi_image.mbn

+826daa66daa1551e6f14171f9c87b629cdf63138f1edfdc15e611cbaa9ba3325  multi_image.mbn

I also don't like having contents.xml provided by the boot firmware recipe, as in the end it has no direct relation to it (not used by the boot stack at all). Maybe better to have a separated recipe to provide such file (and have it as part of meta-axiom or similar, as discussed at #849).

Can we generate it ourselves during the build?

@vkraleti
Copy link
Copy Markdown
Contributor Author

@vkraleti what are the other changes done as part of this update besides having contents.xml?
At least on QCM6490_bootbinaries:


-c298d6072c62aea5f954f2e19a57700288addecd37c2839bde04ddc2ddc2ef53  multi_image.mbn

+826daa66daa1551e6f14171f9c87b629cdf63138f1edfdc15e611cbaa9ba3325  multi_image.mbn

I also don't like having contents.xml provided by the boot firmware recipe, as in the end it has no direct relation to it (not used by the boot stack at all). Maybe better to have a separated recipe to provide such file (and have it as part of meta-axiom or similar, as discussed at #849).

Can we generate it ourselves during the build?

`contents.xml' file is not generated by any tool. During release, it is manually written by the integration team based on the partition layout and corresponding image locations.

@lumag
Copy link
Copy Markdown
Contributor

lumag commented May 15, 2025

@vkraleti what are the other changes done as part of this update besides having contents.xml?
At least on QCM6490_bootbinaries:


-c298d6072c62aea5f954f2e19a57700288addecd37c2839bde04ddc2ddc2ef53  multi_image.mbn

+826daa66daa1551e6f14171f9c87b629cdf63138f1edfdc15e611cbaa9ba3325  multi_image.mbn

I also don't like having contents.xml provided by the boot firmware recipe, as in the end it has no direct relation to it (not used by the boot stack at all). Maybe better to have a separated recipe to provide such file (and have it as part of meta-axiom or similar, as discussed at #849).

Can we generate it ourselves during the build?

`contents.xml' file is not generated by any tool. During release, it is manually written by the integration team based on the partition layout and corresponding image locations.

This is error-prone. We handle partition layout on our own, inside meta-qcom.

@vkraleti
Copy link
Copy Markdown
Contributor Author

@vkraleti what are the other changes done as part of this update besides having contents.xml?

At least on QCM6490_bootbinaries:

-c298d6072c62aea5f954f2e19a57700288addecd37c2839bde04ddc2ddc2ef53  multi_image.mbn
+826daa66daa1551e6f14171f9c87b629cdf63138f1edfdc15e611cbaa9ba3325  multi_image.mbn

I also don't like having contents.xml provided by the boot firmware recipe, as in the end it has no direct relation to it (not used by the boot stack at all). Maybe better to have a separated recipe to provide such file (and have it as part of meta-axiom or similar, as discussed at #849).

Apart from contents.xml addition, there is no difference between this and the 00075 release for both QCS9100 and QCS8300.
For QCM6490, there is a bug fix in ADSP for PMIC less support along with contents.xml addition. I'll update commit message accordingly.

@ricardosalveti
Copy link
Copy Markdown
Contributor

`contents.xml' file is not generated by any tool. During release, it is manually written by the integration team based on the partition layout and corresponding image locations.

We can easily migrate to a different recipe then, and later find a way to automatically match with the partition layout that is generated by the build.

@lumag
Copy link
Copy Markdown
Contributor

lumag commented May 15, 2025

For QCM6490, there is a bug fix in ADSP for PMIC less support

Do we have more info? Does it affect our platforms or not?

Copy link
Copy Markdown
Contributor

@lumag lumag left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This needs to be rebased in order to resolve conflicts

@vkraleti
Copy link
Copy Markdown
Contributor Author

This needs to be rebased in order to resolve conflicts

Anticipating a new firmware drop in a day or two. Will rebase along with upgrade.

@vkraleti vkraleti changed the title firmware-qcom-boot: update to 00085.0 for contents.xml. firmware-qcom-boot: update to 00090.0 Jun 16, 2025
Copy link
Copy Markdown
Contributor

@lumag lumag left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • Missing commit messages
  • Missing changelog / notes, why do we want to upgrade the firmware
  • PR description also needs to be updated.

@vkraleti vkraleti marked this pull request as draft June 16, 2025 11:53
@vkraleti
Copy link
Copy Markdown
Contributor Author

Waiting for release notes to update commit msgs. Moved the PR to draft for now.

@github-actions
Copy link
Copy Markdown

@vkraleti vkraleti changed the title firmware-qcom-boot: update to 00090.0 firmware-qcom-boot: update to 00095.0 Jul 1, 2025
@vkraleti vkraleti marked this pull request as ready for review July 1, 2025 18:06
Comment thread recipes-bsp/firmware-boot/firmware-qcom-boot-qcs6490_00095.0.bb Outdated
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Jul 1, 2025

vkraleti added 3 commits July 2, 2025 16:23
Use firmware available as part of the Qualcomm Linux 1.5 release.

Known changes:
    - Support boot from eMMC
    - XBL support for KVM usage
    - Support SD card as secondary storage
    - Minor bug fixes

Signed-off-by: Viswanath Kraleti <viswanath.kraleti@oss.qualcomm.com>
Use firmware available as part of the Qualcomm Linux 1.5 release.

Known changes:
    - Peripheral interfaces support on SAIL domain
    - Support boot from eMMC
    - XBL support for KVM usage
    - Minor bug fixes

Signed-off-by: Viswanath Kraleti <viswanath.kraleti@oss.qualcomm.com>
Use firmware available as part of the Qualcomm Linux 1.5 release.

Known changes:
    - Free RTOS enablement on SAIL domain
    - Boot from eMMC support
    - XBL support for KVM usage
    - Minor bug fixes

Signed-off-by: Viswanath Kraleti <viswanath.kraleti@oss.qualcomm.com>
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Jul 2, 2025

@ricardosalveti
Copy link
Copy Markdown
Contributor

@mwasilew lemans failure is due a download timeout https://lava.infra.foundries.io/scheduler/job/81963

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Jul 2, 2025

Copy link
Copy Markdown
Contributor

@lumag lumag left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • XBL support for KVM usage

So, can we use KVM now from a normal Linux system? Or do we need to perform any extra steps?

  • Support SD card as secondary storage

What does that mean in the contents of the bootloaders?

@vkraleti
Copy link
Copy Markdown
Contributor Author

vkraleti commented Jul 2, 2025

  • XBL support for KVM usage

So, can we use KVM now from a normal Linux system? Or do we need to perform any extra steps?

To use KVM, users need to flash "xml_config_kvm.elf" available in the same bootbins tar. GA 1.5 documentation has details about switching to KVM.

  • Support SD card as secondary storage

What does that mean in the contents of the bootloaders?

The same bootloader image supports this functionality. If the UFS storage becomes corrupted and a valid bootable media is present in the SD card slot, UEFI can detect it and automatically boot from the SD card.

@lumag lumag merged commit 0c47db4 into qualcomm-linux:master Jul 2, 2025
27 checks passed
@vkraleti vkraleti deleted the bootbins_85 branch July 3, 2025 07:01
basak-qcom added a commit to basak-qcom/qcom-deb-images that referenced this pull request Jul 24, 2025
This is similar to qualcomm-linux/meta-qcom#886 and should bring at
least one bug fix for QCM6490 (RB3Gen2).

Fixes: qualcomm-linux#106
basak-qcom added a commit to basak-qcom/qcom-deb-images that referenced this pull request Jul 24, 2025
This is similar to qualcomm-linux/meta-qcom#886 and should bring at
least one bug fix for QCM6490 (RB3Gen2).

Fixes: qualcomm-linux#106
Signed-off-by: Robie Basak <robibasa@qti.qualcomm.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants