Added notes on using the RPi header for GPIO. #375
Merged
Conversation
This file contains 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
Adding a note to explain that the pinmux must be used before attempting to the use the GPIO on the Raspberry Pi's header.
Added a note to pinmux regarding the consequences of the output selection defaulting to 0b10.
|
This caught me out, so I think it may be worth mentioning. |
marnovandermaas
approved these changes
Jan 6, 2025
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.
Added notes to pinmux and GPIO sections of the manual regarding the impact of the pinmux output selector defaulting on 0b10 and the importance of correctly setting the pinmux before attempting to use the RPi header's GPIO pins as outputs.