Add initial changes for Nord RRD board - #3097
Viswanath Kraleti (vkraleti) wants to merge 12 commits into
Conversation
|
Submitted qualcomm-linux/meta-qcom-distro#459 to add Nord boot bins to exception list. |
roshs189
left a comment
There was a problem hiding this comment.
Is the final Licence file LICENSE.qcom-2 or LicenseRef-LICENSE.qcom-2? The zip has LICENSE.qcom-2 file.
0ac3eb9 to
bd28c94
Compare
Dmitry Baryshkov (lumag)
left a comment
There was a problem hiding this comment.
One minor comment
| # tag: nord-staging-qcom-next-7.2-rc3-20260902 | ||
| LINUX_VERSION:nord = "7.1+7.2-rc3-20260902+nord" | ||
| SRCBRANCH:nord = "branch=staging/nord" | ||
| SRCREV:nord = "4ee8d36976563786de92b67e51005f858ed32eb5" |
There was a problem hiding this comment.
When do we expect for this to happen? Will it stay as staging/nord or will we be able to just keep track of qcom-next for it?
There was a problem hiding this comment.
Nord support in qcom-next is expected to be part of 'Linux 7.3-rc2' upgrade. Which is likely to land in a week's time.
There was a problem hiding this comment.
Which is likely to land in a week's time.
It's not, unless the kernel issues are solved.
bd28c94 to
cd9b5e6
Compare
| @@ -288,3 +288,7 @@ FIT_DTB_COMPATIBLE[qcom_qcs6490-iot-subtype2-el2gh-camx-staging] = \ | |||
| # ---------- glymur ---------- | |||
There was a problem hiding this comment.
Nit: "so that the FIT image"
|
cd9b5e6 to
afab3c0
Compare
|
Nord SoC kernel support landed in the 'qcom-next' branch under tag qcom-next-7.3-rc2-20260921, but updating the linux-qcom-next recipe globally to consume this tag causes regressions and test failures on some of the other SoCs, prevents Nord enablement. Add a linux-qcom-next bbappend that overrides LINUX_VERSION and SRCREV for the "nord" SOC_FAMILY only. This allows Nord builds to use the required kernel revision while preserving the existing qcom-next version for all other platforms. This bbappend can be removed once all supported SoCs are validated against a common qcom-next tag. Signed-off-by: Viswanath Kraleti <viswanath.kraleti@oss.qualcomm.com>
Nord SoC (qam8x97p) and its board variant (nord-qam) have no entries in the upstream qcom-dtb-metadata repository. Without them, the kernel FIT image cannot be built with Nord configurations. Add a patch that registers the Nord SoC msm-id (0x288) and qam8x97p variant (0x2b2) in qcom-metadata.dts. This patch should be dropped once the Nord support is merged into the upstream qcom-dtb-metadata repository. Signed-off-by: Viswanath Kraleti <viswanath.kraleti@oss.qualcomm.com>
Nord DTB files specified in FIT_DTB_COMPATIBLE strings only exist in the 'qcom-next' tag used by Nord, not in the default SRCREV that yocto-check-layer builds against. That makes checks fail with error "entries missing DTB/DTBO files in kernel sources". Backport the two board DTS files, still not yet in the default SRCREV, so the default kernel source tree has them too. Drop the backport for Nord itself, since its tag already carries these two commits and re-applying them would cause merge conflicts. Signed-off-by: Viswanath Kraleti <viswanath.kraleti@oss.qualcomm.com>
The Nord platform supports two board types — Ride Embedded (qam8x97p-qam) and RRD(nord-qam). Add entries for both compatibles in fit-dtb-compatible-linux-qcom.inc, mapping them to the coresponding DTB so that he FIT image loader can select the correct DTB at boot. Signed-off-by: Viswanath Kraleti <viswanath.kraleti@oss.qualcomm.com>
Add recipe to deliver boot firmware for Nord RRD board. This enables UEFI compatible boot flow and ensures integration with flat build targets. Signed-off-by: Viswanath Kraleti <viswanath.kraleti@oss.qualcomm.com>
Nord platforms require a board-specific Configuration Data Table (CDT) during early boot to initialize hardware settings such as DDR configuration and RF calibration data. Without the correct CDT, the boot firmware may configure hardware incorrectly, resulting in boot failures or unreliable platform behavior. Add a recipe to fetch and package the CDT artifacts required by Nord platforms. This ensures the appropriate board configuration data is available to the boot chain. Signed-off-by: Viswanath Kraleti <viswanath.kraleti@oss.qualcomm.com>
The Nord SoC is new to meta-qcom and has no entry in packagegroup-machine-essential, so Nord images would miss the SoC-specific kernel modules that other families get through their own -soc packages. Define a new package with known Nord-soc specific kernel modules, following the pattern used by the other qcom-<soc>-soc packages. The exact module list is a placeholder until the real Nord kernel module names are confirmed. Signed-off-by: Viswanath Kraleti <viswanath.kraleti@oss.qualcomm.com>
The linux-firmware version currently used by OE-Core does not include
the WLAN firmware required by Nord. As a result, WiFi is not working
loading fails on Nord platforms.
These firmware files were added upstream after the linux-firmware
release currently consumed by OE-Core. Until OE-Core is updated to a
newer release, backport upstream linux-firmware commit e88807ffbf0f
("ath12k: WCN7850 hw2.0: update board-2.bin") as a KAS patch.
The patch can be removed once OE-Core updates linux-firmware to a
release that includes above commit.
Signed-off-by: Viswanath Kraleti <viswanath.kraleti@oss.qualcomm.com>
Without a board specific packagegroup, there is no structured way to pull firmware into images. Add packagegroup-nord-rrd.bb with the standard borad firmware in the same pattern used by other board packagegroups (e.g. packagegroup-purwa-iot-evk). Signed-off-by: Viswanath Kraleti <viswanath.kraleti@oss.qualcomm.com>
The IQ10 RRD is a new Qualcomm board based on the Nord SoC. Add a machine conf to build Yocto image for this hardware, to kick start software bring-up and validation on this platform. Add conf/machine/include/qcom-nord.inc, following the format used by other SoC families for setting SOC_FAMILY, other required common qcom includes, and selecting the armv8-6a-crypto CPU tune. Add conf/machine/nord-rrd.conf requiring the new qcom-nord.inc, wiring up the board's firmware packagegroups, CDT and boot firmware providers. Signed-off-by: Viswanath Kraleti <viswanath.kraleti@oss.qualcomm.com>
Without a KAS configuration file, developers and CI systems have no standardized way to set up the correct layers, MACHINE and build configuration for Nord RRD. Signed-off-by: Viswanath Kraleti <viswanath.kraleti@oss.qualcomm.com>
The Nord RRD machine configuration is new and not yet covered by CI. Without a build job for this target, regressions can go undetected. As Nord is currently enabled only in the `staging/nord` branch built as part of linux-qcom-next kernel, exclude it from 6.18 kernel variants. Signed-off-by: Viswanath Kraleti <viswanath.kraleti@oss.qualcomm.com>
afab3c0 to
7001928
Compare
|
|
The tarball posted with 0002 tag has only UFS. Expecting another drop with SAIL Zephyr soon. |
|
Will move to draft then until we get the boot firmware with sail, as it is required for the board to boot. |
This PR adds initial bring-up support for the Qualcomm Nord RRD (IQ10 RRD) board.
It provides a machine config and packagegroups following the existing per-SoC-family pattern,
builds the kernel from the
qcom-nextbranch latest tag qcom-next-7.3-rc2-20260921,registers Nord's DTB/FIT metadata, a boot firmware recipe, and backports NSP/HPASS/QUPv3
firmware blobs from linux-firmware.git.
CI gets a KAS config and build workflow coverage for nord-rrd.
The kernel branch override, and the qcom-dtb-metadata patch is temporary and already
submitted upstream. Track for removal once merged.