This chapter explains the differences between Non-Project Mode and Project Mode. To fully understand Non-Project Mode in the AMD Vivado™ Design Suite, first review Project Mode as described in Using Project Mode.
In Non-Project Mode, you use Tcl commands to compile a design through the entire flow. AMD Vivado™ creates an in-memory project to manage various properties of a design, but the project file is not written to disk and its status is not preserved.
Tcl commands give you flexibility to set up, run, analyze, and debug designs. Run Tcl commands in batch mode, from the Vivado Design Suite Tcl shell, or through the Vivado IDE Tcl Console. Non-Project Mode gives you full control over each design flow step, but you must manually manage source files, reports, and design checkpoints (DCP)s. You can generate reports, perform DRCs, and write DCPs at any stage of the implementation process.
The config_flows command supports -synth_strategy and
-impl_strategy options. You can use these options in Non-Project
flows to apply preset implementation strategy compile options. This approach lets you
avoid manually specifying individual directives and options for each flow command.
- For more information on synthesis strategies, refer to Vivado Synthesis in Vivado Design Suite User Guide: Synthesis (UG901).
- For more information on implementation strategies, refer to Implementing the Design in Vivado Design Suite User Guide: Implementation (UG904).
Unlike Project Mode, Non-Project Mode does not include runs infrastructure, source file management, or design state reporting. Whenever you update a source file, rerun the design manually. Default reports and intermediate files do not generate automatically. Use Tcl commands to create necessary reports and DCPs. You can still access GUI-based design analysis and constraints assignment in the Vivado IDE.
In Non-Project Mode, you can open the current in-memory design or any saved DCP in the IDE. The IDE omits Project Mode features such as Flow Navigator, Project Summary, and IP catalog. You cannot access or modify synthesis or implementation runs from the IDE. If source files remain in their original locations, cross probe to design objects across multiple windows. You can open either the current design in memory or any saved DCP in the Vivado IDE.
For example, select design objects and use one of the following options to open the RTL files. You can then highlight the relevant lines.
- Go To Instantiation
- Go To Definition
- Go To Source
You must write reports or DCPs to save the in-memory design as it progresses. The DCP is an exact file representation of the in-memory design. Save DCPs after steps such as post-synthesis, post-optimization, and post-placement. Read a DCP file back into Vivado to restore the captured design state.
You can open a DCP in the Vivado IDE to perform interactive constraints assignment and design analysis. When viewing the active design in memory, changes automatically carry forward in the flow. Save updated constraints or new DCPs for future runs.
Most Non-Project Mode features are also available in Project Mode. However, Project Mode does not include certain options, such as source file and run results management, saving configurations, design status, and IP integration. Use Non-Project Mode to skip specific processes and reduce the design’s memory footprint. This also saves disk space by avoiding project-related files.