How mrvbeth/-distributeurcafe works
Project Type and Purpose
• This is a single-target FPGA design (“DistributeurCafe”) described in VHDL.
• Its purpose is to implement a “coffee‐dispenser” controller in hardware.
File Structure
Top-level files:
• DistributeurCafe.vhd ← main VHDL source (plus .bak)
• DistributeurCafe.qsf ← Quartus Pin & device constraints
• DistributeurCafe.qpf ← Quartus project file
• DistributeurCafe.pof ← generated FPGA programming file
• DistributeurCafe.pin ← pin assignment file
• DistributeurCafe.vwf ← waveform for simulation
• *.rpt, *.summary ← synthesis/fit/asm/map/tan reports
Directories:
• db/ ← Quartus compilation database & logs
• incremental_db/ ← per-partition compiled artifacts for incremental builds
Core Components
a. Source Layer
– VHDL modules (DistributeurCafe.vhd, any submodules)
– Constraint files (.qsf, .pin)
– Testbench/waveform (.vwf)
b. Toolchain Flow
– Simulation (ModelSim or built-in Quartus simulator)
– Synthesis (Quartus Synthesis → netlist)
– Fitter/Mapper (Fit → Placement & Routing)
– Assembler (ASM → .pof bitstream)
– Timing Analysis (TAN)
– Reports generation (fit.rpt, map.rpt, asm.rpt, tan.rpt)
c. Database & Incremental Compilation
– Master DB (db/)
– Partitioned DBs (incremental_db/compiled_partitions)
Relationships and Data Flows
1. VHDL + constraints → Simulation → waveform results
2. VHDL + constraints → Synthesis → netlist
3. Netlist → Fitter/Mapper → placed/routed design
4. Placed/routed design → Assembler → .pof bitstream
5. Bitstream → FPGA hardware
6. Each tool stage reads/writes into the project DB (db/) or incremental_db/.
Architectural Patterns
– Modular VHDL hierarchy (you may show top-level ‘DistributeurCafe’ and child blocks).
– Clear separation of “compile stages” vs. “physical implementation stages.”
Technology Stack
– Intel Quartus Prime (synthesis, fitter, assembler, timing)
– VHDL (RTL description)
– FPGA device (as specified in .qsf)
– (Optional) ModelSim or Quartus Simulator for functional verification