Skip to content
This repository was archived by the owner on Mar 7, 2026. It is now read-only.

Single register access - Target methods and GDB server support#291

Merged
UweBonnes merged 5 commits into
blackmagic-debug:masterfrom
gsmcmullin:single_register_access
Sep 1, 2019
Merged

Single register access - Target methods and GDB server support#291
UweBonnes merged 5 commits into
blackmagic-debug:masterfrom
gsmcmullin:single_register_access

Conversation

@gsmcmullin
Copy link
Copy Markdown
Contributor

  • Add new target methods to access single registers
  • Add GDB packets support for p and P packets
  • Implement new methods in Cortex-M and Cortex-A drivers

@UweBonnes
Copy link
Copy Markdown
Contributor

Where is this access used?

@gsmcmullin
Copy link
Copy Markdown
Contributor Author

It's used when GDB sends us one of these packets. It's not needed for the ARM targets, but is needed by upcoming RISC-V support where GDB queries high numbered registers that aren't present in the g and G packets. I might argue that what's being done in RISC-V GDB is bad, but they're unlikely to care.

@gsmcmullin gsmcmullin mentioned this pull request Oct 3, 2017
@UweBonnes UweBonnes merged commit e6504e1 into blackmagic-debug:master Sep 1, 2019
@UweBonnes
Copy link
Copy Markdown
Contributor

Perhaps helpful for those thinking about RiscV support

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants