Skip to content

Latest commit

 

History

History
54 lines (30 loc) · 2.4 KB

README.md

File metadata and controls

54 lines (30 loc) · 2.4 KB
Raw

Starting your own Custom Logic

1. Make sure you have the FPGA HDK installed and the environment variables set up

In case you haven't cloned AWS FPGA HDK+SDK, please follow the next steps to download and configure the HDK to the source directory on the instance:

$ git clone https://github.com/aws/aws-fpga
$ cd aws-fpga
$ source hdk_shell.sh

2. Create a new CL directory, environment variable, and reference directory structure

The developer has two ways to start a new Custom Logic design:

  1. Copy one of the example directory from $HDK_DIR/cl/examples, and make sure to set up $CL_DIR environment variable to point to the new design

  2. Setup a new CL directory:

    $ mkdir Your_New_CL_Directory $ cd Your_New_CL_Directory $ export CL_DIR=$(pwd) $ source $HDK_DIR/cl/developer_designs/prepare_new_cl.sh

Setting up the $CL_DIR environment variable is crucial as the build scripts rely on that value.

The prepare_new_cl.sh would set up the directory structure to match what's expected by the HDK simulation and build scripts. Execute source $HDK_DIR/cl/developer_designs/prepare_new_cl.sh from within the directory you want to use for your CL development.

In both cases, double check that the $CL_DIR is set correctly by calling and checking the result of:

$ echo $CL_DIR

3. Modify the build scripts

The following scripts should be modified before starting the build:

  • /build/constraints/* to set all the timing, clock and placement constraints.
  • /build/scripts/encrypt.tcl to set the source file names before encryption.
  • /build/scripts/create_dcp_from_cl.tcl to update the final build scripts with right source files and IP.

Once your design is ready and you would like to start the build/create process, please refer to this checklist.

NOTE: The DCP generation can take up to several hours to complete. We recommend that you initiate the generation in a way that prevents interruption. For example, if working on a remote machine, we recommend using window management tools such as screen to mitigate potential network disconnects.

Once you verified the checklist, you can run:

$ ./aws_build_dcp_from_cl.tcl

NOTE A detailed walkthrough on how to build the CL is also available in $CL_DIR/build/scripts/README.md.