fix(nightly): cortex-m33 board target mps2/an521 → mps2/an521/cpu0 (4.4.0 dual-cluster)#61
Merged
Merged
Conversation
…4.4.0 dual-cluster)
The nightly `zephyr/cortex-m33 (mps2/an521)` job has been red every run since
the pulseengine/zephyr@gale/sem-replacement branch was rebased to Zephyr v4.4.0.
`west build -b mps2/an521` fails at CMake configure:
CMake Error at .../cmake/modules/boards.cmake:281 (message):
Board qualifiers `an521` for board `mps2` not found.
Root cause: the 4.4.0 fork restructured AN521 into a dual-cluster SoC. The bare
`mps2/an521` target no longer exists; the board files are now
`mps2_an521_cpu0.{dts,yaml}` / `_cpu1.*`, and the twister yaml declares the
canonical identifier as `mps2/an521/cpu0`. cortex-r5 (qemu_cortex_r5, old-style
name) is unaffected — that's why only the M33 leg was red.
Fix: use the valid 4.4.0 target `mps2/an521/cpu0` (secure cpu0 cluster — the
standard kernel-test target). Authoritative source: the fork's
boards/arm/mps2/mps2_an521_cpu0.yaml `identifier:` field, not a guess.
Kill-criterion: nightly m33 leg gets past CMake configure and runs the
semaphore suite (was: FATAL ERROR exit 1 at configure).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The nightly
zephyr/cortex-m33 (mps2/an521)job has been red every run (at least the last 8 nights) and no one had triaged it. Theprecondition_erasurecancel in those runs is just fail-fast fallout from this job.Root cause (measured, not guessed)
west build -b mps2/an521fails at CMake configure:The workspace pulls
pulseengine/zephyr@gale/sem-replacement, which is now rebased to Zephyr v4.4.0 (VERSION: 4.4.0). In that tree, AN521 was restructured into a dual-cluster SoC — the board files are nowmps2_an521_cpu0.{dts,yaml},mps2_an521_cpu1.*, andmps2_an521_cpu0_ns.*, withmps2_an521-common.dtsi. The baremps2/an521target no longer resolves; the canonical identifier (from the fork'sboards/arm/mps2/mps2_an521_cpu0.yaml) is:cortex-r5 (qemu_cortex_r5)uses an old-style board name, so only the M33 leg was affected.Fix
Point the nightly M33 leg at the valid 4.4.0 target
mps2/an521/cpu0(secure cpu0 cluster — the standard kernel-test target). One-line matrix change + the doc comment. Blast radius is justnightly.yml(only file in the repo referencingmps2/an521).Kill-criterion
This is wrong if the next nightly's M33 leg still fails at CMake configure with a board-qualifier error. Expected: it gets past configure and runs the semaphore suite under QEMU.
🤖 Generated with Claude Code