Hamoa IoT EVK support #1211

shoudil · 2025-11-14T07:03:36Z

To support Homoa IoT EVK board on meta-qcom, includes:

Add machine conf
Consume boot firmware from external release.
Upgrade qcom-ptool to consume partition conf.
Support to create flat build with non-hlos images for spinor.
Pack DTB in UKI as current uefi don't support to load dtb.bin.
Add nvme kernel config to mount rootfs normally.
kas configuration and github CI support.

Depends on:
qualcomm-linux/qcom-ptool#51
qualcomm-linux/qcom-ptool#52

recipes-kernel/linux/linux-qcom-next/configs/qcom.cfg

ci/iq-x7181-evk.yml

conf/machine/include/qcom-x7181.inc

recipes-bsp/firmware-boot/firmware-qcom-boot-x7181.inc

vivpuar · 2025-11-14T07:57:53Z

recipes-bsp/firmware-boot/firmware-qcom-boot-x7181.inc

@@ -0,0 +1,30 @@
+DESCRIPTION = "QCOM NHLOS Firmware for Qualcomm IQ-X7181 platform"
+
+LICENSE = "CLOSED"


Can you add proper LICENSE?

There is no LICENSE file inside external released boot binaries: https://artifacts.codelinaro.org/ui/native/qli-ci/flashable-binaries/ubuntu-fw/X1E80100/IQ-X.1.0-Ver.1.1

This needs to be fixed then. Please reach out to the relevant folks

LICENSE should be part of the boot binaries, and then need to add in the firmware inc file.

Yes, agree. Target team missed this file in Sprint1 release, I will chat with target to add it in Sprint2 release.

Well... We can probably trust Qualcomm engineers... More importantly why is the licence not there in the first place? I assumed that the build / publish / etc. scripts are already written in a way to add it.

Target team took care of the external push for boot binaries, they will add this in coming sprint2 release. Is there any concern to add it in recipe folder like below ?

meta-qcom/recipes-bsp/firmware-boot$ tree -L 2
.
|-- files
| `-- Qualcomm-Technologies-Inc.-Proprietary

Can't we use https://softwarecenter.qualcomm.com/nexus/generic/software/chip/ubuntu_qualcomm_iot-spf-1-0/ubuntu-qualcomm-iot-spf-1-0_test_device_public/r1.0_00001.0/hamoa_iot-ubun-1-0/ instead? We do have a LICENSE and NOTICE there.

Can't we use https://softwarecenter.qualcomm.com/nexus/generic/software/chip/ubuntu_qualcomm_iot-spf-1-0/ubuntu-qualcomm-iot-spf-1-0_test_device_public/r1.0_00001.0/hamoa_iot-ubun-1-0/ instead? We do have a LICENSE and NOTICE there.

I compared the content of LICENSE.txt and the prop license inside boot binaries tar ball, they are different. let me confirm once with target team.

Added license file under local recipe folder and inline corresponding comment in recipe.

ndechesne · 2025-11-14T08:19:54Z

recipes-bsp/firmware-boot/firmware-qcom-boot-x7181.inc

@@ -0,0 +1,30 @@
+DESCRIPTION = "QCOM NHLOS Firmware for Qualcomm IQ-X7181 platform"
+
+LICENSE = "CLOSED"


This needs to be fixed then. Please reach out to the relevant folks

recipes-bsp/firmware-boot/firmware-qcom-boot-iq-x7181.inc

ndechesne · 2025-11-14T08:23:37Z

recipes-bsp/firmware-boot/firmware-qcom-boot-iq-x7181.inc

+
+do_deploy:append() {
+    install -d ${DEPLOYDIR}/${QCOM_BOOT_IMG_SUBDIR}/spinor
+    find "${S}/spinor" -maxdepth 1 -name '*.bin' -exec install -m 0644 {} ${DEPLOYDIR}/${QCOM_BOOT_IMG_SUBDIR}/spinor \;


I don't understand why you need to create the 'spinor' subfolder in DEPLOYDIR

This is to align the directory structure in released boot binaries.
shoudil@shoudil2-gv:/local/mnt/workspace2/shoudil/Hamoa_Yocto_Mainine$ ls -l IQ-X.1.0-Ver.1.1-ubuntu-X1E80100-nhlos-bin*
-rw-r----- 1 shoudil users 17016 Nov 13 20:27 IQ-X.1.0-Ver.1.1-ubuntu-X1E80100-nhlos-bins.tar.gz
-rw-r----- 1 shoudil users 17016 Nov 13 20:27 IQ-X.1.0-Ver.1.1-ubuntu-X1E80100-nhlos-bins.tar.gz.1

IQ-X.1.0-Ver.1.1-ubuntu-X1E80100-nhlos-bins:
total 4
drwxr-xr-x 2 shoudil users 4096 Oct 14 15:27 spinor
shoudil@shoudil2-gv:/local/mnt/workspace2/shoudil/Hamoa_Yocto_Mainine$ tree -L 2 IQ-X.1.0-Ver.1.1-ubuntu-X1E80100-nhlos-bins
IQ-X.1.0-Ver.1.1-ubuntu-X1E80100-nhlos-bins
`-- spinor
|-- adsp_dtbs.elf
|-- adsp_lite.lzma
|-- aop_devcfg.mbn
|-- aop.mbn
|-- cpucp_dtbs.elf

This is to align the directory structure in released boot binaries.

This doesn't really answer the 'why' question.

Updated with "spinor" included in QCOM_BOOT_IMG_SUBDIR.

conf/machine/include/qcom-x7181.inc

classes-recipe/image_types_qcom.bbclass

recipes-kernel/linux/linux-qcom-next/configs/qcom.cfg

ci/iq-x7181-evk.yml

