MSP430 USI SPI Library: pins should be released after SPI.end() #735
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
…om SPI hardware when SPI.end() called.
|
I fully agree that this change should be merged in. |
|
probably also the same issue with USCI, will check |
|
USCI is actually fine as long as you do pinMode() or digitalWrite() to that pins after SPI.end(). Those functions will clear PxSELx registers for SPI pins. |
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.
MOSI, MISO and SCK pins should be released from SPI hardware when SPI.end() called. Otherwise you can not use these pins for something else after spi transmission done.