fix: sat/ti: fix symbol timing for TI#233
Open
HongNguyen635 wants to merge 1 commit into
Open
Conversation
For TI, when the stack is light, symbol timing can be quite precise, however, in DMM application where both BLE and SAT are present, symbol timing is off, which causes timing error. The fix is to compute the start time right at the beginning of the packet, and add a constant symbol time offset to it, so that the timing can be more accurate (as accurate as the underlying hardware / scheduler can provide). Signed-off-by: Hong Nguyen <hong@hubble.com>
Collaborator
Author
|
waiting for test results before marking this ready for review |
Collaborator
|
@HongNguyen635 are you still waiting or it should be moved to ready ? |
Collaborator
Author
@hunterhubble just updated these today, I'd say maybe wait over the weekend to see how it goes. I'll check back on Monday. |
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
3 participants
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.
For TI, when the stack is light, symbol timing can be quite precise, however, in DMM application where both BLE and SAT are present, symbol timing is off, which causes timing error.
The fix is to compute the start time right at the beginning of the packet, and add a constant symbol time offset to it, so that the timing can be more accurate (as accurate as the underlying hardware / scheduler can provide).