lumag · 2025-11-14T10:41:27Z

To support homa iot evk board on meta-qcom, includes:

hamoa, IoT, EVK (also please fix PR subject)

recipes-bsp/firmware-boot/firmware-qcom-boot-x7181.inc

lumag · 2025-11-14T10:45:28Z

recipes-bsp/firmware-boot/firmware-qcom-boot-x7181.inc

+BOOTBINARIES = "IQ-X.1.0-Ver.${PV}-ubuntu-X1E80100-nhlos-bins"
+
+SRC_URI = " \
+    https://artifacts.codelinaro.org/artifactory/qli-ci/flashable-binaries/ubuntu-fw/X1E80100/IQ-X.1.0-Ver.1.1/IQ-X.1.0-Ver.1.1-ubuntu-X1E80100-nhlos-bins.tar.gz;downloadfilename=X7181_bootbinaries.tar.gz;name=bootbinaries \


What happens with download cache when the next archive gets released?

downloadfilename should have ${PV} as well. And name it with something more aligned with the original tar (to avoid potential naming conflicts with other X7181 targets), or just use hamoa_iot_evk_bootbinaries_${PV}.tar.gz

Also, what is the difference between this boot binary comparing to https://qartifactory-edge.qualcomm.com/artifactory/qsc_releases/software/chip/ubuntu_qualcomm_iot-spf-1-0/ubuntu-qualcomm-iot-spf-1-0_test_device_public/r1.0_00001.0/hamoa_iot-ubun-1-0/HAMOA_bootbinaries.zip ?

from qartifactory we also have a license file: https://qartifactory-edge.qualcomm.com/artifactory/qsc_releases/software/chip/ubuntu_qualcomm_iot-spf-1-0/ubuntu-qualcomm-iot-spf-1-0_test_device_public/r1.0_00001.0/hamoa_iot-ubun-1-0/LICENSE.txt

Only the one in recipe was announced by target team and officially pointed to Canonical as well.

But the one in this recipe has no LICENSE, not even in the top folder, we can't include it here until this is fixed.

recipes-bsp/firmware-boot/firmware-qcom-boot-iq-x7181.inc

lumag · 2025-11-14T10:48:53Z

classes-recipe/image_types_qcom.bbclass

+    if [ -d "${DEPLOY_DIR_IMAGE}/${QCOM_BOOT_FILES_SUBDIR}/spinor" ]; then
+        install -d spinor
+        find "${DEPLOY_DIR_IMAGE}/${QCOM_BOOT_FILES_SUBDIR}/spinor" -maxdepth 1 -type f -exec install -m 0644 {} spinor \;
+        find "${DEPLOY_DIR_IMAGE}/${QCOM_BOOT_FILES_SUBDIR}/spinor" -maxdepth 1 -type f -name 'xbl_s_devprg_ns.melf' -exec install -m 0644 {} . \;


Are we now getting two copies? Also why is it installed outside of spinor?

yes, we have two flat builds. here I installed the programmer outside of spinor, which is used to flash nvme flat build (with efi/rootfs images)

Two copies of xbl_s_devprg_ns.melf. Why does it need special handling?

There is no programmer in nvme flat build at default, so copy it from spinor boot binaries.

Can SPI-NOR programmer program NVMe?

Yes, it worked fine, share the QDL flash logs for your referrence.
shoudil@shoudil2-gv:/local/mnt/workspace2/shoudil/Hamoa_Yocto_Mainine/build/tmp/deploy/images/iq-x7181-evk/core-image-base-iq-x7181-evk.rootfs-20251118034250.qcomflash/spinor$ ./qdl xbl_s_devprg_ns.melf rawprogram0.xml patch0.xml --storage spinor
Waiting for EDL device
waiting for programmer...
flashed "recoveryinfo" successfully
flashed "trial_boot_info" successfully
flashed "XBL_SC" successfully at 193kB/s
flashed "XBL_RAMDUMP" successfully
flashed "XBL_CONFIG" successfully
flashed "UEFI" successfully at 238kB/s
flashed "AOP" successfully
flashed "AOP_CONFIG" successfully
flashed "TZ" successfully at 137kB/s
flashed "DEVCFG" successfully
flashed "HYP" successfully
flashed "QUP" successfully
flashed "TZAPPS" successfully
flashed "MULTIIMGOEM" successfully
flashed "CPUCP" successfully
flashed "CPUCP_DTB" successfully
flashed "SHRM" successfully
flashed "ADSP_UEFI" successfully at 149kB/s
flashed "ADSP_UEFI_DTB" successfully
flashed "ImageFv" successfully
flashed "XBL_SC_BACKUP" successfully at 193kB/s
flashed "XBL_RAMDUMP_BACKUP" successfully
flashed "XBL_CONFIG_BACKUP" successfully
flashed "UEFI_BACKUP" successfully at 247kB/s
flashed "AOP_BACKUP" successfully
flashed "AOP_CONFIG_BACKUP" successfully
flashed "TZ_BACKUP" successfully at 137kB/s
flashed "DEVCFG_BACKUP" successfully
flashed "HYP_BACKUP" successfully
flashed "QUP_BACKUP" successfully
flashed "TZAPPS_BACKUP" successfully
flashed "MULTIIMGOEM_BACKUP" successfully
flashed "CPUCP_BACKUP" successfully
flashed "CPUCP_DTB_BACKUP" successfully
flashed "SHRM_BACKUP" successfully
flashed "ADSP_UEFI_BACKUP" successfully at 149kB/s
flashed "ADSP_UEFI_DTB_BACKUP" successfully
flashed "ImageFv_BACKUP" successfully
flashed "PrimaryGPT" successfully
flashed "BackupGPT" successfully
11 patches applied
shoudil@shoudil2-gv:/local/mnt/workspace2/shoudil/Hamoa_Yocto_Mainine/build/tmp/deploy/images/iq-x7181-evk/core-image-base-iq-x7181-evk.rootfs-20251118034250.qcomflash$ ./qdl xbl_s_devprg_ns.melf rawprogram0.xml patch0.xml --storage nvme
waiting for programmer...
flashed "efi" successfully at 47662kB/s
flashed "rootfs" successfully at 43776kB/s
flashed "PrimaryGPT" successfully
flashed "BackupGPT" successfully
13 patches applied

