You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Contributors are encouraged to be a [member](https://www.openhwgroup.org/membership/) of the
3
-
OpenHW Group. New members are always welcome.
2
+
New Contributors and new Members are always welcome!
3
+
Although membership is not required, most Contributors are [members](https://openhwfoundation.org/membership/become-a-member/)
4
+
of the OpenHW Foundation and participate in one or more of our [Projects](https://openhwfoundation.org/projects/).
5
+
6
+
## Contributor Agreement
7
+
Contributors **must** be covered by the terms of the [Eclipse Contributor Agreement](https://www.eclipse.org/legal/ECA.php)
8
+
(for individuals) **or** the [Eclipse Member Committer and Contributor Agreement](https://www.eclipse.org/legal/committer_process/EclipseMemberCommitterAgreement.pdf)
9
+
(for employees of Member companies). The ECA/MCCA provides a legal
10
+
framework for a Contributor's technical contributions to the OpenHW Foundation,
11
+
including provisions for grant of copyright license and a Developer
12
+
Certificate of Origin on contributions merged into OpenHW Foundation repositories.
4
13
5
14
## Getting Started
6
-
The [OpenHW Work Flow](https://github.com/openhwgroup/programs/blob/5fa810bf16d25cf32c7eca58be084975bec38f96/TGs/verification-task-group/documents/presentations/OpenHWGroup_WorkFlow.pdf) document
7
-
is required reading. You will find information about the implementation and usage of the CORE-V verification environments
8
-
in the [Verification Strategy](https://docs.openhwgroup.org/projects/core-v-verif/en/latest/index.html).
15
+
The [OpenHW Work Flow](https://github.com/openhwgroup/programs/blob/5fa810bf16d25cf32c7eca58be084975bec38f96/TGs/verification-task-group/documents/presentations/OpenHWGroup_WorkFlow.pdf)
16
+
document is recommended reading.
9
17
10
18
## The Mechanics
11
19
1. From GitHub: [fork](https://help.github.com/articles/fork-a-repo/) the [cve2](https://github.com/openhwgroup/cve2) repository
3. Create your feature branch: `git checkout -b <my_branch>.`<br> Please uniquify your branch name. See the [Git Cheats](https://github.com/openhwgroup/core-v-verif/blob/master/GitCheats.md)
14
22
for a useful nominclature.
15
23
4. Make your edits...
16
-
5. Commit your changes: `git commit -m 'Add some feature' -s`<br>; `-s` or `--sign-off` is engouraged, but not required.
24
+
5. Commit your changes: `git commit -m 'Add some feature' -s`
Copy file name to clipboardexpand all lines: doc/03_reference/debug.rst
+14-19
Original file line number
Diff line number
Diff line change
@@ -3,12 +3,12 @@
3
3
Debug Support
4
4
=============
5
5
6
-
Ibex offers support for execution-based debug according to the `RISC-V Debug Specification <https://riscv.org/specifications/debug-specification/>`_, version 0.13.
6
+
CVE2 offers support for execution-based debug according to the `RISC-V Debug Specification <https://riscv.org/specifications/debug-specification/>`_, version 0.13.
7
7
8
8
9
9
.. note::
10
10
11
-
Debug support in Ibex is only one of the components needed to build a System on Chip design with run-control debug support (think "the ability to attach GDB to a core over JTAG").
11
+
Debug support in CVE2 is only one of the components needed to build a System on Chip design with run-control debug support (think "the ability to attach GDB to a core over JTAG").
12
12
Additionally, a Debug Module and a Debug Transport Module, compliant with the RISC-V Debug Specification, are needed.
13
13
14
14
A supported open source implementation of these building blocks can be found in the `RISC-V Debug Support for PULP Cores IP block <https://github.com/pulp-platform/riscv-dbg/>`_.
@@ -18,29 +18,24 @@ Ibex offers support for execution-based debug according to the `RISC-V Debug Spe
0 commit comments