Draft
Conversation
The documentation in the comments stated that the receive-data offsets started at 6000, but `OFFSET_SHRAM_READ` is defined as `0x1800` (6144 in decimal). This commit updates the comments to reflect the correct offset value.
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
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.
The documentation in the comments stated that the receive-data offsets started at 6000, but
OFFSET_SHRAM_READis defined as0x1800(6144in decimal). This PR updates the comments to reflect the correct offset value.Alternatively, we could change the
#define OFFSET_SHRAM_READto match the comments (6000), if appropriate.