Please handle those details in the bootbins package

Actually I am not clear how to handle these in bootbins pkgs.
Changes in image_types_qcom.bbclass is to take care of qcom flashable package (flat builds):
=>build/tmp/deploy/images/iq-x7181-evk/qcom-multimedia-image-iq-x7181-evk.rootfs-20251125053933.qcomflash$
while bootbins package take care the non-hlos images under this folder, images in this folder will be provided as input for function in image_type_qcom.bbclass.
=> build/tmp/deploy/images/iq-x7181-evk/iq-x7181/spinor$

Install a copy of the programmer in the boot firmware recipe, not in the common image class.

Install it in boot firmware recipe and consume it to create nvme flat build.
firmware-qcom-boot-iq-x7181.inc:
find "${S}" -maxdepth 1 -type f -name 'xbl_s_devprg_ns.melf' -exec install -m 0644 {} ${DEPLOYDIR}/${QCOM_BOOT_FILES_SUBDIR} ;

image_types_qcom.bbclass:

if [ -e "${DEPLOY_DIR_IMAGE}/${QCOM_BOOT_FILES_SUBDIR}/xbl_s_devprg_ns.melf" ]; then
install -m 0644 "${DEPLOY_DIR_IMAGE}/${QCOM_BOOT_FILES_SUBDIR}/xbl_s_devprg_ns.melf" .
fi

recipes-kernel/linux/linux-qcom-next/configs/qcom.cfg

conf/machine/include/qcom-x7181.inc

lumag · 2025-11-14T10:51:43Z

conf/machine/include/qcom-hamoa.inc

+
+QCOM_VFAT_SECTOR_SIZE = "512"
+
+DEFAULTTUNE = "armv8-2a-crypto"


For this part, I just leverage from IQ-8xx/IQ-9xx, it's not suitable ? if yes, could you share what should be configured here ? Thanks.

It works but it might not be optimized for it, isn't it compatible with armv8.7?

conf/machine/iq-x7181-evk.conf

recipes-bsp/firmware-boot/firmware-qcom-boot-x7181.inc

github-actions · 2025-11-17T13:15:28Z

Test run workflow

Test jobs for commit `4a7dd63`

Job 117071 on dragonboard-410c - boot test (dragonboard-410c) 19430551097
Job 117066 on qcs9100-rb8 - boot test (iq-9075-evk) 19430551097
Job 117065 on qrb2210-rb1 - boot test (qrb2210-rb1-core-kit) 19430551097
Job 117070 on dragonboard-820c - boot test (dragonboard-820c) 19430551097
Job 117063 on qcs8300 - boot test (qcs8300-ride-sx) 19430551097
Job 117064 on qrb2210-rb1 - boot test (qrb2210-rb1-core-kit) 19430551097
Job 117062 on qcs6490 - boot test (qcs6490-rb3gen2-core-kit) 19430551097
Job 117067 on dragonboard-820c - boot test (dragonboard-820c) 19430551097
Job 117069 on qcs9100-rb8 - boot test (iq-9075-evk) 19430551097
Job 117075 on qcs8300 - boot test (qcs8300-ride-sx) 19430551097
Job 117072 on dragonboard-410c - boot test (dragonboard-410c) 19430551097
Job 117073 on qcs6490 - boot test (qcs6490-rb3gen2-core-kit) 19430551097
Job 117068 on qcs9100 - boot test (qcs9100-ride-sx) 19430551097
Job 117074 on qcs9100 - boot test (qcs9100-ride-sx) 19430551097

github-actions · 2025-11-17T13:15:40Z

Test Results

14 files ±0 28 suites ±0 33m 31s ⏱️ + 3m 11s
50 tests ±0 50 ✅ ±0 0 💤 ±0 0 ❌ ±0
304 runs ±0 304 ✅ ±0 0 💤 ±0 0 ❌ ±0

Results for commit 4a7dd63. ± Comparison against base commit 36fd613.

lumag

Also:

2025-11-19 07:07:41 - INFO     - | find: ‘/work/build/tmp/work/all-qcom-linux/firmware-qcom-boot-x7181/1.1/sources/IQ-X7181_bootbinaries/spinor’: No such file or directory

lumag · 2025-11-19T08:43:03Z

recipes-bsp/firmware-boot/firmware-qcom-boot-x7181.inc

@@ -0,0 +1,30 @@
+DESCRIPTION = "QCOM NHLOS Firmware for Qualcomm IQ-X7181 platform"
+
+LICENSE = "CLOSED"


Well... We can probably trust Qualcomm engineers... More importantly why is the licence not there in the first place? I assumed that the build / publish / etc. scripts are already written in a way to add it.

lumag · 2025-11-19T08:44:05Z

recipes-bsp/firmware-boot/firmware-qcom-boot-iq-x7181.inc

