Skip to content

Commit 787a394

Browse files
committed
v1.3.3 doc updates
1 parent e774084 commit 787a394

File tree

2 files changed

+32
-2
lines changed

2 files changed

+32
-2
lines changed

FAQs.md

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -104,16 +104,19 @@ It is the compiled FPGA code that is loaded into an FPGA in AWS for performing t
104104

105105
The developer can create multiple AFIs at no extra cost, up to a defined limited (typically 100 AFIs per region per AWS account). An AFI can be loaded into as many FPGAs as needed.
106106

107+
107108
**Q: What regions are supported?**
108109

109110
AWS FPGA generation and EC2 F1 instances are supported in us-east-1 (N. Virginia), us-west-2 (Oregon) and ue-west-1 (Ireland).
110111

112+
111113
**Q: What is the process for creating an AFI?**
112114

113115
The AFI process starts by creating Custom Logic (CL) code that conforms to the [Shell Specification]((./hdk/docs/AWS_Shell_Interface_Specification.md). Then, the CL must be compiled using the HDK scripts which leverages Vivado tools to create a Design Checkpoint (DCP). That DCP is submitted to AWS for generating an AFI using the `aws ec2 create-fpga-image` API.
114116

115117
Use the AWS CLI `describe-fpga-images` API to get information about the created AFIs using the AFI ID provided by `create-fpga-image`, or to list available AFIs for your account. See [describe-fpga-images](./hdk/docs/describe_fpga_images.md) document for details on how to use this API.
116118

119+
117120
**Q: Can I load an AFI on every region AWS FPGA is supported?**
118121

119122
Yes, but you must first copy the AFI using the [copy-fpga-image](./hdk/docs/copy_fpga_image.md) API. You should generate AFIs in one region and use copy to make them available in other regions. Copy preserves the Global AFI ID used to load an AFI on a EC2 instance.
@@ -225,6 +228,19 @@ To be able to manage and monitor the F1 FPGAs it is required to install the [FPG
225228

226229
Typically, you will not need the HDK nor any Xilinx Vivado tools on an F1 instance that is using prebuilt AFIs; unless, you want to do in-field debug using Vivado's ChipScope (Virtual JTAG).
227230

231+
**Q: How do I update the AWS CLI to use the latest EC2 commands to manage my AFI's?**
232+
233+
On the FPGA Developer AMI, you can update your AWS CLI for all users using the command:
234+
```
235+
sudo pip install awscli --upgrade
236+
```
237+
238+
If You want to upgrade the AWS CLI for just your user, you can run the following:
239+
```
240+
pip install awscli --upgrade --user
241+
```
242+
The AWS CLI [documentation page](http://docs.aws.amazon.com/cli/latest/userguide/installing.html) shows steps to update the AWS CLI.
243+
We recommend using the latest available version to be able to use the expanding list of commands that we add.
228244

229245
## Marketplace
230246
**Q: What does publishing my AFI/AMI to AWS Marketplace enables?**
@@ -418,4 +434,18 @@ elapsed = 00:08:59 . Memory (MB): peak = 4032.184 ; gain = 3031.297 ; free physi
418434
/opt/Xilinx/Vivado/2016.3/bin/loader: line 164: 8160 Killed "$RDI_PROG" "$@"
419435
Parent process (pid 8160) has died. This helper process will now exit
420436

437+
**Q: Why am I getting an error: `A valid license was not found for feature 'XYZ' and/or device 'XYZ'` from Xilinx Vivado while trying to build by dcp/running my examples?**
438+
439+
*For On Premise runs:*
440+
441+
You would need a valid [on premise license](./hdk/docs/on_premise_licensing_help.md) provided by Xilinx.
442+
443+
*For runs using the FPGA Developer AMI:*
444+
445+
**NOTE:**
446+
> * The license included on FPGA Developer AMI Versions 1.3.0_a and earlier expires on October 31 2017.
447+
> * If you see the above error, please update to FPGA Developer AMI Version 1.3.3 or later.
448+
> * All FPGA Developer AMI Versions 1.3.0_a and earlier will be deprecated once Version 1.3.3 is released.
421449
450+
* If you are using the FPGA Developer AMI Version 1.3.3 or later, please check if the environment variable `XILINXD_LICENSE_FILE` is set to `/opt/Xilinx/license/XilinxAWS.lic`
451+
* If you still face the above error, please contact us on the forums and we'd be happy to help further.

hdk/docs/on_premise_licensing_help.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11

22
# Enabling on-premises development with Xilinx tools
33

4-
**NOTE: If you are developing on AWS cloud and using AWS FPGA Developer AMI provided on AWS Marketplace, you can skip this document.**
4+
**NOTE: If you are developing on the AWS cloud and using AWS FPGA Developer AMI provided on AWS Marketplace, you can skip this document.**
55

66
This document helps developers who choose to develop on-premises with specifying and licensing AWS-compatible Xilinx tools for use with the AWS FPGA HDK.
77

@@ -15,7 +15,7 @@ This document helps developers who choose to develop on-premises with specifying
1515

1616
* On-Premises customers may need a new or updated license
1717
* Existing F1 on-premises customers will not need a new license
18-
* New users will need to obtain an on-premises license of Vivado, please follow instruction at: https://www.xilinx.com/products/design-tools/acceleration-zone/ef-vivado-sdx-vu9p-op-fl-nl.html
18+
* New users will need to obtain an on-premises license of Vivado, please follow the instructions at: https://www.xilinx.com/products/design-tools/acceleration-zone/ef-vivado-sdx-vu9p-op-fl-nl.html
1919
* The correct ordering number for the product is EF-VIVADO-SDX-VU9P-OP-(NL/FL)
2020
* You can confirm you are using the correct license for this product by ensuring you have the following in Xilinx License Manager:
2121
* EncryptedWriter_v2

0 commit comments

Comments
 (0)