Allow GDB to debug RSP #197
Open
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
Add debug hooks to RSP Allow gdb stub to debug RSP
lambertjamesd
changed the title
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.
This pull request first moves debug hooks code out of the VR3400 code into a common location usable by both the cpu and rsp. I then add debugging hooks to the rsp and allow the gdb debugger to debug the rsp.
The debugger maps the memory range 0-0x1000 to the rsp IMEM. Adding breakpoints to that memory range will add them to the RSP. All other breakpoints go to the CPU. If a breakpoint is hit in the RSP registers will be read from the RSP in all other cases registers will be read from the CPU.
This PR also maps the memory at 0x04020000 to the vector registers of the RSP but only from the perspective of the debugger. This mapping does't effect the memory bus inside the emulator.