Add stm32g0b1 support #36
Open
Conversation
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
did you try loading the G071 build on your G0B1 Nucleo? Maybe it is close enough to work? |
|
@azerupi you also need to update the MCU list in bl_update/make_amj.py |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This adds support for the STM32G0B1 which is pretty much equivalent to the G071. This was tested on a Nucleo-G0B1RE and also on some custom hardware.
Since the G071 and G0B1 are so close I feel like there should be a better way than having two distinct Mcu directories. But the G0B1 required an updated CMSIS package and for now I didn't want to touch to the G071.