Flush vendor after write #16
Open
Conversation
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
|
Thank you, I'll test if this is the incompatibility! |
|
Just tried this fix and it didn't really do anything. I'm using a T8015, demoting with checkra1n, disconnecting and connecting to the Tamarin cable, and openOCD still refuses to connect with the same error as issue #4. |
|
@tjkr0wn Your issue is unrelated to what this PR is about |
The author of the PR implied JTAG functionality may have been broken because of the tinyUSB change. After ruling out all possible causes for my issue, I assumed this pertained to it and tried it. Would just like to say that my host (ASi) is probably the culprit, as someone else got T8015 to work, so ignore my comments. |
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.
Recent versions of tinyUSB, such as what's currently included in recent versions of pico-sdk, appear to have changed to require flushing after writes. Without this, nothing is (immediately) written in response from the probe, breaking JTAG.
This PR applies a fix similar to what picoprobe applied upstream.
(Is this the USB incompatibility mentioned in the README? With this applied, JTAG and other functionality appears to otherwise work as prior.)