vivado-tcl
Use this skill when the user wants to generate, write, or execute Vivado/Vitis TCL scripts for FPGA design flows. This includes creating projects, running synthesis/implementation, programming devices, working with IP Integrator block designs, debug core insertion, constraint management, simulation, and any Vivado automation task. Trigger when the user mentions Vivado, Vitis, FPGA, TCL scripts for hardware design, bitstream generation, XDC constraints, ILA/VIO debug, or any Xilinx/AMD FPGA toolchain task. This skill generates and executes TCL — it does NOT analyze Vivado output or reports. For debug strategy and core configuration decisions use vivado-debug, for timing analysis use vivado-analysis.
adeleempurpled290 · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add adeleempurpled290/FPGA-Agent-skills --skill vivado-tcl技能说明
name: vivado-tcl description: Use this skill when the user wants to generate, write, or execute Vivado/Vitis TCL scripts for FPGA design flows. This includes creating projects, running synthesis/implementation, programming devices, working with IP Integrator block designs, debug core insertion, constraint management, simulation, and any Vivado automation task. Trigger when the user mentions Vivado, Vitis, FPGA, TCL scripts for hardware design, bitstream generation, XDC constraints, ILA/VIO debug, or any Xilinx/AMD FPGA toolchain task. This skill generates and executes TCL — it does NOT analyze Vivado output or reports. For debug strategy and core configuration decisions use vivado-debug, for timing analysis use vivado-analysis.
Vivado TCL Script Generation Guide
Overview
This skill generates Vivado TCL scripts and executes them via vivado -mode batch. It covers the full FPGA design flow: project creation, synthesis, implementation, bitstream generation, hardware programming, IP integration, debug, and simulation. For the complete command reference, see REFERENCE.md.
Critical Rules
- NEVER mix Project Mode and Non-Project Mode commands — they are incompatible flows
- Project Mode: uses
create_project,add_files,launch_runs,wait_on_run,open_run - Non-Project Mode: uses
read_verilog,synth_design,opt_design,place_design,route_design - Always ask the user which mode they want if not obvious from context
- This skill only generates/executes TCL — do NOT attempt to parse or analyze Vivado reports or logs
Execution Model
How to run a TCL script
# Batch mode (recommended for automation)
vivado -mode batch -source <script.tcl>
# With arguments
vivado -mode batch -source script.tcl -tclargs "ARG1=value1"
# Interactive TCL shell
vivado -mode tcl
Key output files
vivado.log— full session logvivado.jou— journal of TCL commands (reusable as script)*.dcp— design checkpoints (snapshots of design state)*.bit— bitstream files*.xsa— hardware platform for Vitis*.ltx— debug probes file
Quick Reference: Project Mode Flow
# 1. Create project
create_project <name> <dir> -part <part>
# 2. Add sources
add_files {./src/top.v ./src/sub.v}
add_files -fileset constrs_1 ./constraints/timing.xdc
update_compile_order -fileset sources_1
# 3. Synthesis
launch_runs synth_1
wait_on_run synth_1
# 4. Open synth results & reports
open_run synth_1 -name netlist_1
report_timing_summary -file syn_timing.rpt
report_power -file syn_power.rpt
# 5. Implementation + bitstream
launch_runs impl_1 -to_step write_bitstream
wait_on_run impl_1
# 6. Reports
open_run impl_1
report_timing_summary -file imp_timing.rpt
report_utilization -file imp_util.rpt
report_power -file imp_power.rpt
Quick Reference: Non-Project Mode Flow
# 0. Setup
set outputDir ./output
file mkdir $outputDir
# 1. Read sources
read_verilog {./src/top.v ./src/sub.v}
read_xdc ./constraints/timing.xdc
# 2. Synthesis
synth_design -top <top_module> -part <part>
write_checkpoint -force $outputDir/post_synth.dcp
report_timing_summary -file $outputDir/post_synth_timing.rpt
# 3. Implementation
opt_design
place_design
# Optional: phys_opt_design
route_design
write_checkpoint -force $outputDir/post_route.dcp
# 4. Reports
report_timing_summary -file $outputDir/post_route_timing.rpt
report_utilization -file $outputDir/post_route_util.rpt
report_power -file $outputDir/post_route_power.rpt
report_drc -file $outputDir/post_route_drc.rpt
# 5. Generate bitstream
write_bitstream -force $outputDir/top.bit
IP Integrator (Block Design)
# Create block design
create_bd_design "system"
# Add IP cores
create_bd_cell -type ip -vlnv xilinx.com:ip:<ip_name>:<version> <instance>
# Run automation (AXI connections, external ports)
apply_bd_automation -rule xilinx.com:bd_rule:processing_system7 \
-config {make_external "FIXED_IO, DDR"} [get_bd_cells ps7_0]
apply_bd_automation -rule xilinx.com:bd_rule:axi4 \
-config {Master "/ps7_0/M_AXI_GP0"} [get_bd_intf_pins peripheral/S_AXI]
# Validate, save, generate wrapper
assign_bd_address
validate_bd_design
save_bd_design
make_wrapper -files [get_files system.bd] -top
# Export for Vitis
write_hw_platform -fixed -include_bit -force ./system_wrapper.xsa
Hardware Programming
open_hw_manager
connect_hw_server -url localhost:3121
open_hw_target
current_hw_device [get_hw_devices <device>]
set_property PROGRAM.FILE {<bitstream>.bit} [current_hw_device]
set_property PROBES.FILE {<probes>.ltx} [current_hw_device]
program_hw_devices [current_hw_device]
close_hw_target
disconnect_hw_server
close_hw_manager
Debug Core Insertion (ILA)
# After synthesis, before implementation
open_run synth_1
# Create ILA
create_debug_core u_ila_0 ila
set_property C_DATA_DEPTH 1024 [get_debug_cores u_ila_0]
# Connect clock
set_property port_width 1 [get_debug_ports u_ila_0/clk]
connect_debug_port u_ila_0/clk [get_nets clk]
# Add probes
set_property port_width <width> [get_debug_ports u_ila_0/probe0]
connect_debug_port u_ila_0/probe0 [get_nets {<signal_list>}]
# Implement and write probes
implement_debug_core
write_debug_probes -force ./output/top.ltx
TCL Syntax Tips
Object queries
get_cells -hierarchical -filter "lib_cell =~ FD*"
get_pins -of [get_cells inst_1]
get_nets -of [get_pins inst_1/D]
get_property loc [get_cells inst_1]
set_property loc SLICE_X1Y27 [get_cells inst_1]
Bus indexing
add_wave {bus[4]} ;# braces for square brackets
add_wave bus(4) ;# parentheses work too
Error handling
if {[catch {<command>} result]} {
puts "Error: $result"
}
Workflow Guidelines
- Always write TCL to a
.tclfile first, then execute withvivado -mode batch -source - Include
file mkdirfor output directories to avoid errors - Use
write_checkpointat key stages in Non-Proje