https://github.com/riscv/riscv-debug-spec

Working Draft of the RISC-V Debug Specification Standard
https://github.com/riscv/riscv-debug-spec

Last synced: 4 days ago
JSON representation

Working Draft of the RISC-V Debug Specification Standard

• Host: GitHub
• URL: https://github.com/riscv/riscv-debug-spec
• Owner: riscv
• License: other
• Created: 2017-01-20T20:58:54.000Z (almost 8 years ago)
• Default Branch: main
• Last Pushed: 2024-09-12T16:25:16.000Z (2 months ago)
• Last Synced: 2024-09-13T05:29:32.501Z (2 months ago)
• Language: Python
• Homepage: https://jira.riscv.org/browse/RVG-94
• Size: 48.7 MB
• Stars: 454
• Watchers: 73
• Forks: 92
• Open Issues: 52
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
RISC-V Debug Specification

==========================

You may be looking for one of the following pre-built PDFs:

* [Latest release candidate](https://github.com/riscv/riscv-debug-spec/releases)

* [Latest release](https://github.com/riscv/riscv-debug-spec/blob/release/riscv-debug-release.pdf)

  (This is outdated at this point, and only of historical interest.)

Build Instructions

------------------

```

sudo apt-get install git make python3 python3-sympy graphviz texlive-full

make

```

There are two other interesting make targets:

1. `make debug_defines` creates a C header and implementation files containing

   constants for addresses and fields of all the registers and abstract

   commands, as well as function and structures used to decode register values.

   An implementation of such decoder can be seen in `debug_reg_printer.c/h`.

2. `make chisel` creates scala files for DM registers and abstract commands

   with the same information.

Contributing

------------------

There are various ways to contribute to this spec. You can use a combination of them to get your idea across.

Please note that pull requests will only be reviewed/accepted from RISC-V Foundation members.

1. Make a PR. This is the best way to deal with minor typos and edits.

2. File an issue with something that you want to know or see.

3. Discuss higher-level questions or ideas on the riscv-debug-group mailing list: https://lists.riscv.org/g/tech-debug

For More Information

------------------

Additional information can be found at

https://github.com/riscv/debug-taskgroup