-
Notifications
You must be signed in to change notification settings - Fork 516
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fail in get_f1_ami_id() #647
Comments
Hello! Thank you so much for reaching out with this issue. Currently the AWS CLI and boto3 is not working when run from an instance using the COMMAND import boto3
import botocore
f1_ami_name = "FPGA Developer AMI - 1.12.2-40257ab5-6688-4c95-97d1-e251a40fd1fc"
def get_f1_ami_id():
client = boto3.client('ec2')
response = client.describe_images(Filters=[{'Name': 'name', 'Values': [f1_ami_name]}])
assert len(response['Images']) == 1
print(response['Images'])
if __name__ == '__main__':
get_f1_ami_id() STDOUT
We recommend only launching new FireSim builds from a machine that is not running Thanks! |
Due to Centos end of life, some AWS CLI commands are not working on |
i have a fresh install of the FPGA AMI ( FPGA Developer AMI - 1.12.2-40257ab5-6688-4c95-97d1-e251a40fd1fc)and we are facing some problems in generateing bitstream.
when i run "firesim buildbitstream" command, it successfully Builds Verilog for FireSimWithNIC_DDR3FRFCFSLLC4MB_WithDefaultFireSimBridges_WithFireSimHighPerfConfigTweaks_chipyard.Sha3RocketConfig-F65MHz_BaseF1Config and FPGA driver for FireSimWithNIC_DDR3FRFCFSLLC4MB_WithDefaultFireSimBridges_WithFireSimHighPerfConfigTweaks_chipyard.Sha3RocketConfig-F65MHz_BaseF1Config.
But it encoutners fatal error when trying to get ami id.(below is the error message in log files)
i try to solve the problem from the web,and the CSL-KU/firesim-nvdla#1 is likely to be the same.
i follow the link, create a py file to test if the ami id is avaiable, but it fails.
By the way, i use a manager instance of z1d,2xlarge,which is also I launch bitstream on.
what can i do now ?
The text was updated successfully, but these errors were encountered: