https://github.com/trmckay/universal-otter-debugger

Implementation of the RISC-V UART Debugger for Cal Poly's Otter
https://github.com/trmckay/universal-otter-debugger

Last synced: about 1 month ago
JSON representation

Implementation of the RISC-V UART Debugger for Cal Poly's Otter

• Host: GitHub
• URL: https://github.com/trmckay/universal-otter-debugger
• Owner: trmckay
• License: gpl-3.0
• Created: 2020-08-11T01:32:15.000Z (over 4 years ago)
• Default Branch: master
• Last Pushed: 2020-12-20T17:01:28.000Z (about 4 years ago)
• Last Synced: 2024-10-12T06:22:37.407Z (2 months ago)
• Language: SystemVerilog
• Size: 2.02 MB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# universal-otter-debugger

## About ##

This project allows you to debug and program your Otter from a host machine.

![Block diagram](doc/block_diag.png)

## Features ##

- Read/write registers

- Read/write memory

- Program the Otter without re-synthesizing

- Breakpoints

- Pause/resume execution

- Configurable variables for commonly used values

- Communicates over the same micro-USB used to program the board

## Required files ##

Debugging your Otter depends on three semi-independent projects: a general RISC-V debugger module, its client, and the adapter

for the Otter. This repository houses the adapter (`otter_DBU.sv`).

```

git clone https://github.com/trmckay/universal-otter-debugger

```

The [RVDB project](https://github.com/trmckay/riscv-uart-debugger) houses everything else you need.

You will need to install the client to your machine and include the Verilog files under `module` in

your Otter project.

I recommend thoroughly reading the README there, as well as skimming the man page (`man rvdb`) once it

is installed.

## Implementing the module ##

Implementing the module for your Otter is very simple, as it uses standard Otter signals.

In general, internal MCU signals should be used when `db_active` is low and debugger signals when it is high.

More detailed instructions are included the [documentation](doc/multicycle_instructions.pdf).