+
+do_deploy:append() {
+    install -d ${DEPLOYDIR}/${QCOM_BOOT_IMG_SUBDIR}/spinor
+    find "${S}/spinor" -maxdepth 1 -name '*.bin' -exec install -m 0644 {} ${DEPLOYDIR}/${QCOM_BOOT_IMG_SUBDIR}/spinor \;


This is to align the directory structure in released boot binaries.

This doesn't really answer the 'why' question.

recipes-bsp/firmware-boot/firmware-qcom-boot-iq-x7181.inc

recipes-bsp/firmware-boot/firmware-qcom-boot-iq-x7181_1.1.bb

lumag · 2025-11-19T08:46:13Z

classes-recipe/image_types_qcom.bbclass

    # skip BLANK_GPT and WIPE_PARTITIONS for rawprogram xml files
    for rawpg in `find ${DEPLOY_DIR_IMAGE}/${QCOM_PARTITION_FILES_SUBDIR} -maxdepth 1 -type f -name 'rawprogram*.xml' \
                ! -name 'rawprogram*_BLANK_GPT.xml' ! -name 'rawprogram*_WIPE_PARTITIONS.xml'`; do
        install -m 0644 ${rawpg} .


Meanwhile, copy the programer outside
of spinor folder to be part of NVME flat build.

Why?

NVME flat build include partition bins, hlos images efi.bin, rootfs.img and programmer to support build flash.

That's not an answer for the question. Please add a comment that you are reusing SPI-NOR programmer for NVMe.

Also, maybe it's too platform specific. Should it be done in bootbins?

Still not addressed

This is part of qcom flashable images deployment, should be implemented in create_qcomflash_pkg().

Can't understand your response.

Updated with below (in create_qcomflash_pkg):
if [ -e "${DEPLOY_DIR_IMAGE}/${QCOM_BOOT_FILES_SUBDIR}/xbl_s_devprg_ns.melf" ]; then
install -m 0644 "${DEPLOY_DIR_IMAGE}/${QCOM_BOOT_FILES_SUBDIR}/xbl_s_devprg_ns.melf" .
fi

No, this is still machine-specific. Move that part to the IQ-X7181 boot binaries recipe.

classes-recipe/image_types_qcom.bbclass

lumag · 2025-11-19T08:47:32Z

classes-recipe/image_types_qcom.bbclass

+    if [ -d "${DEPLOY_DIR_IMAGE}/${QCOM_BOOT_FILES_SUBDIR}/spinor" ]; then
+        install -d spinor
+        find "${DEPLOY_DIR_IMAGE}/${QCOM_BOOT_FILES_SUBDIR}/spinor" -maxdepth 1 -type f -exec install -m 0644 {} spinor \;
+        find "${DEPLOY_DIR_IMAGE}/${QCOM_BOOT_FILES_SUBDIR}/spinor" -maxdepth 1 -type f -name 'xbl_s_devprg_ns.melf' -exec install -m 0644 {} . \;


Can SPI-NOR programmer program NVMe?

recipes-kernel/linux/linux-qcom-next/configs/qcom.cfg

lumag · 2025-11-19T08:50:33Z

conf/machine/include/qcom-hamoa.inc

@@ -0,0 +1,18 @@
+# Configurations and variables for IQ-X7181 SoC family.


This is the

There is no action in the commit message (nor imperative language).

conf/machine/include/qcom-x7181.inc

koenkooi · 2025-11-24T10:34:55Z

Please use git rebase instead of git merge, PRs should never contain merge commits.

recipes-kernel/images/esp-qcom-image.bb

lumag

@shoudil I see a lot unresolved ocmments from the previous review cycles. Why were they ignored?

github-actions · 2025-11-24T14:33:20Z

Test run workflow

Test jobs for commit `384bc3b`

Job 119087 on qcs8300 - boot test (qcs8300-ride-sx) 19635516584
Job 119106 on dragonboard-410c - boot test (dragonboard-410c) 19635516584
Job 119093 on qcs9100-rb8 - boot test (iq-9075-evk) 19635516584
Job 119090 on qcs6490 - boot test (qcs6490-rb3gen2-core-kit) 19635516584
Job 119101 on dragonboard-820c - boot test (dragonboard-820c) 19635516584
Job 119097 on qcs9100 - boot test (qcs9100-ride-sx) 19635516584
Job 119085 on qrb2210-rb1 - boot test (qrb2210-rb1-core-kit) 19635516584
Job 119088 on qcs6490 - boot test (qcs6490-rb3gen2-core-kit) 19635516584
Job 119102 on dragonboard-410c - boot test (dragonboard-410c) 19635516584
Job 119086 on qrb2210-rb1 - boot test (qrb2210-rb1-core-kit) 19635516584
Job 119096 on dragonboard-820c - boot test (dragonboard-820c) 19635516584
Job 119094 on dragonboard-410c - boot test (dragonboard-410c) 19635516584
Job 119092 on qcs9100 - boot test (qcs9100-ride-sx) 19635516584
Job 119091 on qcs9100-rb8 - boot test (iq-9075-evk) 19635516584
Job 119107 on dragonboard-410c - boot test (dragonboard-410c) 19635516584
Job 119103 on dragonboard-410c - boot test (dragonboard-410c) 19635516584
Job 119089 on dragonboard-410c - boot test (dragonboard-410c) 19635516584
Job 119098 on qcs8300 - boot test (qcs8300-ride-sx) 19635516584
Job 119095 on dragonboard-820c - boot test (dragonboard-820c) 19635516584

test-reporting-app · 2025-11-24T14:33:32Z

Test Results

14 files ±0 28 suites ±0 35m 48s ⏱️ + 1m 48s
50 tests ±0 50 ✅ ±0 0 💤 ±0 0 ❌ ±0
304 runs ±0 304 ✅ ±0 0 💤 ±0 0 ❌ ±0

Results for commit 384bc3b. ± Comparison against base commit edaaaf0.

shoudil · 2025-11-25T03:22:59Z

Also:

2025-11-19 07:07:41 - INFO     - | find: ‘/work/build/tmp/work/all-qcom-linux/firmware-qcom-boot-x7181/1.1/sources/IQ-X7181_bootbinaries/spinor’: No such file or directory

This issue got resolved in new push.

lumag · 2025-11-25T08:57:24Z

This issue got resolved in new push.

Please resolve all review comments instead of fixing them one by one

lumag · 2025-11-25T09:42:33Z

recipes-bsp/firmware-boot/firmware-qcom-boot-iq-x7181.inc

@@ -0,0 +1,29 @@
+DESCRIPTION = "QCOM NHLOS Firmware for Qualcomm IQ-X7181 platform"
+LICENSE = "CLOSED"


No. Please specify a correct one

No. Please specify a correct one

There is no correct LICENSE in current available bootbins externally, target team will add LICENSE in coming release. if this is block issue for this PR, then we can consider merge after new release available.

I'm not talking about the licence in the archive. Please specify the licence to be used for these binaries.

Updated with license file added under recipe folder.

shoudil · 2025-11-25T09:55:11Z

@shoudil I see a lot unresolved ocmments from the previous review cycles. Why were they ignored?

Several issues need to check on one board, will resolve them ASAP.

ricardosalveti · 2025-11-26T01:30:37Z

classes-recipe/image_types_qcom.bbclass

-    if [ -n "${QCOM_CDT_FILE}" ]; then
+    # check CDT file existence and install as per need, for iq-x7181, CDT file will be part of spinor build, which will
+    # be placed under spinor subfolder.
+    if [ -n "${QCOM_CDT_FILE}" ] && [ -e "${DEPLOY_DIR_IMAGE}/${QCOM_BOOT_FILES_SUBDIR}/${QCOM_CDT_FILE}.bin" ]; then


But why are you copying the CDT to the main folder since it is only really used by spinor?

It should just copy the CDT (provided by the build) to the right destination folder, which could be the main folder itself (e.g. ufs) and inside spinor in your case.

The added condition here is to avoid copy on Hamoa as CDT file not present in this folder, it will report error without this.
"-e ${DEPLOY_DIR_IMAGE}/${QCOM_BOOT_FILES_SUBDIR}/${QCOM_CDT_FILE}.bin"

QCOM_BOOT_IMG_SUBDIR should contain spinor, as raised before, then this would have to be changed if you want avoid copying, or just install CDT to the parent folder (as done by other machines) and then copy it here to the right destination folder, which is under spinor.

The create_qcomflash_pkg function only support one flat build currently, I updated PR using QCOM_BOOT_IMG_SUBDIR (contain spinor) to take care spinor flashable pkg in subfolder, and QCOM_BOOT_FILES_SUDBDIR pointing to the parent folder to take care of nvme flashable images.

This can be handled in a generic code instead of creating extra copies. We know that CDT is either in the root folder or in the spinor/ subfolder.

Use the boot firmware from external release to generate spinor flat build for IQ-X7181 platform, meanwhile specify license file under recipe folder, it will be part of boot binaries tarball in next push. Signed-off-by: Shoudi Li <[email protected]>

Spinor firmware is needed on iq-x7181 based devices, and recently included as part of hamoa sprint one release, deploy them to generate the flat build for spinor flash. Meanwhile, copy the programer outside of spinor folder to be part of NVME flat build. Signed-off-by: Shoudi Li <[email protected]>

Upgrade qcom-ptool to consume partition conf files added for IQ-X7181 platform. Signed-off-by: Shoudi Li <[email protected]>

Enable nvme kernel config to probe nvme driver normally, which help to fix rootfs mount failure. Signed-off-by: Shoudi Li <[email protected]>

Add machine configuration file for IQ-X7181 platform, specify the paths of partition binaries for both NVMe and spinor, where partition bins will be consumed to create flat builds. Signed-off-by: Shoudi Li <[email protected]>

Currently released boot firmware have no capability to load dtb from partition. To address this, pack DTB inside Unified Kernel Image. This ensure proper device tree handling during boot. Signed-off-by: Shoudi Li <[email protected]>

This is the kas config file to support building iq-x7181-evk. Signed-off-by: Shoudi Li <[email protected]>

Update github workflow to build iq-x7181-evk in CI. Signed-off-by: Shoudi Li <[email protected]>

ricardosalveti · 2025-12-01T23:15:27Z

recipes-bsp/firmware-boot/files/license/Qualcomm-Technologies-Inc.-Proprietary

@@ -0,0 +1,3 @@
+Copyright (c) 2023 Qualcomm Technologies, Inc.
+All Rights Reserved.
+Confidential and Proprietary - Qualcomm Technologies, Inc.


This doesn't really add much, I know it is the same content as used by the other boot firmware blobs, but there this file is at least part of the tarball (and it will be updated with the correct license at some point).

This is not enough at all. It doesn't define any terms or conditions. Please use an actual licence.

ricardosalveti · 2025-12-01T23:15:52Z

recipes-bsp/firmware-boot/firmware-qcom-boot-common.inc

 # Install NHLOS boot binaries in DEPLOY_DIR

-S = "${UNPACKDIR}/${BOOTBINARIES}"
+S ?= "${UNPACKDIR}/${BOOTBINARIES}"


Have this as a separated commit.

I don't think it is required at all.

If this is a concern, I will put the "include firmware-qcom-boot-common.inc" before the S= override. otherwise, the change is needed for the override to take effect.
firmware-qcom-boot-iq-x7181.inc:

S = "${UNPACKDIR}/${BOOTBINARIES}/spinor"
...
QCOM_BOOT_IMG_SUBDIR = "iq-x7181/spinor"
include firmware-qcom-boot-common.inc

ricardosalveti · 2025-12-01T23:27:19Z

recipes-bsp/firmware-boot/firmware-qcom-boot-iq-x7181.inc

+    find "${S}" -maxdepth 1 -name '*.lzma' -exec install -m 0644 {} ${DEPLOYDIR}/${QCOM_BOOT_IMG_SUBDIR} \;
+    find "${S}" -maxdepth 1 -name '*.xz' -exec install -m 0644 {} ${DEPLOYDIR}/${QCOM_BOOT_IMG_SUBDIR} \;
+
+    find "${S}" -maxdepth 1 -type f -name 'xbl_s_devprg_ns.melf' -exec install -m 0644 {} ${DEPLOYDIR}/${QCOM_BOOT_FILES_SUBDIR} \;


I believe we can probably add '.lzma', '.xz' and '*.melf' directly in recipes-bsp/firmware-boot/firmware-qcom-boot-common.inc. We just don't want .xml there by default as we prefer to generate those with qcom-ptool.

The scope for QCOM_BOOT_FILES_SUBDIR is at image_types_qcom.bbclass (initially set there), and the local variable is actually QCOM_BOOT_IMG_SUBDIR, but you would have to drop spinor out of it.

I'd rather not do that.

This is totally unnecessary, the melf files are handled in firmware-qcom-boot-common.inc.

In firmware-qcom-boot-common.inc, it will install .melf (include programmer) to spinor subfolder. previous commit I made a copy of programmer in image_types_qcom.bbclass, looks there is still concern. which recipe do you think we need to install a programmer copy to support flash build for nvme ?

The same programer will be needed with spinor, nvme and ufs, right? You could handle that in image_types_qcom (as I said, the scope of QCOM_BOOT_FILES_SUBDIR is already outside this file).

I asked for this change. The sharing of SPINOR programmer for NVMe works for this platform, but I don't want to impose such dependencies in a generic code.

ricardosalveti · 2025-12-01T23:32:31Z

classes-recipe/image_types_qcom.bbclass


-    if [ -n "${QCOM_CDT_FILE}" ]; then
+    # check CDT file existence and install as per need, for iq-x7181, CDT file will be part of spinor build, which will
+    # be placed under spinor subfolder.


Make this comment more generic saying this is due spinor, we will have other spinor devices later.

ricardosalveti · 2025-12-01T23:53:05Z

classes-recipe/image_types_qcom.bbclass

+    # spinor firmware, partition bins, CDT etc.
+    if [ -d "${DEPLOY_DIR_IMAGE}/${QCOM_BOOT_FILES_SUBDIR}/spinor" ]; then
+        install -d spinor
+        find "${DEPLOY_DIR_IMAGE}/${QCOM_BOOT_FILES_SUBDIR}/spinor" -maxdepth 1 -type f -exec install -m 0644 {} spinor \;


You copied over the xml files before, and then you replace them later, you should probably not copy them over in the first place.

ricardosalveti · 2025-12-02T00:20:17Z

INFO: FAIL: test_machine_signatures (bsp.BSPCheckLayer.test_machine_signatures)
INFO: ----------------------------------------------------------------------
INFO: Traceback (most recent call last):
  File "/work/oe-core/scripts/lib/checklayer/cases/bsp.py", line 206, in test_machine_signatures
    self.fail('\n'.join(msg))
    ~~~~~~~~~^^^^^^^^^^^^^^^^
AssertionError: The machines have conflicting signatures for some shared tasks:
   allarch firmware-qcom-boot-iq-x7181:do_deploy: 780b13dbdc88bdd183e7e402896039fc6dea94aca36a7ce80b27dadbbaf1a454 (iq-x7181-evk) != 0716c775c7d2c620c0958e95c90c90b8622e9f62019dc15de7cec47a7e79c5be (qcm6490-idp, qcs6490-rb3gen2-core-kit) != 0aa593b2288e94f78c6cf4794a138a902633bd4519e6f76d05768f297e2c7403 (qcom-armv7a, qcom-armv8a, sm8750-mtp) != 22ae3f0bf7417ecc0e61ebc8f6d8b5074afa0351a6a086ef5fec7fde5e3ea206 (qcs615-adp-air) != 81995b96f1e7c0c4baf7047e963e3e1a2c256b9695d9540c00d30e4b3ab95053 (qcs8300-ride-sx, iq-8275-evk) != 477f1851a614078d82561dba4d6a277ece0f81543a5c4225e31abe7b536f6c8b (qcs9100-ride-sx, iq-9075-evk) != 57996c816b784d9e36a7acc28903014421213408d42ca8ead6e34b8e2d73a711 (qrb2210-rb1-core-kit)

To investigate, run bitbake-diffsigs -t recipename taskname -s fromsig tosig.
Example: (qcs9100-ride-sx, iq-9075-evk) != (qcm6490-idp, qcs6490-rb3gen2-core-kit) in the last line
Command: bitbake-diffsigs -t firmware-qcom-boot-iq-x7181 do_deploy -s 477f1851a614078d82561dba4d6a277ece0f81543a5c4225e31abe7b536f6c8b 0716c775c7d2c620c0958e95c90c90b8622e9f62019dc15de7cec47a7e79c5be
   NOTE: Reconnecting to bitbake server...
   basehash changed from cc309ddbcb1c32001528f9f705bcb8415472152e7b2de65e0e9020dd077377b3 to 3778905feafbe625f284665537130331433fd6ccb329b803f8936acede186196
   Variable QCOM_BOOT_FILES_SUBDIR value changed from 'qcs9100' to 'qcm6490'

lumag · 2025-12-02T00:01:47Z

recipes-bsp/firmware-boot/firmware-qcom-boot-iq-x7181.inc

+DESCRIPTION = "QCOM NHLOS Firmware for Qualcomm IQ-X7181 platform"
+LICENSE = "Proprietary"
+# Speicify the license in recipe folder, it will be part of tarball for hamoa sprint2 release.
+LIC_FILES_CHKSUM = "file://${THISDIR}/files/license/Qualcomm-Technologies-Inc.-Proprietary;md5=58d50a3d36f27f1a1e6089308a49b403"


Nope. It must a be a checksum of the file inside the "source". Checksumming a file outside of the source tree makes zero sense. If you want to checksum something, checksum the library. At least we know that it will change for the next release.

lumag · 2025-12-02T00:01:54Z

recipes-bsp/firmware-boot/firmware-qcom-boot-iq-x7181.inc

@@ -0,0 +1,27 @@
+DESCRIPTION = "QCOM NHLOS Firmware for Qualcomm IQ-X7181 platform"
+LICENSE = "Proprietary"


lumag · 2025-12-02T00:03:01Z

recipes-bsp/firmware-boot/firmware-qcom-boot-iq-x7181.inc

@@ -0,0 +1,27 @@
+DESCRIPTION = "QCOM NHLOS Firmware for Qualcomm IQ-X7181 platform"
+LICENSE = "Proprietary"
+# Speicify the license in recipe folder, it will be part of tarball for hamoa sprint2 release.


What does that mean? I don't know what is sprint2 nor what are the expected release dates. Please think about out-of-context people reading the patch.

lumag · 2025-12-02T00:12:00Z

recipes-bsp/firmware-boot/firmware-qcom-boot-iq-x7181.inc

+
+SRC_URI = " \
+    https://artifacts.codelinaro.org/artifactory/qli-ci/flashable-binaries/ubuntu-fw/X1E80100/IQ-X.1.0-Ver.${PV}/IQ-X.1.0-Ver.${PV}-ubuntu-X1E80100-nhlos-bins.tar.gz;downloadfilename=${BOOTBINARIES}.tar.gz;name=bootbinaries \
+    https://artifacts.codelinaro.org/artifactory/codelinaro-le/Qualcomm_Linux/X1E80100/cdt/IQ-X.1.0-EVK-CDT.tar.gz;downloadfilename=cdt-iq-x7181-evk_${PV}.tar.gz;name=iq-x7181-evk \


name=cdt-iq-x7181-evk.

lumag · 2025-12-02T00:14:08Z

recipes-bsp/firmware-boot/firmware-qcom-boot-iq-x7181.inc

+include firmware-qcom-boot-common.inc
+
+do_deploy:append() {
+    find "${S}" -maxdepth 1 -name '*.xml' -exec install -m 0644 {} ${DEPLOYDIR}/${QCOM_BOOT_IMG_SUBDIR} \;


Nope, no partition files, please.

lumag · 2025-12-02T00:16:12Z

recipes-bsp/firmware-boot/firmware-qcom-boot-iq-x7181.inc

+    find "${S}" -maxdepth 1 -type f -name 'xbl_s_devprg_ns.melf' -exec install -m 0644 {} ${DEPLOYDIR}/${QCOM_BOOT_FILES_SUBDIR} \;
+    find "${UNPACKDIR}" -name '*CDT.bin' -exec install -m 0644 {} ${DEPLOYDIR}/${QCOM_BOOT_IMG_SUBDIR} \;
+}
+


Extra empty line

lumag · 2025-12-02T00:16:36Z

recipes-bsp/firmware-boot/firmware-qcom-boot-iq-x7181.inc

+    find "${S}" -maxdepth 1 -name '*.lzma' -exec install -m 0644 {} ${DEPLOYDIR}/${QCOM_BOOT_IMG_SUBDIR} \;
+    find "${S}" -maxdepth 1 -name '*.xz' -exec install -m 0644 {} ${DEPLOYDIR}/${QCOM_BOOT_IMG_SUBDIR} \;
+
+    find "${S}" -maxdepth 1 -type f -name 'xbl_s_devprg_ns.melf' -exec install -m 0644 {} ${DEPLOYDIR}/${QCOM_BOOT_FILES_SUBDIR} \;


I'd rather not do that.

lumag · 2025-12-02T00:17:37Z

classes-recipe/image_types_qcom.bbclass

    # skip BLANK_GPT and WIPE_PARTITIONS for rawprogram xml files
    for rawpg in `find ${DEPLOY_DIR_IMAGE}/${QCOM_PARTITION_FILES_SUBDIR} -maxdepth 1 -type f -name 'rawprogram*.xml' \
                ! -name 'rawprogram*_BLANK_GPT.xml' ! -name 'rawprogram*_WIPE_PARTITIONS.xml'`; do
        install -m 0644 ${rawpg} .


No, this is still machine-specific. Move that part to the IQ-X7181 boot binaries recipe.

lumag · 2025-12-02T00:18:34Z

classes-recipe/image_types_qcom.bbclass

-    if [ -n "${QCOM_CDT_FILE}" ]; then
+    # check CDT file existence and install as per need, for iq-x7181, CDT file will be part of spinor build, which will
+    # be placed under spinor subfolder.
+    if [ -n "${QCOM_CDT_FILE}" ] && [ -e "${DEPLOY_DIR_IMAGE}/${QCOM_BOOT_FILES_SUBDIR}/${QCOM_CDT_FILE}.bin" ]; then


This can be handled in a generic code instead of creating extra copies. We know that CDT is either in the root folder or in the spinor/ subfolder.

lumag · 2025-12-02T00:20:08Z

recipes-bsp/firmware-boot/firmware-qcom-boot-iq-x7181.inc

+    find "${S}" -maxdepth 1 -name '*.lzma' -exec install -m 0644 {} ${DEPLOYDIR}/${QCOM_BOOT_IMG_SUBDIR} \;
+    find "${S}" -maxdepth 1 -name '*.xz' -exec install -m 0644 {} ${DEPLOYDIR}/${QCOM_BOOT_IMG_SUBDIR} \;
+
+    find "${S}" -maxdepth 1 -type f -name 'xbl_s_devprg_ns.melf' -exec install -m 0644 {} ${DEPLOYDIR}/${QCOM_BOOT_FILES_SUBDIR} \;


This is totally unnecessary, the melf files are handled in firmware-qcom-boot-common.inc.

shoudil requested review from lumag, mwasilew, ndechesne, ricardosalveti, sbanerjee-quic and vkraleti as code owners November 14, 2025 07:03

shoudil force-pushed the hamoa-iot-evk-support branch from 66b8455 to 01aaa27 Compare November 14, 2025 07:22

koenkooi requested changes Nov 14, 2025

View reviewed changes

recipes-kernel/linux/linux-qcom-next/configs/qcom.cfg Show resolved Hide resolved

ci/iq-x7181-evk.yml Show resolved Hide resolved

conf/machine/include/qcom-x7181.inc Outdated Show resolved Hide resolved

recipes-bsp/firmware-boot/firmware-qcom-boot-x7181.inc Outdated Show resolved Hide resolved

vivpuar reviewed Nov 14, 2025

View reviewed changes

shoudil force-pushed the hamoa-iot-evk-support branch from 01aaa27 to 4a7dd63 Compare November 14, 2025 08:39

ndechesne reviewed Nov 14, 2025

View reviewed changes

lumag requested changes Nov 14, 2025

View reviewed changes

ricardosalveti reviewed Nov 14, 2025

View reviewed changes

recipes-bsp/firmware-boot/firmware-qcom-boot-x7181.inc Outdated Show resolved Hide resolved

shoudil changed the title ~~Hamoa iot evk support~~ Hamoa IoT EVK support Nov 17, 2025

shoudil force-pushed the hamoa-iot-evk-support branch from 4a7dd63 to 4432991 Compare November 19, 2025 06:39

lumag requested changes Nov 19, 2025

View reviewed changes

shoudil force-pushed the hamoa-iot-evk-support branch 2 times, most recently from 04acbf1 to 384bc3b Compare November 24, 2025 11:06

lumag reviewed Nov 24, 2025

View reviewed changes

recipes-kernel/images/esp-qcom-image.bb Outdated Show resolved Hide resolved

lumag requested changes Nov 24, 2025

View reviewed changes

lumag reviewed Nov 25, 2025

View reviewed changes

ricardosalveti reviewed Nov 26, 2025

View reviewed changes

shoudil force-pushed the hamoa-iot-evk-support branch from 384bc3b to d9ee3ff Compare November 27, 2025 09:52

shoudil added 7 commits November 27, 2025 18:14

qcom-partition-conf: upgrade qcom-ptool revision

8ace388

Upgrade qcom-ptool to consume partition conf files added for IQ-X7181 platform. Signed-off-by: Shoudi Li <[email protected]>

qcom.cfg: add NVME storage related kernel config

5e15cb6

Enable nvme kernel config to probe nvme driver normally, which help to fix rootfs mount failure. Signed-off-by: Shoudi Li <[email protected]>

conf: machine conf for IQ-X7181 EVK board

00d98a1

Add machine configuration file for IQ-X7181 platform, specify the paths of partition binaries for both NVMe and spinor, where partition bins will be consumed to create flat builds. Signed-off-by: Shoudi Li <[email protected]>

ci: add KAS configuration file for iq-x7181-evk machine

c362e4c

This is the kas config file to support building iq-x7181-evk. Signed-off-by: Shoudi Li <[email protected]>

ci: enable iq-x7181-evk in github CI by default

4c9cebf

Update github workflow to build iq-x7181-evk in CI. Signed-off-by: Shoudi Li <[email protected]>

shoudil force-pushed the hamoa-iot-evk-support branch from d9ee3ff to 4c9cebf Compare November 27, 2025 10:17

ricardosalveti reviewed Dec 1, 2025

View reviewed changes

lumag requested changes Dec 2, 2025

View reviewed changes

		@@ -0,0 +1,30 @@
		DESCRIPTION = "QCOM NHLOS Firmware for Qualcomm IQ-X7181 platform"

		LICENSE = "CLOSED"


		QCOM_VFAT_SECTOR_SIZE = "512"

		DEFAULTTUNE = "armv8-2a-crypto"

		@@ -0,0 +1,18 @@
		# Configurations and variables for IQ-X7181 SoC family.

		@@ -0,0 +1,29 @@
		DESCRIPTION = "QCOM NHLOS Firmware for Qualcomm IQ-X7181 platform"
		LICENSE = "CLOSED"

		@@ -0,0 +1,27 @@
		DESCRIPTION = "QCOM NHLOS Firmware for Qualcomm IQ-X7181 platform"
		LICENSE = "Proprietary"

Hamoa IoT EVK support #1211

Are you sure you want to change the base?

Hamoa IoT EVK support #1211

Uh oh!

Conversation

shoudil commented Nov 14, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

shoudil Nov 19, 2025 • 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!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

shoudil Nov 27, 2025 • 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!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

lumag commented Nov 14, 2025

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

shoudil Nov 18, 2025 • 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!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

shoudil commented Nov 14, 2025 •

edited

Loading

shoudil Nov 19, 2025 •

edited

Loading

shoudil Nov 27, 2025 •

edited

Loading

shoudil Nov 18, 2025 •

edited

Loading

shoudil Nov 25, 2025 •

edited

Loading

shoudil Nov 27, 2025 •

edited

Loading

Test jobs for commit `4a7dd63`