rpi3: update OpenOCD configuration for RPi3 #342
Merged
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
|
How about upstreaming to OpenOCD? http://openocd.org/doc-release/doxygen/patchguide.html |
Fixes: OP-TEE#257 Signed-off-by: Joakim Bech <joakim.bech@linaro.org> Tested-by: Joakim Bech <joakim.bech@linaro.org> (RPi3+NFS+JTAG) Acked-by: Jerome Forissier <jerome.forissier@linaro.org>
jbech-linaro
force-pushed
the
rpi3-jtag
branch
from
6227ca6
to
59b7945
Compare
Yes, that was my initial idea with the old cfg that I wrote. But to send this one, I think I need to figure out the email address to the Petr guy and just get his acknowledge (or just add "Suggested-by"). It's on my to-do-list. Squashed, rebased and tag(s) applied (should be) ready for merge! Thanks! |
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.
While doing updates to the upcoming optee_docs / RPi3, I've tested JTAG at the same time and found out that there was indeed an issue with the pi3.cfg file. I found another config that makes it working again and now it seems like having all 4 cores enabled also behaves nicely.
Fixes an old issue also (already closed): #257