Repository navigation
feat(platform): adopt pinned CMSIS Core 6.4 - #35
Merged
Merged
Conversation
Unify all seven maintained MCU families on the reviewed CMSIS Core commit, with private target dependencies and strict current symbols. Keep vendor imports intact and validate real C/C++ Device/Core include closures, Native isolation and explicit staged dependency upgrades. Export the complete Core include tree and notices in the Source SDK; update provider models and the maintained English/Chinese documentation.
Select unchanged GNU-compatible CMSIS declarations only for real Core host models, preserving Arm instruction bodies and C++ linkage. Keep complete mock Core targets independent of the vendor Core dependency.
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
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 and resulting behavior
Unify STM32F103/F407/G474/H743/U575 and GD32F303/F470 on official CMSIS-Core v6.4.0, commit
af1b110e46a1720349f6f125e386e126767699bd. Private CMake targets select the same Core headers for providers, startup and standalone components, and the installed Source SDK exports the complete nested include tree.Requirement: CMSIS6 adaptation across the maintained platform. Accountable roles:
technical-lead,bsp-ports,build-releaseandquality-hil, managed by Codex under.github/maintainer-roles.json.Contract and scope
The official Git tag and Core macros are v6.4.0; the upstream PDSC's
6.4.0-rcentry is recorded separately.Executed validation
f9db4fe383ddc68b82d6933684b6c1d8c5cde380; locally gated8864b3828f4456c4f7134f5c0283752a07ac360e; both have verified treeaaf41e50f7467627fd54663529f6e70175bf2eb88864b382: style, offline documentation/configuration checks, Actions DSL lint, complete-index TDD and Conventional Commit checks passednot_executed; hardware is not connectedExecuted through ordinary
git commit -F .../commit-message.txt, with its unmodified pre-commit configuration. The hook ranpython scripts/ci/tdd_gate.py --stagedand all four tool domains. Current raw results are inbuild/native-debug/tdd/and the local retained attempt under.git/local-recovery/cmsis6-followup-20261026/ordinary-clang-fix-1793024168610997459/.TDD record
PYTHONPATH=tests/contracts python -B -m unittest test_source_sdk.CMSISCoreSelectionTests -vfailed because the export admitted unrelated/missing/nonregular Core payloads.python -B -m unittest tools.configure.test_descriptors.CMSISCoreDescriptorContracts -vfailed because six families selected CMSIS5 and GD470 had no shared Core dependency.payload/dependencies/review.jsonand the corresponding raw files in the frozen evidence archive.Historical development evidence archive SHA256:
dc870b6ca0b4f30af25bdd70c090d36ac0952528830c328f78f067f78f722985. It records original source identities; local records are not claimed to be public CI artifacts. Independent GitHub checks bind this PR head. The first remote Clang run exposed the host ACLE selection boundary; its failed logs are retained. The host bridge and mock-Core isolation regressions were executed RED then GREEN before the complete local gate.The CLI credential expired before synchronization. The connected GitHub API transported the eight already committed files, verified the resulting tree against local commit
8864b382, and advanced the branch with an expected-parent check andforce=false. The remote commit has different author/time metadata; it is not claimed to have executed local commit hooks. The ordinary local commit and its original evidence remain retained.Review and delivery