DitDah-A1 is a configurable 64-bit RISC-V processor with up to sixteen coherent harts. It uses an eight-stage, in-order pipeline with one to three issue lanes.
| Component | Current implementation |
|---|---|
| ISA | RV64I/Zicsr/Zifencei with optional M/A/C/F/D and standard scalar extensions |
| Execution | Independent integer ALUs can follow one ordinary load/store; instructions using other resources issue alone |
| Privilege | M, optional M/U or M/S/U and H with HS/VS/VU; Bare, Sv39/Svade and Sv39x4 |
| Protection | Zero or sixteen PMP entries per hart, including internal memory and device paths |
| Memory | Private instruction/data caches, CPU data coherence, optional 128 KiB shared cache |
| Interfaces | AXI4 with 64/128/256/512-bit data; optional system-level JTAG Debug 1.0 subset |
The default uses one single-issue, M-mode hart with M/A, Bare addressing, and no caches, PMP, interrupts or JTAG. Atomic accesses require a qualified memory region and end-to-end exclusive monitoring. Optional Svnapot, Svpbmt, Svinval and host/guest pointer masking extend the supervisor memory system. Sv48 and vector execution are not implemented. RVA23S64 remains a target. Linux and FPGA operation have not been validated.
Module hierarchy:
flowchart TD
T[DitDahA1] --> C[1 to 16 cores]
T --> M[Memory fabric]
T --> D[Optional JTAG DTM, DMI bridge and Debug Module]
T --> P[Optional private data caches]
T --> S[Optional shared cache]
C --> F[Frontend]
C --> B[Backend]
See the system top, core and parameters.
Use Nix with flakes enabled. Run these commands from the repository root:
nix develop
make config
make check
configure-ditdah-a1 --rtl --config result/ditdah_a1_config.json --output result/checked.json
build-ditdah-a1 --config result/checked.json --output result/rtlresult/rtl contains SystemVerilog, filelist.f and the selected configuration in ditdah_a1_config.json.
make rtl independently generates the default configuration; it does not read the output of make config.
Software and external-debug tests need additional tools listed in Verification.
Edit the generated configuration's parameters object, then pass the file explicitly with --config.
Without --rtl, the configuration command checks the parameter schema, which also describes unimplemented target values.
The builder validates the selected system or component before generating RTL.
Configuration documents supported values, memory requirements, fault behavior and integration contracts.
System JTAG needs an explicit jtagIdcode and debugBase; attached AXI peers must follow the systemResetActive reset domain.
With enableJtag, standalone Core and Backend builds expose a debug execution interface instead of JTAG pins.
make verify-simulation # scalar and multicore RTL checks
make verify-signoff # full hardware verification campaignThe campaign includes software, protocol checks, formal properties and negative controls; its runtime depends on configuration and workload. See Verification for prerequisites, individual gates, reports and acceptance limits. These checks do not establish full ISA compliance, RVA23 conformance or physical signoff.
Project code uses MIT; the arithmetic library retains BSD-3-Clause notices. See REUSE.toml.
- CHIPS Alliance Rocket: processor architecture and configurable hardware design.
- CHIPS Alliance T1: hardware generation and verification workflows.
- DitDah-E1: project structure and reproducible configuration workflow.
- Zaozi: hardware description framework and pinned development tools.
- RISC-V specifications: instruction and privilege contracts.
- LLVM, CIRCT and YosysHQ: compiler and verification tools.
- Berkeley HardFloat: IEEE 754 arithmetic.
- RISC-V architectural tests, Sail, RVFI instruction models and herdtools7: architectural and memory-model checks.
- Zephyr: multicore software tests.