aws / aws-fpga

Official repository of the AWS EC2 FPGA Hardware and Software Development Kit
Other
1.51k stars 516 forks source link

XILINX_VITIS varaiblet not set #508

Closed yanyr closed 4 years ago

yanyr commented 4 years ago

Hi,

after I source vitis_setup.sh a get these errors in the end: ERROR: XILINX_VITIS variable not set and vitis not in the path ERROR: Please set XILINX_VITIS variable to point to your location of your Xilinx installation or add location of vitis exectuable to your PATH variable

And I also cannot find Xilinx folder in the examples.

AWSbatsunil commented 4 years ago

Hi yanyr,

Can you please let us know the AMI that you are running the command on?

FPGA Developer AMI should be used to do FPGA related developments.

Thanks, Sunil.

yanyr commented 4 years ago

Hi Sunil,

the latest 1.7.1

Yan

On 2 Nov 2020, at 16:59, AWSbatsunil notifications@github.com wrote:

Hi yanyr,

Can you please let us know the AMI that you are running the command on?

FPGA Developer AMI https://aws.amazon.com/marketplace/pp/B06VVYBLZZ should be used to do FPGA related developments.

Thanks, Sunil.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/aws/aws-fpga/issues/508#issuecomment-720561046, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKRXX2CFLXCJO6XSYNFRRIDSN3JNVANCNFSM4TGBCDXQ.

deeppat commented 4 years ago

Hi @yanyr 1.7.1 is an updated version of the AMI with Xilinx toolset 2019.1 which does not include Vitis as Vitis was not launched till Xilinx 2019.2 tool release. To use Vitis, please use AMI v1.8.1 or 1.9.0 from the AWS Marketplace dropdown menu.

deeppat commented 4 years ago

Closing this issue. Please re-open if you weren't able to use v1.9.0!

Thanks, Deep

ashwintcs commented 1 year ago

Hi Just to confirm if we are following on-premise, do we still need to install Vitis on F1 instance?

kyyalama2 commented 1 year ago

If your design uses vitis flow, then you do need XRT envrionment and thsi should come by default if you are using one of the AWS provided AMIs. Thanks