Fix register corruption due to colliding SPI transactions in FSK #1550
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
thingsconnected
changed the base branch from
master
to
feature/update-samr34-platform
thingsconnected
changed the base branch from
feature/update-samr34-platform
to
master
In FSK Tx, the Dio1 interrupt may already fire while the SPI transaction for SetOpMode is still in progress. This leads to registers 0x02 and further being overwritten with junk data. This is solved by disabling interrupts for this specific SetOpMode call.
thingsconnected
force-pushed
the
pullreq15
branch
from
e1a1a66
to
51f792a
Compare
devilish66694
approved these changes
Jun 25, 2024
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.
Fix register corruption due to colliding SPI transactions in FSK
In FSK Tx, the Dio1 interrupt may already fire while the SPI transaction for SetOpMode is still in progress. This leads to registers 0x02 and further being overwritten with junk data.
This is solved by disabling interrupts for this specific SetOpMode call.
A more detailed discussion is posted on #1551