Reduce wait time in dwReadBytes to boost transfer rate from 160Bps to 487Bps #42
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
In previous implementaion, the DebugWIRE func waited 2ms to for all USB transactions to complete. Now it waits 100us, if there is USB transactions, it waits for another 100us. If there is no USB transactions for 100us, the function will proceeed.
When using SIGTRAP (singal 5), VScode no loger show exception warning, and continue works properly.
|
Now the branch has been both tested in OSX 10.13 and Win7 |
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.
There used to be a 30ms interval between 2 debugWIRE access.
It seems dwReadBytes wait 23ms after receiving the last byte.
So I added a test in dwReadBytes, if the coming byte is not the 1st one, it will only wait for about 1 Byte's time.
At this moment, the interval between 2 debugWIRE access reduced to 6ms.