NewInstrCalBoard_Zynq/Debug_FW.ip_user_files/sim_scripts/system/xcelium

################################################################################
# Vivado (TM) v2023.2 (64-bit)
#
# README.txt: Please read the sections below to understand the steps required to
#             run the exported script and how to fetch design source file details
#             from the file_info.txt file.
#
# Generated by export_simulation on Mon May 25 15:47:32 CST 2026
#
################################################################################

1. Steps to run the generated simulation script

From the shell prompt in the current directory, issue the following command:-

./system.sh

This command will launch the 'compile', 'elaborate' and 'simulate' functions
implemented in the script file for the 3-step flow. These functions are called
from the main 'run' function in the script file.

The 'run' function first calls the 'check_args' function, the purpose of which
is to verify the generated script arguments and print error if incorrect switch
is specified. The 'run' function then calls the 'setup' function, the purpose of
which is to specify custom or initialization commands. The function also executes
following sub-functions:-
'reset_run' if -reset_run switch is specified.
'reset_log' if -reset_log switch is specified.

The purpose of 'reset_run' function' is to delete the simulator generated design
data from the previous run and the purpose of 'reset_log' function' is to delete
the simulator generated log files.

The 'run' function then calls the 'init_lib' function, the purpose of which is to
create design library mappings and directories. This function is called before the
'compile' step. By default, if '-step' switch is specified with the script then the
script will execute that specfic step, else it will execute all steps applicable
for the target simulator.

For more information on the script, please type './system.sh -help'

2. Design source file information

export_simulation generates a 'file_info.txt' file that contains design file information
based on the compile order when export_simulation was executed from Vivado. The file
contains information about the file name, type, library it is compiled into, whether
it is part of the IP, associated library, file path information in a comma separated
format. This file can be parsed to extract the required information for generating a
custom script or can be read from verification test infra.