Skip to content

shikra-evk: add initial changes for shikra-evk board#2450

Merged
Ricardo Salveti (ricardosalveti) merged 9 commits into
qualcomm-linux:masterfrom
vivpuar:shikra
Jun 30, 2026
Merged

shikra-evk: add initial changes for shikra-evk board#2450
Ricardo Salveti (ricardosalveti) merged 9 commits into
qualcomm-linux:masterfrom
vivpuar:shikra

Conversation

@vivpuar

@vivpuar vivpuar commented Jun 13, 2026

Copy link
Copy Markdown
Contributor

Adding below changes for shikra-evk Board:

  • machine configuration
  • KAS configuration file
  • firmware packagegroup for shikra
  • boot-firmware recipe for shikra

NOTE: This Shikra target PR will be for sample engineering, it won't be of the GA quality as we will have for the other targets.

@lumag Dmitry Baryshkov (lumag) left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

kas-container: Error: configuration file 'ci/shikra-evk.yml' not found

Doesn't build

Comment thread conf/machine/include/qcom-shikra.inc
Comment thread conf/machine/shikra-evk.conf Outdated
Comment thread recipes-bsp/packagegroups/packagegroup-shikra-evk.bb
Comment thread .github/workflows/build-yocto.yml
@ricardosalveti

Copy link
Copy Markdown
Contributor

This recipe fetches and installs the boot firmware and CDT to generate
flat build for Shikra ITP board.

Don't describe what the recipe is doing, but instead explain why the recipe is needed and what it is delivering (e.g. edk2-based firmware at what level of functionality and compatibility with other targets, etc).

Comment thread conf/machine/shikra-evk.conf Outdated
@github-actions

Copy link
Copy Markdown

Test run workflow

Test jobs for commit 0d5a8ab

nodistro
Pass: 9 | Fail: 0 | Total: 9
qcom-distro_linux-qcom-6.18
Pass: 208 | Fail: 0 | Total: 250
qcom-distro
Pass: 9 | Fail: 1 | Total: 10

@lumag Dmitry Baryshkov (lumag) left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

The biggest problem is that there is no signle "shikra-evk" board. There are three different boards, each having a separate model, compats, etc.

Comment thread recipes-bsp/firmware-boot/firmware-qcom-boot-shikra.inc Outdated
Comment thread recipes-bsp/packagegroups/packagegroup-shikra-evk.bb

@lumag Dmitry Baryshkov (lumag) left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

The biggest problem is that there is no signle "shikra-evk" board. There are three different boards, each having a separate model, compats, etc.

@github-actions

Copy link
Copy Markdown

Test run workflow

Test jobs for commit 5a165a5

nodistro
Pass: 9 | Fail: 0 | Total: 9
qcom-distro_linux-qcom-6.18
Pass: 202 | Fail: 0 | Total: 245
qcom-distro
Pass: 243 | Fail: 2 | Total: 292

@test-reporting-app

test-reporting-app Bot commented Jun 15, 2026

Copy link
Copy Markdown

Test Results

  110 files  +   38    657 suites  +288   5h 38m 59s ⏱️ + 58m 22s
  157 tests  -     5    156 ✅ +   16   1 💤  -  2  0 ❌  - 19 
6 252 runs  +2 771  6 200 ✅ +2 781  52 💤 +18  0 ❌  - 28 

Results for commit b4d2916. ± Comparison against base commit e4d25b5.

