Skip to content

Update README.md #106

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
AWSwinefred merged 1 commit into from
Feb 22, 2017
Merged

Update README.md #106

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions hdk/cl/examples/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -65,12 +65,12 @@ If you like to start your own CL, check out the [How to create your own CL](../d

$ vivado -mode batch # Verify Vivado is installed.

Executing the `aws_build_dcp_from_cl.tcl` script will perform the entire implementation process converting the CL design into a completed Design Checkpoint that meets timing and placement constrains of the target FPGA.
Executing the `aws_build_dcp_from_cl.sh` script will perform the entire implementation process converting the CL design into a completed Design Checkpoint that meets timing and placement constrains of the target FPGA.
The output is a tarball file comprising the DCP file, and other log/manifest files, formatted as `YY_MM_DD-hhmm.Developer_CL.tar`.
This file would be submitted to AWS to create an AFI.

$ cd $CL_DIR/build/scripts
$ ./aws_build_dcp_from_cl.tcl
$ ./aws_build_dcp_from_cl.sh

**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.
Expand Down