run_multiple_start (::quartus::stp)

Belongs to ::quartus::stp 1.0

Defines the start of a set of "run" commands. This command 
is used when multiple instances of data acquisition are 
started simultaneously. Add this command before the set of 
"run" commands that specify data acquisition. Add 
"run_multiple_end" after the set of commands. 

If "run_multiple_end" is not included, the "run" commands 
do not execute.

#opens signaltap session
open_session -name stp1.stp

#start acquisition of instance auto_signaltap_0 and auto_signaltap_1 at the same time
#calling run_multiple_end will start all instances run after run_multiple_start call

#start acquistion using the configuration last saved; timeout after 5 seconds if no trigger occurs
#NOTE: Use this to replicate how SignalTap GUI works.
#      Only one acquisition is saved into the .stp file upon close_session next.
run_multiple_start
run -instance auto_signaltap_0 -timeout 5
run -instance auto_signaltap_1 -timeout 5
if { [catch {run_multiple_end} err_msg} {
	# Timeout event is thrown as TCL exception
	puts "ERROR: $err_msg"
}

#start acquistion using a specific configuration saved in the data log tree; timeout after 5 seconds if no trigger occurs
#signal_set_1 and trigger_1 must exist in the data log tree as saved in the .stp file. 
#log_1 will be created to hold the acquired data. if -data_log is not specified, a log name is generated automatically.
#NOTE: Use this to save multiple acquisition data logs by executing this command in a loop.
run_multiple_start
run -instance auto_signaltap_0 -signal_set signal_set_1 -trigger trigger_1 -data_log log_1 -timeout 5
run -instance auto_signaltap_1 -signal_set signal_set_1 -trigger trigger_1 -data_log log_1 -timeout 5
if { [catch {run_multiple_end} err_msg} {
	# Timeout event is thrown as TCL exception
	puts "ERROR: $err_msg"
}

#close signaltap session
close_session