Skip to content

RISC-V Debug Support for our PULP RISC-V Cores

License

Unknown, Apache-2.0 licenses found

Licenses found

Unknown
LICENSE
Apache-2.0
LICENSE.SiFive
Notifications You must be signed in to change notification settings

pulp-platform/riscv-dbg

Folders and files

NameName
Last commit message
Last commit date
Oct 4, 2022
Oct 24, 2023
Nov 2, 2022
Jul 8, 2024
Oct 8, 2020
Mar 15, 2024
Mar 6, 2022
Mar 19, 2020
Apr 4, 2022
Nov 10, 2023
Jan 24, 2019
May 21, 2019
Jul 8, 2024
Jun 25, 2020

Repository files navigation

RISC-V Debug Support for various Cores

This module is an implementation of a debug unit compliant with the RISC-V debug specification v0.13.1. It is used in the cva6, cv32e40p and ibex cores.

Implementation

We use an execution-based technique, also described in the specification, where the core is running in a "park loop". Depending on the request made to the debug unit via JTAG over the Debug Transport Module (DTM), the code that is being executed is changed dynamically. This approach simplifies the implementation side of the core, but means that the core is in fact always busy looping while debugging.

Features

The following features are currently supported

  • Parametrizable buswidth for XLEN=32 XLEN=64 cores
  • Accessing registers over abstract command
  • Program buffer
  • System bus access (only XLEN)
  • DTM with JTAG interface

These are not implemented (yet)

  • Trigger module
  • Quick access using abstract commands
  • Accessing memory using abstract commands
  • Authentication

Limitations

  • The JTAG clock frequency needs to be lower than the system's clock frequency (see also #163).

Tests

We use OpenOCD's RISC-V compliance tests, our custom testbench in tb/ and riscv-tests/debug.