creating an AFI from cl_hello_world, axi_register_slice.v does not exist

0

Hello,

I was following the guide in https://github.com/aws/aws-fpga/blob/master/hdk/README.md to create an AFI from the hello_world CL example. After executing ./aws_build_dcp_from_cl.sh -notify -foreground, I received this errors:

.  
.  
.  
Phase 1 Generate And Synthesize Debug Cores  
  
INFO: \[IP_Flow 19-3806] Processing IP xilinx.com:ip:xsdbm:3.0 for cell xsdbm_CV.  
**ERROR**: \[Vivado 12-172]  **File or Directory '/home/centos/aws-fpga/hdk/common/shel                           l_v04261818/design/ip/axi_register_slice/sim/axi_register_slice.v' does not exist**                           t  
ERROR: \[IP_Flow 19-3805] Failed to generate and synthesize debug IPs.  
ERROR: \[Common 17-39] 'send_msg_id' failed due to earlier errors.  
Phase 1 Generate And Synthesize Debug Cores | Checksum: 273edc26d  
  
Time (s): cpu = 00:00:43 ; elapsed = 00:01:22 . Memory (MB): peak = 5774.426 ; gain = 3.996 ; free physical = 113112 ; free virtual = 135161  
INFO: \[Common 17-83] Releasing license: Implementation  
9 Infos, 2 Warnings, 0 Critical Warnings, and 3 Errors encountered.  
opt_design failed  

Is there any other way to create an AFI directly? Thank you in advance for your advice.

I have run the hdk_setup and, it has already passed.
HDK version: 1.4.19
FPGA Dev AMI: 1.6.1

Ajhonny
posta 3 anni fa247 visualizzazioni
11 Risposte
0
Risposta accettata

Hi

I have verified the flow with AMI 1.6.1 and hdk version 1.4.15a on F1.2x instance. Please see if you are able to follow the below steps/instructions and recreate the flow successfully

1.) On your F1.2x instance with 1.6.1AMI, start in a clean dir, say "new_dir"
2.) Inside the directory, do a git clone of 1.4.15a using
git clone https://github.com/aws/aws-fpga
cd aws-fpga
git checkout <tag> i.e., git checkout v1.4.15a
3.) Once you sync'd to v1.4.15a, cd to aws-fpga
4.) Update the supported_vivado_versions.txt file as recommended
5.) Now follow the instructions in https://github.com/aws/aws-fpga/blob/master/hdk/README.md
i.e., run source hdk_setup.sh
cd $HDK_DIR/cl/examples/cl_hello_world
export CL_DIR=$(pwd)
./aws_build_dcp_from_cl.sh
Once the tar file is generated, make buckets for dcp and logs and copy the files
create fpga image and wait till the state is available
Now source sdk_setup.sh from aws-fpga dir and clear the FPGA and load the image
cd $CL_DIR/software/runtime/
make all
sudo ./test_hello_world

Please let me know if the above steps work on your side.

The error you reported with 1.4.15a seem like something went wrong with repo cloning possibly. Can you specify the exact process you followed to sync your dev kit to 1.4.15a version before running source hdk_setup.sh.

Thanks
Kishore

AWS
con risposta 3 anni fa
0

Hi Ajhonny

Thank you so much for trying the cl_hello_world example and also contacting us for support. Thanks for providing us the error messages and the info. The file that is reported as missing in the error message is part of git repo https://github.com/aws/aws-fpga/tree/master/hdk/common/shell_v04261818/design/ip/axi_register_slice/sim

It looks like possibly something did not go well with git clone? Can you please confirm if you are able to see this file in the location referred to in your error message.
/home/centos/aws-fpga/hdk/common/shell_v04261818/design/ip/axi_register_slice/sim/axi_register_slice.v

Thanks
Kishore

AWS
con risposta 3 anni fa
0

Hi Kishore,

I don't think so, nothing unusual happened during cloning but, when I want to source the hdk_setup.sh, I got an error. (I asked about it in the forum too, here is the link https://forums.aws.amazon.com/message.jspa?messageID=985017#985017)

I can't see that file, and here is the list of files in /home/centos/aws-fpga/hdk/common/shell_v04261818/design/ip/axi_register_slice :
axi_register_slice.veo axi_register_slice.xci
axi_register_slice.vho axi_register_slice.xml

Thanks

Edited by: Ajhonny on May 28, 2021 9:36 AM

Ajhonny
con risposta 3 anni fa
0

Hi Ajhonny