This pull request removes 5 tests.
0_West[ ‑ Weston_Runtime_Preflight
lava ‑ auto-login-action
lava ‑ lava-test-retry
lava ‑ lava-test-shell
lava ‑ minimal-boot

♻️ This comment has been updated with latest results.

@github-actions

Copy link
Copy Markdown

Test run workflow

Test jobs for commit 5a165a5

nodistro
Pass: 9 | Fail: 0 | Total: 9
qcom-distro_linux-qcom-6.18
Pass: 203 | Fail: 0 | Total: 250
qcom-distro
Pass: 245 | Fail: 1 | Total: 297

@ricardosalveti

Copy link
Copy Markdown
Contributor

A major concern here is that we don't have this board in our lab (lava or axiom/coral), so this can't be tested (and won't be maintained as tested), which is a major concern.

@vkraleti

Viswanath Kraleti (vkraleti) commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

The biggest problem is that there is no signle "shikra-evk" board. There are three different boards, each having a separate model, compats, etc.

Dmitry Baryshkov (@lumag) vivpuar Product team is expecting a single image that can be used on all 3 variants. If hexagon-dsp-binaries recipe produces all 3 packages, qcom-shikra-[cqs|cqm|iqs]-evk-cdsp (they may symlink to each other avoid firmware duplication) and all 3 pkgs are included in the image by default, is it acceptable? Do we still need 3 machine configs?

@vkraleti

Copy link
Copy Markdown
Contributor

A major concern here is that we don't have this board in our lab (lava or axiom/coral), so this can't be tested (and won't be maintained as tested), which is a major concern.

Test team is working on adding Shikra boards to Lava. To speed up the enablement, can it be done in two phases? First phase, build in CI run manual boot test before merging the PRs. Second phase complete Lava test enablement.

@mwasilew

Copy link
Copy Markdown
Contributor

A major concern here is that we don't have this board in our lab (lava or axiom/coral), so this can't be tested (and won't be maintained as tested), which is a major concern.

Test team is working on adding Shikra boards to Lava. To speed up the enablement, can it be done in two phases? First phase, build in CI run manual boot test before merging the PRs. Second phase complete Lava test enablement.

If it was my decision I would say "no". This encourages to cut corners in the future. It would also not be fair to Hamoa team who are waiting for LAVA testing. See #2349

@quaresmajose

Copy link
Copy Markdown
Contributor

The mixin layer already have the shikra backport and I will update the #2542 to include it.

You'd also need 13af9c7

I'll add it, thank you.

@github-actions

Copy link
Copy Markdown

Test run workflow

Test jobs for commit 8884e0d

nodistro
Pass: 10 | Fail: 0 | Total: 10
qcom-distro_linux-qcom-6.18
Pass: 225 | Fail: 1 | Total: 259
qcom-distro
Pass: 274 | Fail: 0 | Total: 301

vivpuar added 9 commits June 29, 2026 15:56
Update SRCREV to pick up V0.8 tag.

Changes since V0.5:

v0.6:
- Update qcom-next-fitimage.its for overlay of monaco-camx-el2.dtbo
- Update qcom-next-fitimage.its for Hamoa EL2 by @LXQUALCOMM
- Update qcom-next-fitimage.its for Lemans and Monaco boards
- Update qcom-next-fitimage.its for Purwa EL2 by @LXQUALCOMM
- Update qcom-next-fitimage.its for Lemans and Monaco upstream camera
  DTB overlay

v0.7:
- scripts: add build-dtb-image.sh, self-contained FIT DTB image builder
  co-located with metadata
- Update bit definition for board-subtype
- qcom-metadata: dts: add Shikra msm-id entries

v0.8:
- Update qcom-next-fitimage.its to add camera overlay for Hamoa EL2
- workflow: add a test workflow to build dtb.bin
- build-dtb-image: optionally prune its based on kernel input
- qcom-next-fitimage.its: Add CamX DTBO support for Hamoa and Purwa EVK
- Add ITP board-id entry in qcom-metadata
- Add Shikra CQM, CQS and IQS variant support

Signed-off-by: Vivek Puar <vpuar@qti.qualcomm.com>
Shikra platform has multiple variants that share same soc but differ
in board subtype. Without their compatible strings, the FIT image loader
cannot match the correct DTB at boot. Add the compatible string
'qcom_shikracqm-itp', 'qcom_shikracqs-itp' and 'qcom_shikraiqs-itp' for
the Shikra DTB to ensure correct DTB matching for the Shikra ITP boards.
Also add compatible strings to include the imx577-camera overlay for the
Shikra ITP boards.

Signed-off-by: Vivek Puar <vpuar@qti.qualcomm.com>
Add recipe to deliver edk2 based boot firmware for Shikra ITP board.
This enables UEFI compatible boot flow and ensures integration with
flat build targets. LIC_FILES_CHKSUM will refer LICENSE.qcom-2.txt
from within the bootbinaries zip instead of fetching a standalone
LICENSE.txt

Signed-off-by: Vivek Puar <vpuar@qti.qualcomm.com>
The Shikra board requires a board-specific Configuration Data Table
(CDT) to correctly initialize hardware parameters such as DDR and RF
calibration data during early boot. Without the CDT, the bootloader
may be unable to correctly  configure the hardware, resulting in boot
failures or incorrect hardware behavior. Add recipe to fetch CDT
required for Shikra ITP Board.

Signed-off-by: Vivek Puar <vpuar@qti.qualcomm.com>
Add firmware and Hexagon DSP packages into image for the Shikra-EVK
boards.

'linux-firmware-qcom-shikra-adreno' package is not provided by oe-core
and 'packagegroup-shikra-evk' depends on the patch that brings the package
which will only be applied if qcom machine is selected. COMPATIBLE_MACHINE
can be dropped once the linux-firmware will upgrade to 202606+

Signed-off-by: Vivek Puar <vpuar@qti.qualcomm.com>
Define a new package with shikra-soc specific kernel modules.

Signed-off-by: Vivek Puar <vpuar@qti.qualcomm.com>
The Shikra EVK is a new Qualcomm development board that has no machine
definition in meta-qcom. Without this, it is not possible to build a
Yocto image targeting Shikra hardware, blocking any software bring-up
or validation work on this platform.

This is an initial bring-up configuration, not all features are
validated to GA quality yet.

Signed-off-by: Vivek Puar <vpuar@qti.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 Shikra-EVK.

Signed-off-by: Vivek Puar <vpuar@qti.qualcomm.com>
The Shikra-EVK machine configuration is new and not yet covered by CI.
Without a build job for this target, regressions in the machine config,
packagegroups or firmware recipes can go undetected until a developer
manually attempts a build.

Signed-off-by: Vivek Puar <vpuar@qti.qualcomm.com>

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Fine with the changes, but please only merge once validated manually by someone, and with the test validation results available in a comment here.

@github-actions

Copy link
Copy Markdown

Test run workflow

Test jobs for commit b4d2916

nodistro
Pass: 10 | Fail: 0 | Total: 10
qcom-distro_linux-qcom-6.18
Pass: 7 | Fail: 1 | Total: 8
qcom-distro
Pass: 272 | Fail: 0 | Total: 300

@github-actions

Copy link
Copy Markdown

Test run workflow

Test jobs for commit b4d2916

nodistro
Pass: 10 | Fail: 0 | Total: 10
qcom-distro_linux-qcom-6.18
Pass: 217 | Fail: 2 | Total: 247
qcom-distro
Pass: 276 | Fail: 0 | Total: 304

@knaveen-qc

Copy link
Copy Markdown

Below are the Test valiation result on this PR Shikra bins for both 6.18 & qcom-next kernel

Test Case IQ-EITP(6.18) CQS(6.18) IQS(qcom-next v7.1-rc7) CQS(qcom-next v7.1-rc7)
ADB push PASS PASS PASS PASS
ADB shell PASS PASS PASS PASS
RPROC modem PASS PASS PASS PASS
RPROC cdsp PASS PASS PASS PASS
RPROC lpaicp PASS PASS PASS PASS
Display FAIL PASS FAIL PASS
DSP Caluclator PASS PASS PASS PASS
BT PASS PASS PASS PASS
Ethernet PASS PASS FAIL (enabled in v7.1) FAIL (enabled in v7.1)
Video encoder/decoder PASS PASS PASS PASS
GPU Off Screen - PASS,               On Screen - FAIL PASS Off Screen - PASS,               On Screen - FAIL PASS
Audio PASS PASS FAIL (enabled in v7.1 PR pending merge) FAIL (enabled in v7.1 PR pending merge)
Adb reboot PASS PASS PASS PASS
Adb reboot bootloader PASS PASS PASS PASS
Adb reboot edl PASS PASS PASS PASS
reboot bootloader PASS PASS PASS PASS
reboot edl PASS PASS PASS PASS
Alpaca Fast boot PASS PASS PASS PASS
Fast boot reboot PASS PASS PASS PASS

@bhargav0610

Bhargav-qcom (bhargav0610) commented Jun 30, 2026

Copy link
Copy Markdown

Test run workflow

Test jobs for commit b4d2916

nodistro
Pass: 10 | Fail: 0 | Total: 10
qcom-distro_linux-qcom-6.18
Pass: 217 | Fail: 2 | Total: 247
qcom-distro
Pass: 276 | Fail: 0 | Total: 304

6.18: qcs6490 bootup crash Kernel panic - not syncing (unrelated PR)
https://lava.infra.foundries.io/scheduler/job/299585

@lumag Dmitry Baryshkov (lumag) left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Display FAIL

What does it mean? Why does it fail?

@ricardosalveti

Copy link
Copy Markdown
Contributor

Yeah, please comment what we will do with the failures, and explain in more details about the failures.

@quic-agnelod

Copy link
Copy Markdown

Display on IQS is not enabled yet, hence the failure. There is an approved exception for this.
Display will be enabled via PRs on top of the ES tag. This will be clearly documented in the bring-up guide.

@github-actions

Copy link
Copy Markdown

Test run workflow

Test jobs for commit b4d2916

nodistro
Pass: 10 | Fail: 0 | Total: 10
qcom-distro_linux-qcom-6.18
Pass: 234 | Fail: 1 | Total: 259
qcom-distro
Pass: 278 | Fail: 0 | Total: 306

@ricardosalveti Ricardo Salveti (ricardosalveti) merged commit 774c978 into qualcomm-linux:master Jun 30, 2026
270 of 271 checks passed
@quic-yocto-ci

Copy link
Copy Markdown
Contributor

Git push to origin failed for wrynose with exitcode 1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.