Based on the error messages you've shared, it appears there are issues with running a simulation in Vivado. Let's break down the errors and discuss potential solutions:

1. [Common 17-180] Spawn failed: Broken pipe This error typically occurs when there's a communication problem between Vivado and its subprocesses. It could be due to system resource limitations or conflicts with other software.
2. [USF-XSim-62] 'compile' step failed with error(s) This indicates that the compilation step of your simulation failed. The error suggests checking the compile.bat file for correct permissions and reviewing the Tcl console output for more specific errors.
3. [Vivado 12-4473] Detected error while running simulation This is a general error indicating that the simulation couldn't run due to the previous errors.

To address these issues, try the following steps:

1. Check file permissions: Ensure that all project files, especially the compile.bat file, have the correct read/write/execute permissions.
2. Review Tcl console output: Look for more specific error messages in the Tcl console that might provide additional details about the compilation failure.
3. Clean and rebuild: Try cleaning your project and rebuilding it from scratch. In Vivado, go to "Project" -> "Clean Project" and then rebuild.
4. Check system resources: Ensure your computer has enough free RAM and disk space to run the simulation.
5. Update Vivado: If you're not using the latest version, consider updating Vivado to the most recent version as it might include fixes for these issues.
6. Verify source files: Double-check your source files for any syntax errors or issues that might be causing the compilation to fail.
7. Run as administrator: Try running Vivado as an administrator to ensure it has all necessary permissions.
8. Disable antivirus temporarily: Sometimes antivirus software can interfere with Vivado's processes. Try temporarily disabling it to see if it resolves the issue.

If these steps don't resolve the problem, you may need to provide more information about your project setup, the specific files you're working with, and any recent changes you've made to help diagnose the issue more accurately.