How skandakm29/shakti_risc_v_32i works
Main Components
– ALU (e.g., module_fn_alu, mkalu)
– Register File (e.g., RegFile.v and RegFileLoad.v)
– Control/CSR Unit (e.g., mkcsr.v, mkcsrfile.v)
– Pipeline stages modules (e.g., mkstage1.v, mkstage2.v, mkstage3.v)
• Memory Subsystem – Highlight the BRAM modules (e.g., BRAM1Load.v, BRAM2.v, etc.) which likely serve as on-chip memory.
• FIFO and Synchronization Units – Include modules like FIFO, SyncFIFO, and SyncHandshake that manage buffering and clock-domain crossings.
• Boot and External Interfaces – Use the “boot.hex” and boot loader binaries (boot.LSB, boot.MSB) to indicate a boot sequence or initialization process.
• Additional Modules – Other supporting modules like address validation, decode units, and signal inverters (e.g., ClockInverter.v, ResetEither.v) should be shown as peripheral functional blocks.
Relationships and Data Flow
• Data paths between the CPU’s register file, the ALU, and memory modules.
• Interactions between pipeline stages—marking interfaces between mkstage1, mkstage2, and mkstage3 blocks.
Architectural Patterns and Design Principles
• Modularity – Emphasize that each hardware block (e.g., arithmetic, control, memory) is a separate Verilog module, permitting reuse and easier testing.
• Pipeline Architecture – Since there are clearly distinct “stage” modules, outline the pipeline flow from instruction fetch through execution.
• Synchronous Design – Signal the synchronization mechanisms in place (e.g., SyncFIFO, SyncHandshake, SyncReset) which are critical in digital circuits.
• Boot and Initialization Flow – Capture how the boot loader (using boot.hex) interacts with the processor core to start the system.
Specify Relevant Technologies and Tools
• Verilog HDL – Indicate that all components are designed in Verilog.
• FPGA/ASIC Context – Given the file organization (presence of binary output and synthesis report files like yosys_report.txt), the target might be an FPGA or ASIC.