FPGA HW linker Error

Hi,

Looks like the "markdown format" corrupted the logs you pasted into the post. Could you please attach and send the full log file? This will help us to better understand the issue.

Just FYI --

• You can setup a GUI environment on your F1 instance using NICE DCV:
  https://github.com/aws/aws-fpga/blob/master/developer_resources/DCV.md

• It is possible to launch vivado in "-mode tcl" and use the TCL commands to upgrade IP and generate output products. Please see descriptions for "upgrade_ip" and "generate_target" in :
  https://www.xilinx.com/support/documentation/sw_manuals/xilinx2019_2/ug835-vivado-tcl-commands.pdf

thanks!
Chakra

Edited by: awschakra on Oct 9, 2020 7:54 AM

Thanks a lot for the quick reply..
attachment is the vivado log--can you check and give some suggestion, please?

Looking at the log, the mismatch and IP locking messaging is due to version, the IP was used with 2019.2, however AWS applies the AR73068 patch to its build. This is done automatically when using the appropriate setup script on the Github page. The two specific IP that are locked are:

WARNING: [BD 41-1661] One or more IPs have been locked in the design 'cl.bd'. Please run report_ip_status for more details and recommendations on how to fix this issue.
List of locked IPs:
cl_HIP_0
cl_aws_0_0

The HIP IP core is the one giving the error messaging. Could you make sure that your original design is being built with the appropriate version of 2019.2 that AWS uses (2019.2_AR73068)? I would suggest using the setup scripts to make sure the AWS environment is setup on your local machine.

I log into Vivado project by using -mode tcl, and run report_ip_status as suggested,
from the report, I did not see issues (both two IPs are Up-to-date).

Could you make sure that your original design is being built with the appropriate version of 2019.2 that AWS uses (2019.2_AR73068)? I would suggest using the setup scripts to make sure the AWS environment is setup on your local machine.

--> my project is originally built by using Vitis 2019.2.1 on my local computer -- do you mean I shall revert my vitis back to 2019.2?

Project IP Instances
------------------------------------------------------------------------------------------------------------------------------------------------------------
| Instance Name | Status | Recommendation | Change | IP Name | IP | New Version | New | Original Part |
| | | | Log | | Version | | License | |
------------------------------------------------------------------------------------------------------------------------------------------------------------
| cl_HIP_0 | Up-to-date | No changes required | Change | SDx Memory | 1.0 | 1.0 (Rev. 5) | Included | xcvu9p-flgb2104-2-i |
| | | | Log not | Subsystem | (Rev. | | | |
| | | | available | | 5) | | | |
------------------------------------------------------------------------------------------------------------------------------------------------------------
| cl_aws_0_0 | Up-to-date | No changes required | *(1) | AWS | 1.0 | 1.0 (Rev. 3) | Included | xcvu9p-flgb2104-2-i |
| | | | | | (Rev. | | | |
| | | | | | 3) | | | |

Finally, I revert back the AWS from 1.4.15 to 1.4.14, redo all the setup, then I can run my build..
This is much faster then make another Vitis version etc..