cpu/gd32v: add periph_dac support#19248
Conversation
ca4e9c0 to
507dff2
Compare
|
bors merge |
17045: sys/coding: add XOR based coding module r=benpicco a=benpicco 19248: cpu/gd32v: add periph_dac support r=benpicco a=gschorcht ### Contribution description This PR provides the `periph_dac` support for GD32VF103. ### Testing procedure `tests/periph_dac` should work on `sipeed-longan-nano` port on PA4 and PA5. ### Issues/PRs references 19251: tests/driver_dac_dds: fix output of sine and saw functions r=benpicco a=benpicco Co-authored-by: Benjamin Valentin <[email protected]> Co-authored-by: Gunar Schorcht <[email protected]>
cpu/gd32v/periph/dac.c
Outdated
| assert(dac_config[line].chan < DAC_CHANNEL_NUMOF); | ||
|
|
||
| /* disable the DAC channel */ | ||
| DAC->CTL |= ~((dac_config[line].chan) ? DAC_CTL_DEN1_Msk : DAC_CTL_DEN0_Msk); |
There was a problem hiding this comment.
I found a small mistake
| DAC->CTL |= ~((dac_config[line].chan) ? DAC_CTL_DEN1_Msk : DAC_CTL_DEN0_Msk); | |
| DAC->CTL &= ~((dac_config[line].chan) ? DAC_CTL_DEN1_Msk : DAC_CTL_DEN0_Msk); |
Is it possible to cancel bors only for this PR or will it cancel the whole train?
There was a problem hiding this comment.
It should do it automatically when you do a push (just squash directly)
|
bors cancel |
|
Canceled. |
507dff2 to
c46382a
Compare
What puzzles me a bit is that it seems to hang reproducibly when a command like The driver itself is quite simple. |
Ah, I found my STM32F4 Discovery board that supports |
BTW, it is quite annoying that this board still uses |
That would be my first guess too. On
ah I guess it's never been updated since we have |
c46382a to
066b921
Compare
|
I had to rebase after the merge of PR #19249 to resolve a conflict in doc. |
|
bors merge |
|
Build succeeded: |

Contribution description
This PR provides the
periph_dacsupport for GD32VF103.Testing procedure
tests/periph_dacshould work onsipeed-longan-nanoport on PA4 and PA5.Issues/PRs references