Thanks for the reply. Thanks for the reference to the earlier thread. Yes, temporarily adding the tool version to the file should fix the problem regarding the vivado version support error. Related to the missing file error, can you please try git clone https://github.com/aws/aws-fpga.git in a clean dir and check if the file is still missing from the path
https://github.com/aws/aws-fpga/tree/master/hdk/common/shell_v04261818/design/ip/axi_register_slice/sim

Thanks
Kishore

AWS
con risposta 3 anni fa
0

No, the file does exist in the location.
So, should I remove the older one and clone a clean one and change the supported_vivado_versions.txt file again and follow the steps in the guide?
Also, here when I clone the git, I will receive the 1.4.19 version. How is it supposed to work with FPGA AMI 1.6.1 when it only supports HDK 1.4.8-1.4.15a releases?

Thanks for your help.
Ajhonny

Ajhonny
con risposta 3 anni fa
0

Hi

looks like you are currently using HDK 1.4.19 from the earlier comment. Is that correct?

Thanks
Kishore

Edited by: kishoreataws on May 28, 2021 10:48 AM

AWS
con risposta 3 anni fa
0

Hi

Yes, but I think I am not supposed to use HDK 1.4.19 since my FPGA AMI version is 1.6.1. (vivado 2018.3)

Thanks
Ajohnny

Ajhonny
con risposta 3 anni fa
0

Hi

Correct, we recommend using HDK versions as per https://github.com/aws/aws-fpga. As per the logs, looks like you are using HDK1.4.19.
And as part of 1.4.19, the file axi_register_slice.v is in /hdk/common/shell_v04261818/design/ip/axi_register_slice/sim

I also verified that the same file (axi_register_slice.v) should be present in the exact same location (hdk/common/shell_v04261818/design/ip/axi_register_slice/sim) in v1.4.15a.

So in either case, you should be able to find this file in the path referred to. But from your previous comments looks like you are not able to find this file. Is that correct?

In addition, you should be able to get v1.4.15a for running on AMI 1.6.1 using git checkout v1.4.15a. Please let me know if this helps.

Are you still seeing File or Directory '/home/centos/aws-fpga/hdk/common/shel l_v04261818/design/ip/axi_register_slice/sim/axi_register_slice.v' does not exist error while you can see that this file exists in the path referred to manually?

Thanks
Kishore

AWS
con risposta 3 anni fa
0

Hi

Yes, that is correct.

I couldn't see the axi_register_slice.v file and even 'sim' directory doesn't exist in the /home/centos/aws-fpga/hdk/common/shel l_v04261818/design/ip/axi_register_slice, but now, I can see this file and the directory in the new cloned one.

I tried to download the 1.4.15a from https://github.com/aws/aws-fpga/releases, but even when I added the version in the supported_vivado_versions.txt, I still got this error after executing hdk_setup.sh (here I tried hdk 1.4.15 on another instance):
INFO: HDK shell is up-to-date
INFO: HDK shell is up-to-date
INFO: HDK shell is up-to-date
INFO: DDR4 model files in /home/centos/aws-fpga-1.4.15a/hdk/common/verif/models/ddr4_model/ do NOT exist. Running model creation step.
INFO: Building in /home/centos/aws-fpga-1.4.15a/hdk/common/verif/scripts
INFO: This could take 5-10 minutes, please be patient!
fatal: Not a git repository (or any of the parent directories): .git
make: *** [/home/centos/aws-fpga-1.4.15a/hdk/common/verif/scripts/.done] Error 128
ERROR: build dir=/home/centos/aws-fpga-1.4.15a/hdk/common/verif/scripts/tmp

Thanks,
Ajhonny

Edited by: Ajhonny on May 28, 2021 12:01 PM

Ajhonny
con risposta 3 anni fa
0

Hi,

Thank you for your thorough instruction. I followed it and, it worked.

For the v1.4.19, I only did "git clone https://github.com/aws/aws-fpga" and followed the guide. (I don't know what was the problem in this case) But for the v1.4.15a, I didn't use 'git checkout' and downloaded the files with 'wget' and, I should've done it as you said.

Best,
Ajhonny

Edited by: Ajhonny on May 30, 2021 1:21 PM

Ajhonny
con risposta 3 anni fa
0

I am glad that the instructions helped. Please feel free to contact us if you need any additional help from aws.

Thanks
Kishore

AWS
con risposta 3 anni fa

Accesso non effettuato. Accedi per postare una risposta.

Una buona risposta soddisfa chiaramente la domanda, fornisce un feedback costruttivo e incoraggia la crescita professionale del richiedente.

Linee guida per rispondere alle domande