fpga-load-local-image produces "(12) cl-id-mismatch"

I'm in no way employed in Xilinx or AWS, so this is just my opinion, but I'd suggest you to check the VENDOR_ID and DEVICE_ID parameters in your design (on F1 instance).

These values are what's working for me, so you might want to try with those:
set_property -dict [list CONFIG.VENDOR_ID {0x1D0F}\
CONFIG.DEVICE_ID {0xF000}\
CONFIG.SUBSYSTEM_VENDOR_ID {0xFEDD}\
CONFIG.SUBSYSTEM_ID {0x1D51}]

Good luck!

Edited by: jelicicm on Jan 13, 2021 11:49 AM

Edited by: jelicicm on Jan 13, 2021 11:49 AM

Hi,

This looks like the Device ID/Vendor ID listed in the manifest file (*.manifest.txt generated as part of build process) is different than what is used by your CL design (cl_sh_id0, cl_sh_id1).

AWS performs integrity check by comparing the ID values in design with the one in manifest:
https://github.com/aws/aws-fpga/blob/master/hdk/docs/AWS_Shell_Interface_Specification.md#integrity-check

The manifest is generated by a script which parses $CL_DIR/design/cl_id_defines.vh for Device ID and Vendor IDs… But if customer hardcodes different IDs in their CL top level (by tying off cl_sh_id0, cl_sh_id1 ports) then the IDs in manifest and CL design will differ. This can result in ID mismatch error.

Script parses device and vendor IDs here:
https://github.com/aws/aws-fpga/blob/master/hdk/common/shell_v04261818/build/scripts/aws_build_dcp_from_cl.sh#L236

Example cl_id_defines.vh:
https://github.com/aws/aws-fpga/blob/master/hdk/cl/examples/cl_dram_dma/design/cl_id_defines.vh

Solution:

1. Please update your $CL_DIR/design/cl_id_defines.vh with desired IDs.
2. Ensure cl_sh_id0, cl_sh_id1 ports are using correct IDs.
3. Ensure IDs in manifest file match with IDs used in the design.

Thanks!
Chakra