Following is a list of additional files you may consider revision controlling:
- Simulation scripts for third-party simulators generated by
export_simulation. Because these are typically hand-off files between design and verification, you might want to snapshot them at different stages of the design process. - XSA files. These are hardware hand-off files between Vivado and Vitis™ software platform.
- Bitsteams/PDIs.
- LTX files for hardware debug
- Intermediate DCP files created during the flow
- IP output products. These are usually considered output products, but if you
do not want to upgrade an IP when migrating between Vivado
releases, then you must manage the output files. Vivado only
provides one version of each IP per release. If the IP you are using is updated
between Vivado releases then there are only two choices:
- Upgrade the IP to the latest version in the latest Vivado release. This may cause you to change your design to accommodate IP RTL changes.
- Revision control the output products of the IP. The IP will be locked in the newer version of Vivado because you will not be able to re-customize the IP. But, this allows you to carry the IP forward to a future release because you are essentially capturing all the RTL sources for the IP.