Add partition configurations for Nord RRD by vkraleti · Pull Request #168 · qualcomm-linux/qcom-ptool

Viswanath Kraleti (vkraleti) · 2026-09-02T17:15:31Z

Adds the partition configurations and contents.xml.in for the Nord RRD board
to support downstream boot flow using QTEE, UEFI and systemd-boot and
open boot flow using TF-A, OP-TEE and U-Boot.

Additional files device_programmer_ddr.elf, oem_misc.mbn, qti_misc.mbn, soccp.mbn and xbl_ramdump.elf are used by Nord RRD. Add them to check-missing-files. Signed-off-by: Viswanath Kraleti <viswanath.kraleti@oss.qualcomm.com>

Add initial partition.conf and contents.xml.in for Nord RRD board to support the boot firmware stack using QTEE, UEFI and systemd-boot. Signed-off-by: Viswanath Kraleti <viswanath.kraleti@oss.qualcomm.com>

Ricardo Salveti (ricardosalveti) · 2026-09-02T18:41:39Z

Can't we try to have a single partitioning scheme that would work for both boot firmware deployments?

Viswanath Kraleti (vkraleti) · 2026-09-02T18:53:57Z

Can't we try to have a single partitioning scheme that would work for both boot firmware deployments?

For open boot flow, bootloader team is proposing to use more generic uboot_spl, boot_fit, ubootenv partitions in place of uefi and tz. Gopinath Sekar (@g-sekar) aswinm94 anushka-qcom can provide more details on this.

Ricardo Salveti (ricardosalveti) · 2026-09-02T18:59:28Z

We have open boot firmware with lemans and we didn't really need a custom partition layout for it, the only partition that is not there is the one for ubootenv, but that is current being discussed at qualcomm-linux/meta-qcom#2808.

Gopinath Sekar (g-sekar) · 2026-09-03T10:54:43Z

In Lemans we have reused
TZ partition for U-Boot SPL.
UEFI partition was used for FIT image (TF-A+OPTEE+U-Boot).
Since we have oppurtunity to define the partition table in Nord we wanted to name them in proper way.

Dmitry Baryshkov (lumag) · 2026-09-07T09:23:23Z

+--partition --lun=4 --name=aop_a --size=1024KB --type-guid=D69E90A5-4CAB-0071-F6DF-AB977F141A7F --filename=aop.mbn
+--partition --lun=4 --name=aop_config_a --size=512KB --type-guid=3D12F234-C882-4B46-A20C-17D52C8FC03D --filename=aop_devcfg.mbn
+--partition --lun=4 --name=apdp_a --size=64KB --type-guid=E6E98DA2-E22A-4D12-AB33-169E7DEAA507 --filename=zeros_1sector.bin
+--partition --lun=4 --name=core_nhlos_a --size=122880KB --type-guid=6690B4CE-70E9-4817-B9F1-25D64D888357


What is core_nhlos?

core_nhlos, along with the quantumfv, quantumsdk, and quantumcontentfv partitions, is part of the Quantum UEFI-stage PIL loading framework, used to load and validate subsystems independent of HLOS.

Why are they being left empty?

By default PIL are loaded by HLOS, these partitions exist to accommodate the special asks to support UEFI-stage PIL loading.

Dmitry Baryshkov (lumag) · 2026-09-07T09:24:27Z

+--partition --lun=4 --name=xbl_ramdump_b --size=2048KB --type-guid=FF608BF6-AEDF-4084-BEC5-C92AB4E4534D --filename=xbl_ramdump.elf
+
+#These are non A/B partitions. In a A/B build these would not be updated via a OTA update
+--partition --lun=4 --name=cateloader --size=2048KB --type-guid=AA9A5C4C-4F1F-7D3A-014A-22BD33BF7191


What is it?

This contains the UEFI TZT CATE (Common Automation & Test Environment) loader primarily used for TrustZone test automation.

If it's for the test automation, why does it take space on all production devices?

Internal test automations are also reusing the same partition.xml produced by qcom-ptool. Should this be maintained separately?

Dmitry Baryshkov (lumag) · 2026-09-07T09:25:48Z

In Lemans we have reused TZ partition for U-Boot SPL. UEFI partition was used for FIT image (TF-A+OPTEE+U-Boot). Since we have oppurtunity to define the partition table in Nord we wanted to name them in proper way.

Proper way = compatible with the earlier platforms, unless you are required to break functionality.

Gopinath Sekar (g-sekar) · 2026-09-08T09:56:17Z

Proper way = compatible with the earlier platforms, unless you are required to break functionality.

Legacy platforms followed the XBL → QTEE → EDK2 boot flow, whereas the current implementation adopts the open-source boot architecture of SPL → TF-A → OP-TEE → EDK2/U-Boot.

From a customer or ecosystem perspective, requiring users to flash SPL into the TZ partition does not seem logical. The partition layout should be defined based on the requirements of the open boot flow.

If there are differences between the open boot implementations on NORD and other chipsets, that is a valid topic for discussion. However, it is unclear why we need to preserve compatibility between the legacy boot flow and the new open boot flow when the partitioning scheme has already been redesigned to support the open-source architecture.

Dmitry Baryshkov (lumag) · 2026-09-08T15:05:28Z

Are we going to support QTEE in addition to TF-A/OP-TEE?

Viswanath Kraleti (vkraleti) · 2026-09-08T15:51:41Z

Are we going to support QTEE in addition to TF-A/OP-TEE?

