-
-
Notifications
You must be signed in to change notification settings - Fork 773
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature: Initial RISC-V debug support (v0.13 spec) #1380
Merged
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
dragonmux
added
Enhancement
General project improvement
New Target
New debug target
labels
Feb 11, 2023
dragonmux
force-pushed
the
feature/risc-v
branch
4 times, most recently
from
February 12, 2023 08:30
2f979c6
to
a7f8493
Compare
dragonmux
force-pushed
the
feature/risc-v
branch
from
February 12, 2023 21:17
a7f8493
to
c24c26f
Compare
dragonmux
force-pushed
the
feature/risc-v
branch
3 times, most recently
from
March 28, 2023 02:25
e83a3c4
to
6d26f71
Compare
dragonmux
force-pushed
the
feature/risc-v
branch
4 times, most recently
from
April 4, 2023 08:04
70bfb82
to
f37451f
Compare
dragonmux
force-pushed
the
feature/risc-v
branch
2 times, most recently
from
April 17, 2023 03:13
6c4e7da
to
b13aafb
Compare
dragonmux
force-pushed
the
feature/risc-v
branch
from
April 24, 2023 13:17
b13aafb
to
9c73087
Compare
dragonmux
force-pushed
the
feature/risc-v
branch
2 times, most recently
from
June 6, 2023 05:25
2da4783
to
26d0935
Compare
dragonmux
force-pushed
the
feature/risc-v
branch
2 times, most recently
from
June 22, 2023 05:13
a3817aa
to
69874a2
Compare
dragonmux
force-pushed
the
feature/risc-v
branch
3 times, most recently
from
July 7, 2023 00:17
de4fc3d
to
488cdea
Compare
dragonmux
force-pushed
the
feature/risc-v
branch
2 times, most recently
from
July 20, 2023 07:07
51957f7
to
fbec35e
Compare
…nd what kinds of triggers they each support
…h and breakpoints
…operation on rv64
…ledgement of the reset
…ng unsuitable trigger slots
…rmat and store it as a DMI designer code
…djust for BMD's representation of JEP-106 codes
…ose some CSRs register in the xml description
dragonmux
force-pushed
the
feature/risc-v
branch
from
October 31, 2023 05:34
94cd98a
to
11ec1f1
Compare
esden
approved these changes
Oct 31, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fantastic! Finally! Thank you!
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.
Detailed description
In this PR we implement support for debugging RISC-V targets complying with v0.13.2 of the RISC-V debug specification. This includes support for both rv32 and rv64 targets and intentionally fails to work with rv128 targets (though we still must detect those).
This PR also introduces support for the GD32VF1 series through minimal changes to stm32f1.c, providing a test target to play with.
Known limitations include:
This PR replaces #924.
Your checklist for this pull request
make PROBE_HOST=native
)make PROBE_HOST=hosted
)Closing issues
Fixes #794