Update stm32g0 vendor SVDs from v1.1 to v1.5. #947
Conversation
This file contains 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
Elemecca
force-pushed
the
stm32g0_v1.5
branch
2 times, most recently
from
a0daee9
to
e54edc1
Compare
Elemecca
force-pushed
the
stm32g0_v1.5
branch
from
e54edc1
to
ce7344d
Compare
Elemecca
force-pushed
the
stm32g0_v1.5
branch
from
ce7344d
to
031d2f5
Compare
This was referenced Jan 11, 2024
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.
Updating the vendor SVDs necessitated a lot of changes to the patches, so I ended up simplifying and harmonizing the patch set across all G0 devices.
I have manually reviewed the diffs in the mmaps for the G0 devices, but there are a huge number of changes and it's possible I missed something breaking in the changelog. It'd be great if at least one other person could check those.
Supersedes #730 and #918