Repository navigation
Add the vendor SDKs to the hpm and mspm0 images - #2
Merged
Merged
Conversation
Reviewer's GuideThe PR adds versioned HPM and MSPM0 vendor SDKs directly to their Docker images, configures the environment variables required by the BSPs and SysConfig, introduces a dedicated MSPM0 build context, updates publishing to use it, and documents the resulting image capabilities. Sequence diagram for publishing the dedicated MSPM0 imagesequenceDiagram
participant Workflow as Publish workflow
participant Context as mspm0 build context
participant Image as mspm0 image
participant Build as MSPM0 BSP build
Workflow->>Context: docker build
Context->>Image: Install GNU Arm toolchain and starm-clang
Context->>Image: Clone MSPM0 SDK
Context->>Image: Install SysConfig
Workflow->>Image: Publish docker-image-mspm0
Build->>Image: Read MSPM0_SDK_INSTALL_DIR
Build->>Image: Run SYSCONFIG_TOOL
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
This was referenced Oct 5, 2026
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.
The HPM and MSPM0 BSPs build with the vendor SDK outside the repository; with the SDKs in the images, CI and local Docker builds need no SDK download.
hpm: HPM SDK v1.13.0 at/opt/hpm_sdk/v1.13.0,HPM_SDK_BASEset;GNURISCV_TOOLCHAIN_PATHset to the toolchain root.mspm0: own build contextmspm0/(was an alias ofstm32): the stm32 image content plus MSPM0 SDKmspm0_sdk_2_11_00_07(source/and.metadata/only) at/opt/ti/mspm0_sdk_2_11_00_07and SysConfig 1.28.1 at/opt/ti/sysconfig_1.28.1, withMSPM0_SDK_INSTALL_DIRandSYSCONFIG_TOOLset. The publish workflow buildsdocker-image-mspm0from./mspm0.Image size (compressed): hpm 1.43 -> 1.63 GB, mspm0 0.99 -> 1.33 GB (SysConfig is most of it).
Verified locally: with nothing but the source mounted, bsp-hpm5301evklite (
debug-flash-xip, against SDK v1.13.0) and bsp-mspm0g3507-mini (debug, SysConfig run by CMake) build in the new images;sysconfig_cli.sh --versionprints 1.28.1+4785.Note:
mspm0/Dockerfilerepeats the stm32 Dockerfile, so changes to the shared part have to be made in both.Summary by Sourcery
Bundle the HPM and MSPM0 vendor SDKs and build tools into their Docker images so BSP builds no longer require external SDK downloads.
New Features:
Enhancements:
CI: