Fixes for STM32H7 #63
Merged
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
16 tasks
salkinium
force-pushed
the
fix/stm32h7
branch
5 times, most recently
from
f353321
to
2050ef2
Compare
salkinium
force-pushed
the
fix/stm32h7
branch
2 times, most recently
from
fc977f7
to
237354c
Compare
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.
stm32-extendedstm32-extendedstm32-h7@m0,@m4and@m7, but only for some devicesThe
@m4will probably fall over when a device has two cores of the same type, but then again the data in the device file would also be the same? Alternatively@0and@1would be possible, but it's rather confusing.