wch/ch32: Fix WFE#989
Open
Grazfather wants to merge 3 commits into
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
wfein riscv32.zig was using a sort of wch-specific-but-generic-across-wch-family way. #980 sort of pointed this out but did not propose a real fix.This change attempts to add implementations for each of the different qingkevX CPUs. It also adds a
blinky_wfeexample, which is basically the same as blinky_systick, but it enters deep sleep between blinks.Unfortunately I don't have the equipment to test its power draw (under 1mA at 3.3V).
Tested on LANA_TNY and nano_ch32v203, though on the former I don't add the example since there is no on-board LED other than the ws2812.