ETR01SDK-487: Prepare STM32 examples#418
Merged
andreondra merged 36 commits intodevelopfrom Jan 19, 2026
Merged
Conversation
…cmakelists description
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.
Description
This PR adds STM32 examples. Majority of the content is migrated from the libtropic-stm32 repo.
As we discussed, I duplicated not only boilerplate code, but also vendor code. Due to this, the PR is massive even though I tried to significantly reduce vendor stuff. A lot of code repeats and is basically unchanged from the state in libtropic-stm32 or STM32 vendor repos, as such it's mainly important to review main.h/main.c, CMakeLists.txt, CI, docs.
Type of Change
Select the type(s) that best describe your change:
Checklist
Before submitting, please confirm that you have completed the following:
Optional Checks
You can enable optional CI jobs by checking following boxes. For example, coverage job is useful when modifying or implementing new tests.