How kowdoorshashank/amba5-chi works
Project Type and Purpose
• This is a SystemVerilog hardware-design and verification project focusing on a CHI (Cache-Coherent Hub Interface) requester node and home node.
• The primary goal is to simulate and verify CHI protocol behavior: two DUT modules (chi_requester_node.sv and chi_home_node.sv) interconnected via CHI signals, driven and observed by a SystemVerilog testbench (chi_testbench.sv).
File‐Structure Analysis
• Top‐level files:
• chi_pkg.sv – package defining CHI parameters, types, interfaces
• chi_requester_node.sv – the requester DUT module
• chi_home_node.sv – the home node DUT module
• chi_testbench.sv – top‐level testbench that instantiates both DUTs and performs stimulus/checking
• README.md – link to EDA Playground for quick simulation
Key Points from README
• Simulation is intended to run on EDA Playground (link provided).
• No higher‐level application or software component—pure hardware simulation environment.
Main Components
a. Testbench Harvest (chi_testbench)
• Clock generator
• Reset logic
• Stimulus driver (generates CHI transactions)
• Checker/monitor logic
b. DUT: chi_requester_node
c. DUT: chi_home_node
d. Shared CHI interface (bus)
e. chi_pkg (parameter definitions, interface declarations)
Relationships & Interactions
• The testbench block instantiates both DUT modules and the chi_pkg for interface bindings.
• A single CHI bus (a bundle of request/response channels) interconnects the requester node to the home node.
• The testbench drives requests into the requester node, which sends transactions over the CHI bus to the home node.
• The home node responds via the same bus back to the requester; the testbench monitors responses.
Architectural Patterns & Principles
• Modular hierarchy: chi_pkg → DUT modules → top‐level testbench.
• Separation of concerns:
• Parameter and interface definitions in a package
• Pure DUT logic in separate modules
• Testbench harness for stimulus and observation
• Use of SystemVerilog interfaces and parameterization for scalability
Technologies & Frameworks
• SystemVerilog (design + verification constructs)
• EDA Playground (simulation environment)
Final Advice
• Be exhaustive: show every logical block (stimulus driver, monitor, interface definitions).
• Keep hierarchy clear: top‐level testbench above, DUT modules below.
• Use consistent naming to reflect file/module names.