boards/weact-g030f6: add support for minimal break-out board#20337
Merged
benpicco merged 4 commits intoRIOT-OS:masterfrom Feb 5, 2024
Merged
boards/weact-g030f6: add support for minimal break-out board#20337benpicco merged 4 commits intoRIOT-OS:masterfrom
benpicco merged 4 commits intoRIOT-OS:masterfrom
Conversation
maribu
approved these changes
Feb 4, 2024
199e80a to
b254ab6
Compare
b254ab6 to
e207848
Compare
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.
Contribution description
This adds support for a cheap little board based on STM32G030F6.
It is pretty straightforward, except that there is no RTT. This uncovered a bug in
stm32g0316-discowhich I based this on where the board would not setTIMER_0_MAX_VALUEfor the 16 bit timer, leading to way too early timeouts withztimer_msec.Since it's just a single line, I added the fix to this PR.
I also noticed that
periph_rtcwas not supported for this CPU family yet, so I added the required definitions.I also noticed that I sometimes have trouble flashing the device with a DAP-Link Programmer with
I then have to hold the reset button and release it once OpenOCD starts probing the CPU - I have NRST connected, so maybe my debugger is just not using it.
Testing procedure
RTC works with alarm:
I am a bit wondering if the alarm is working on STM32G4 as I would expect that it should select the same code path as STM32G0 (and STM32L5).
With the default the alarm would not get cleared and keep triggering.
Issues/PRs references