Custom CL Build Strategy

Question

Hello,  
  
The build strategy used in the flow should be mentioned in the manifest sent to AFI generation. currently there are 5 strategies (DEFAULT/BASIC/EXPLORE/TIMING/CONGESTION).  
  
Is the developer allowed to use a custom strategy (or – a custom set of steps and options/primitives per each vivado step), or is it a must to use explicitly one of the AWS-provided strategies that have been described above?  
  
Thanks,

Answer

Hi,  
  
The AWS Manifest file does not contain any build strategy information. For AFI generation, you will only need to upload a tarball that contains the final DCP and a manifest file.   
  
The build strategies (DEFAULT/BASIC/EXPLORE/TIMING/CONGESTION) provided in AWS build scripts are for convenience only. Customer may choose to build CL designs using different strategies, or modify the AWS build scripts with directives supported by Vivado. As long as your CL design adheres to Shell Interface Specification, (https://github.com/aws/aws-fpga/blob/master/hdk/docs/AWS_Shell_Interface_Specification.md#aws-shell-interface-specification) the AFI generation should be successful.   
  
Please feel free to contact us if you run into any issues.   
  
Thanks!  
Chakra

Answer

Thanks!

Custom CL Build Strategy

Contenido relevante