SPIButton: RP2040 mode #163
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
Ultrawipf
force-pushed
the
development
branch
from
dd3010c to
cbd64db
Compare
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.
Add an SPI_BtnMode for the RP2040.
Opened in draft as I can't figure out why the OpenFFBoard still boots into TM-mode if RP2040 mode was saved to flash.#160 has been opened if this isn't the place for spitting ideas.
Edit: Turns out that
restoreFlash()runssetConfig()which in turn runsinitSPI(), only for theSPI_Buttonsconstructor to change some of the SPI port values and re-runinitSPI(). 7cbcb08 fixes this behavior, published separately in #164.