Skip to content
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

create_sdaccel_afi.sh cannot connect to the S3 endpoint #424

Closed
adki opened this issue Aug 26, 2018 · 7 comments
Closed

create_sdaccel_afi.sh cannot connect to the S3 endpoint #424

adki opened this issue Aug 26, 2018 · 7 comments

Comments

@adki
Copy link

adki commented Aug 26, 2018

kristopk may suggest to post this issue on AWS forum, but I could not find any discussion on 'create_sdaccel_afi.sh' on the forum.

I tried to make awsxclbin from xclbin using create_sdaccel_afi.sh,

[centos@AWS] $SDACCEL_DIR/tools/create_sdaccel_afi.sh -xclbin=krnl_vadd.hw.xilinx_aws-vu9p-f1-04261818_dynamic_5_0.xclbin -o=krnl_vadd.hw.xilinx_aws-vu9p-f1-04261818_dynamic_5_0.awsxclbin -s3_bucket=sdaccel-fpga -s3_dcp_key=sdaccel-dcp -s3_logs_ke=sdaccel-log

but error occurs.

...
INFO: Split DCP from xclbin: 18_08_26-072403-primary.bit
INFO: Split Metadata from xclbin: 18_08_26-072403-primary.bit
INFO: Generated manifest file '18_08_26-072403_manifest.txt'
upload failed: ./18_08_26-072403_Developer_SDAccel_Kernel.tar to s3://sdaccel-fpga/sdaccel-dcp/18_08_26-072403_Developer_SDAccel_Kernel.tar Could not connect to the endpoint URL: "https://sdaccel-fpga.s3.us-east-1c.amazonaws.com/sdaccel-dcp/18_08_26-072403_Developer_SDAccel_Kernel.tar?uploads"

I have S3 bucket and DCP and LOG sub-directory on S3.
Thanks.

@deeppat
Copy link
Contributor

deeppat commented Aug 28, 2018

@adki , I believe you have set your default region to us-east-1c which is why the cli can't reach the endpoint. Amazon API endpoints are not AZ specific, so you should set it to the region. For eg, you should set it to us-east-1 and try again.

@deeppat
Copy link
Contributor

deeppat commented Sep 4, 2018

Closing this issue as I believe my comment should solve the problem. Please post on the forum for any follow ups!

-Deep

@deeppat deeppat closed this as completed Sep 4, 2018
@yunqu
Copy link

yunqu commented Mar 6, 2020

I have seen similar issue. Did @adki solve this problem by the comment? I used the us-east-1 as region but still no luck.

@deeppat
Copy link
Contributor

deeppat commented Mar 6, 2020

@yunqu, could you share the specific error message you saw?

@yunqu
Copy link

yunqu commented Mar 6, 2020

I used the command:

./SDAccel/tools/create_sdaccel_afi.sh -xclbin=/home/centos/data/build/resizer.xclbin -o=resizer \
-s3_bucket=arn:aws:s3:us-east-1:186486331965:accesspoint/pynq-helloworld \
-s3_dcp_key=arn:aws:s3:us-east-1:186486331965:accesspoint/pynq-helloworld/dcps/ \
-s3_logs_key=arn:aws:s3:us-east-1:186486331965:accesspoint/pynq-helloworld/logs/

Then it errors out with:

upload failed: ./20_03_06-191234_Developer_SDAccel_Kernel.tar to s3://arn:aws:s3:us-east-1:186486331965:accesspoint/pynq-helloworld/arn:aws:s3:us-east-1:186486331965:accesspoint/pynq-helloworld/dcps//20_03_06-191234_Developer_SDAccel_Kernel.tar Could not connect to the endpoint URL: "https://pynq-helloworld/arn:aws:s3:us-east-1:186486331965:accesspoint/pynq-helloworld-186486331965.s3-accesspoint.us-east-1.amazonaws.com/pynq-helloworld%2Farn%3Aaws%3As3%3Aus-east-1%3A186486331965%3Aaccesspoint%2Fpynq-helloworld/dcps//20_03_06-191234_Developer_SDAccel_Kernel.tar?uploads"

@yunqu
Copy link

yunqu commented Mar 6, 2020

@deeppat Ok I got it. The correct command should be:

./SDAccel/tools/create_sdaccel_afi.sh -xclbin=/home/centos/data/build/resizer.xclbin -o=resizer \
-s3_bucket=arn:aws:s3:us-east-1:186486331965:accesspoint/pynq-helloworld \
-s3_dcp_key=dcps/ \
-s3_logs_key=logs/

The dcp and logs section should not repeat the access point ARN.

@deeppat
Copy link
Contributor

deeppat commented Mar 6, 2020

@yunqu That's correct. internally, the script just calls aws s3 cp and only expects the S3Uri for the s3 bucket argument. I'm glad it's all set for you. I'll see if we can update the script to better specify the requirements too.

kyyalama2 pushed a commit that referenced this issue May 24, 2022
* Adding a check to read description

* boolean instead of bool

* Echo if the sw_emu target exists

* Echo if the sw_emu target exists

* Added rtl_vadd_2clks

* Moving back the default test after testing that it works
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants