-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
New GDB monitor command for reading target registers #115
Comments
Development work for this is complete. I have added two GDB monitor commands: Listing registers (
|
I may add a |
Currently, the only way to read target registers via GDB is to issue a memory access command, and supply a memory address. This is tedious and the output format is limited. I believe this can be improved with a new GDB monitor command, using TDF keys to reference peripherals and registers.
With the new TDF format, all peripherals, register groups and registers have unique keys that can be used to reference those entities.
I'd like to introduce a new
rr
(read register) monitor command:Which should output the details of the register, as well as its current value, in hexadecimal and binary form. The output should also include all bit fields, and their current values.
Example:
Users can use the new target details page on the Bloom website to obtain peripheral and register keys:
The text was updated successfully, but these errors were encountered: