everdrive: Fix 16 byte reading, Add 16 byte writing #14
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 important things
(uint32_t)®S_PTR[REG_USB_DAT] + (512 - len)
is needed when reading or writing to PI with a smaller buffer, because it is techncially the same buffer, just the data is stored closer to the end.Important to note that the buffer retains the data through multiple uses, so you may occasionally need to clear the buffer if the size of what you're putting on it ends up awkward.
I believe the
NOP
actions put the FPGA in a state where it will keep a port connected even though there is no activity. It was required to get the write of "OoTR" to not timeout while writing to the buffer in PI.