Patch Release v4.8.5

Pull Requests Since v4.8.4

Unlabeled

1. #301 - vivado/vcs.tcl Update
2. #302 - Added variables for VCS script generation

Pull Request Details

vivado/vcs.tcl Update

Author:	Larry Ruckman [email protected]
Date:	Mon Jul 10 14:23:44 2023 -0700
Pull:	#301 (39 additions, 33 deletions, 3 files changed)
Branch:	slaclab/vcs-vivado-2023-dev

Notes:

Description

• Fixed the issue with Vivado 2023.1 changing sim_vcs_mx.sh format
• Cleaned up the sim_vcs_mx.sh.tcl parsing in vcs.tcl as well
• Tested on both Vivado 2022.2 and Vivado 2023.1

---

Added variables for VCS script generation

Author:	Larry Ruckman [email protected]
Date:	Mon Aug 7 11:11:15 2023 -0700
Pull:	#302 (16 additions, 3 deletions, 3 files changed)
Branch:	FilMarini/vcs_fix

Notes:

List of changes:

vivado/vcs.tcl

• If VCS_LIB_PATH variable exists, then that is PATH where the vivado compiled libraries for VCS are, otherwise use default PATH ${VIVADO_INSTALL}/vcs-${VersionNumber}
• if VIVADO_PROJECT_SIM exists, then set that as simulation name, otherwise set as [get_property top [get_filesets sim_1]]
  (NB the variable VIVADO_PROJECT_SIM is used also in vivado/xsim.tcl and vivado/msim.tcl scrips)

vivado/sources.tcl

• if VIVADO_PROJECT_SIM is set, then set it as simulation top level (otherwise you would have conflict if you run directly make vcs after a make clean. This might make the change in vivado/vcs.tcl concerning the use of VIVADO_PROJECT_SIM variable useless, but since that is what is done in both xsim.tcl and msim.tcl, I would leave it as double confirmation, in case you want to modify the simulation top level after having done make sources.

system_vivado.mk

• Just a small beautify, fix of a previous PR i made

---