How fred-framework/dart works
DART automates FPGA DPR design: a user supplies a YAML design description, then DART prepares resource and task inputs, optimizes placement/allocation for a supported device, and generates implementation artifacts. The README identifies partitioning, floorplanning, routing, and bitstream generation as product capabilities; the source tree also exposes wrapper and FRED integration generation. The main entry point and optimizer handoff are partly visible, but implementation-generation calls and some subsystem wiring are not, so uncertain links are omitted or marked unverified.
Main entry points: milp_solver_interface.h Solver interface · gurobi_c++.h Gurobi API · flora.cpp Input preparation and planning · main.cpp CLI and YAML validation
Components 16
Entry and orchestration
- CLI and YAML validation
without_gui/src/main.cpp - PR flow orchestration
without_gui/src/pr_tool.cpp
Planning and optimization
- Input preparation and planning
without_gui/src/flora.cpp - CSV data handling
include/csv_data_manipulator.hpp - Solver interface
include/milp_solver_interface.h - Partition model
src/partition.cpp
FPGA device models
- PYNQ optimizer
src/devices/pynq/milp_model_pynq.cpp - PYNQ partition optimizer
src/devices/pynq/milp_model_pynq_with_partition.cpp - ZCU-102 optimizer
src/devices/zcu_102/milp_model_us.cpp - US-96 optimizer
src/devices/us_96/milp_model_us_96.cpp - Zynq partition optimizer
src/not_used/zynq/milp_model_zynq_with_partition.cpp - Gurobi API
include/gurobi_c++.h
Implementation generation
- Floorplan constraints
include/generate_xdc.h - Accelerator wrapper generation
without_gui/include/gen_wrapper.h - Implementation and FRED artifacts
without_gui/src/pr_tool.cpp
Other components
- Design author
Connections 19
- Design author → CLI and YAML validation: supplies YAML
without_gui/src/main.cpp - CLI and YAML validation → Input preparation and planning: starts planning
without_gui/src/main.cpp - CLI and YAML validation → PR flow orchestration: starts PR flow
without_gui/src/main.cpp - Input preparation and planning → CSV data handling: uses data handling
- Input preparation and planning → Solver interface: uses solver contract
- Solver interface → Partition model: shares partition types
include/milp_solver_interface.h - Solver interface → PYNQ optimizer: declares entry point
include/milp_solver_interface.h - Solver interface → PYNQ partition optimizer: declares entry point
include/milp_solver_interface.h - Solver interface → ZCU-102 optimizer: declares entry point
include/milp_solver_interface.h - Solver interface → US-96 optimizer: declares entry point
include/milp_solver_interface.h - Solver interface → Zynq partition optimizer: declares entry point
include/milp_solver_interface.h - PYNQ optimizer → Gurobi API: uses optimization API
src/devices/pynq/milp_model_pynq.cpp - PYNQ partition optimizer → Gurobi API: uses optimization API
src/devices/pynq/milp_model_pynq_with_partition.cpp - ZCU-102 optimizer → Gurobi API: uses optimization API
src/devices/zcu_102/milp_model_us.cpp - US-96 optimizer → Gurobi API: uses optimization API
src/devices/us_96/milp_model_us_96.cpp - Zynq partition optimizer → Gurobi API: uses optimization API
src/not_used/zynq/milp_model_zynq_with_partition.cpp - Input preparation and planning → Floorplan constraints: generates constraints
without_gui/src/flora.cpp - PR flow orchestration → Accelerator wrapper generation: generates wrapper
- PR flow orchestration → Implementation and FRED artifacts: generates implementation files
without_gui/src/pr_tool.cpp