README.txt 2.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748
  1. ################################################################################
  2. # Vivado (TM) v2020.2 (64-bit)
  3. #
  4. # README.txt: Please read the sections below to understand the steps required to
  5. # run the exported script and information about the source files.
  6. #
  7. # Generated by export_simulation on Wed May 03 12:25:18 +0700 2023
  8. #
  9. ################################################################################
  10. 1. How to run the generated simulation script:-
  11. From the shell prompt in the current directory, issue the following command:-
  12. ./MeasDataFifo.sh
  13. This command will launch the 'execute' function for the single-step flow. This
  14. function is called from the main 'run' function in the script file.
  15. The 'run' function first executes the 'setup' function, the purpose of which is to
  16. create simulator specific setup files, create design library mappings and library
  17. directories and copy 'glbl.v' from the Vivado software install location into the
  18. current directory.
  19. The 'setup' function is also used for removing the simulator generated data in
  20. order to reset the current directory to the original state when export_simulation
  21. was launched from Vivado. This generated data can be removed by specifying the
  22. '-reset_run' switch to the './MeasDataFifo.sh' script.
  23. ./MeasDataFifo.sh -reset_run
  24. To keep the generated data from the previous run but regenerate the setup files and
  25. library directories, use the '-noclean_files' switch.
  26. ./MeasDataFifo.sh -noclean_files
  27. For more information on the script, please type './MeasDataFifo.sh -help'.
  28. 2. Additional design information files:-
  29. export_simulation generates following additional file that can be used for fetching
  30. the design files information or for integrating with external custom scripts.
  31. Name : file_info.txt
  32. Purpose: This file contains detail design file information based on the compile order
  33. when export_simulation was executed from Vivado. The file contains information
  34. about the file type, name, whether it is part of the IP, associated library
  35. and the file path information.