Make SPI_Buttons command spispeed more verbose #158
Closed
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
Contributor
Author
|
I just noticed that the baudrate prescaler value macros aren't just simple number representations of their respective names. I've moved this PR into draft mode until I've had time to fix this issue. |
Contributor
Author
|
The command I was trying to use for human readable output is already in use for the Configurator. |
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.
Trying to get an RP2040 to act as a slave over SPI, I went down a rabbit hole of debugging.
Having an easier way to printout the SPI speeds would have helped me quite a bit.
I understand that my use case is quite niche and can totally see why this wouldn't be deemed suitable for upstream.