- Newest
- Most votes
- Most comments
The issue you're experiencing with the init.tcl file is a common problem when setting up the FPGA development environment on AWS EC2 instances. This error suggests that there might be an issue with the Tcl (Tool Command Language) installation or configuration in your development environment.
To address this problem, you can try the following steps:
-
Ensure that you have properly sourced the setup script for the FPGA development environment. Typically, this is done by running:
source ~/aws-fpga/vitis_setup.sh
This script should set up the necessary environment variables and paths.
-
Verify that Tcl is installed on your system by running:
which tclsh
If it's not found, you may need to install Tcl.
-
If Tcl is installed but not found, you might need to update your PATH environment variable to include the directory where Tcl is installed.
-
Consider manually setting the TCL_LIBRARY environment variable to point to the correct Tcl library location. You can do this by adding the following line to your ~/.bashrc file (replace the path with the actual location of your Tcl library):
export TCL_LIBRARY=/usr/share/tcl8.6
After adding this line, source your ~/.bashrc file or restart your terminal.
-
Ensure that you are using the latest version of the AWS FPGA Developer AMI, as it may include fixes for such issues.
If these steps don't resolve the issue, you may need to reinstall the Xilinx tools or seek support from AWS FPGA development forums or AWS support.
Regarding your note about not running on an F2 instance, while it's possible to perform hardware emulation on non-F2 instances, it's important to note that for full hardware builds and certain optimizations, an F2 instance is recommended. The m4.2xlarge instance you're using should be sufficient for hardware emulation, but you might encounter some limitations or performance differences compared to running on an F2 instance.
Once you receive your quota increase and can access F2 instances, you may want to retry your build process on an F2 instance to ensure you're working in the environment most closely matching the final deployment target.
Sources
FPGA F2 development issue | AWS re:Post
Possible XRT installation bug in latest AWS Vitis f2 flow | AWS re:Post
Relevant content
- asked 7 years ago
- asked 4 years ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 5 years ago
