Breakpoint handling for Cortex M7 #341
Merged
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
texane
added a commit
that referenced
this pull request
Oct 3, 2015
Breakpoint handling for Cortex M7
This was
linked to
issues
Apr 3, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This pull request uses chip_id to integrate the breakpoint handling for M7 targets into the handling of M0/1/3/4 breakpoints. The number of hardware breakpoints is not fixed by a define but read from the FP_CTRL register.
Tested on the STM32F746 Discovery, but must be tested on other targets before commited into main.
(Closes #266, Closes #273)