boards/nucleo-f767zi: Fix13179 make nucleo-f767zi debuggable again [backport 2020.01]#13531
Merged
fjmolinas merged 2 commits intoRIOT-OS:2020.01-branchfrom Mar 5, 2020
Merged
Conversation
This was referenced Mar 2, 2020
Contributor
|
I'll provide the toolchain update backport to fix the build issue. |
Contributor
Author
|
ACK, the build errors seem unrelated |
Contributor
|
@kfessel Yes, but backports have the requirement that it must be rebased on the branch to be merged :/, sorry for all the trouble, do you mind rebasing? That should be the only thing missing |
(cherry picked from commit f00f125)
b30cc41 to
f550fe0
Compare
Contributor
Author
|
done |
Contributor
|
GO! Thanks for getting the proper fix done @kfessel, sorry for all the extra work you had to deal with it! |
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
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.
Backport of #13470
Reverts #13179 which introduced debugging issues due to misinformation of openocd and thereby gdb
Contribution description
Fixes the issue that #13179 tried to address by making the flash probing work on the nucleo-f767zi.
Might generaly improve probing Results due to switching from system reset to system halt after reset.
Testing procedure
The issue #13179 tried fixed:
would fail due to openocd not being able to probe flash while srst is asserted
the issue #13179 generated
lead to gdb telling me:
Issues/PRs references
Fixes #13179 this is the same as #13457 but with the patch for openocd.sh added