Yes, Nord is expected to support three boot flows.

U-Boot SPL → TF-A → OP-TEE → U-Boot
U-Boot SPL → TF-A → OP-TEE → upstream EDK2
XBL → QTEE → downstream EDK2(UEFI)

Proposal is to use one partitioning scheme for 1 & 2 boot flows. And a different one for 3.

Ricardo Salveti (ricardosalveti) · 2026-09-08T15:59:15Z

I still would like for us to come up with one single partition scheme here, that could cover the 3 scenarios. As I said, we are already handling this for lemans and other targets with one single partition table.

Viswanath Kraleti (vkraleti) · 2026-09-09T00:59:09Z

Dmitry Baryshkov (@lumag) Ricardo Salveti (@ricardosalveti) as #132 is bringing in open boot partitions, is it fine if I limit this PR only to downstream boot flow? This will help to kick start CI.

SShirishQ · 2026-09-09T05:09:02Z

Viswanath Kraleti (@vkraleti) lets not mix proprietary & open boot related requirement discussions, pls split this PR accordingly as discussed yesterday.

Sumit Garg (b49020) · 2026-09-09T05:48:15Z

Dmitry Baryshkov (Dmitry Baryshkov (@lumag)) Ricardo Salveti (Ricardo Salveti (@ricardosalveti)) as #132 is bringing in open boot partitions, is it fine if I limit this PR only to downstream boot flow? This will help to kick start CI.

#132 is meant to address downstream boot flow as well. Please feel free to test it and comment if we are missing something there.

Viswanath Kraleti (vkraleti) · 2026-09-09T08:56:22Z

Viswanath Kraleti (Viswanath Kraleti (@vkraleti)) lets not mix proprietary & open boot related requirement discussions, pls split this PR accordingly as discussed yesterday.

Dropped the commit that is bringing in open boot flow partitions.

Viswanath Kraleti (vkraleti) requested review from Dmitry Baryshkov (lumag) and Nicolas Dechesne (ndechesne) as code owners September 2, 2026 17:15

check-missing-files: add additional files used by Nord RRD

fd5a8f5

Additional files device_programmer_ddr.elf, oem_misc.mbn, qti_misc.mbn, soccp.mbn and xbl_ramdump.elf are used by Nord RRD. Add them to check-missing-files. Signed-off-by: Viswanath Kraleti <viswanath.kraleti@oss.qualcomm.com>

Viswanath Kraleti (vkraleti) force-pushed the nord-support branch from 78a87ea to 7beb683 Compare September 2, 2026 17:54

platforms: add partitioning scheme for nord-rrd

d53b097

Add initial partition.conf and contents.xml.in for Nord RRD board to support the boot firmware stack using QTEE, UEFI and systemd-boot. Signed-off-by: Viswanath Kraleti <viswanath.kraleti@oss.qualcomm.com>

Viswanath Kraleti (vkraleti) force-pushed the nord-support branch from 7beb683 to 758ca62 Compare September 2, 2026 18:31

Dmitry Baryshkov (lumag) reviewed Sep 7, 2026

View reviewed changes

Viswanath Kraleti (vkraleti) force-pushed the nord-support branch from 758ca62 to d53b097 Compare September 9, 2026 08:52

Uh oh!

Conversation

Viswanath Kraleti (vkraleti) commented Sep 2, 2026

Uh oh!

Ricardo Salveti (ricardosalveti) commented Sep 2, 2026

Uh oh!

Viswanath Kraleti (vkraleti) commented Sep 2, 2026

Uh oh!

Ricardo Salveti (ricardosalveti) commented Sep 2, 2026

Uh oh!

Gopinath Sekar (g-sekar) commented Sep 3, 2026

Uh oh!

Dmitry Baryshkov (lumag) Sep 7, 2026

Choose a reason for hiding this comment

Uh oh!

Viswanath Kraleti (vkraleti) Sep 7, 2026

Choose a reason for hiding this comment

Uh oh!

Dmitry Baryshkov (lumag) Sep 8, 2026

Choose a reason for hiding this comment

Uh oh!

Viswanath Kraleti (vkraleti) Sep 9, 2026

Choose a reason for hiding this comment

Uh oh!

Dmitry Baryshkov (lumag) Sep 7, 2026

Choose a reason for hiding this comment

Uh oh!

Viswanath Kraleti (vkraleti) Sep 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Dmitry Baryshkov (lumag) Sep 8, 2026

Choose a reason for hiding this comment

Uh oh!

Viswanath Kraleti (vkraleti) Sep 9, 2026

Choose a reason for hiding this comment

Uh oh!

Dmitry Baryshkov (lumag) commented Sep 7, 2026

Uh oh!

Gopinath Sekar (g-sekar) commented Sep 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Dmitry Baryshkov (lumag) commented Sep 8, 2026

Uh oh!

Viswanath Kraleti (vkraleti) commented Sep 8, 2026

Uh oh!

Ricardo Salveti (ricardosalveti) commented Sep 8, 2026

Uh oh!

Viswanath Kraleti (vkraleti) commented Sep 9, 2026

Uh oh!

SShirishQ commented Sep 9, 2026

Uh oh!

Sumit Garg (b49020) commented Sep 9, 2026

Uh oh!

Viswanath Kraleti (vkraleti) commented Sep 9, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

Viswanath Kraleti (vkraleti) Sep 8, 2026 •

edited

Loading

Gopinath Sekar (g-sekar) commented Sep 8, 2026 •

edited

Loading