You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: FAQs.md
+3-8
Original file line number
Diff line number
Diff line change
@@ -460,14 +460,9 @@ Parent process (pid 8160) has died. This helper process will now exit
460
460
461
461
You would need a valid [on premise license](./hdk/docs/on_premise_licensing_help.md) provided by Xilinx.
462
462
463
-
*For runs using the FPGA Developer AMI:*
464
-
465
-
**NOTE:**
466
-
> * The license included on FPGA Developer AMI Versions 1.3.0_a and earlier expires on October 31 2017.
467
-
> * If you see the above error, please update to FPGA Developer AMI Version 1.3.3 or later.
468
-
> * All FPGA Developer AMI Versions 1.3.0_a and earlier will be deprecated once Version 1.3.3 is released.
469
-
> * 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`
470
-
> * If you still face the above error, please contact us on the forums and we'd be happy to help further.
463
+
*For runs using the FPGA Developer AMI:* Please contact us through [AWS FPGA Developers forum](https://forums.aws.amazon.com/forum.jspa?forumID=243)
464
+
465
+
471
466
472
467
**Q: Why does Vivado in GUI mode show up blank ? or Why does Vivado in GUI mode show up as an empty window?**
*[FPGA Libraries](sdk/userspace/fpga_libs) - APIs used by C/C++ host applications.
146
145
*[FPGA Management Tools](sdk/userspace/fpga_mgmt_tools/README.md) - AFI management APIs for runtime loading/clearing FPGA image, gathering metrics and debug interface on the F1 instance.
@@ -93,7 +124,7 @@ Look for the ./hdk/hdk_version.txt file.
93
124
94
125
**Q: How do I know what my Shell version is? **
95
126
96
-
The Shell version of an FPGA slot is available through the FPGA Image Management tools. See the description of `fpga-describe-local-image` for more details on retrieving the shell version from a slot.
127
+
The Shell version of an FPGA slot is available through the FPGA Image Management tools after an AFI has been loaded. See the description of `fpga-describe-local-image` for more details on retrieving the shell version from a slot. Prior to loading an AFI, the state of the FPGA (including shell version) is undefined and non-deterministic.
97
128
98
129
**Q: How do I know what version of FPGA Image management tools are running on my instance? **
Copy file name to clipboardExpand all lines: SDAccel/README.md
+3-10
Original file line number
Diff line number
Diff line change
@@ -125,6 +125,8 @@ The instructions below describe how to build the Xilinx FPGA Binary and host app
125
125
$ make TARGETS=hw DEVICES=$AWS_PLATFORM all
126
126
```
127
127
128
+
NOTE: If you encounter an error with `No current synthesis run set`, you may have previously run the [HDK IPI examples](../hdk/docs/IPI_GUI_Vivado_Setup.md) and created a `Vivado_init.tcl` file in `~/.Xilinx/Vivado`. This will cause [problems](https://forums.aws.amazon.com/thread.jspa?threadID=268202&tstart=25) with the build process, thus it is recommended to remove it before starting a hardware system build.
129
+
128
130
Now that you have built your Xilinx FPGA binary, see [SDAccel Power Analysis Guide](./docs/SDAccel_Power_Analysis.md) for more details on how to analyze power for your binary.
129
131
130
132
<aname="createafi"></a>
@@ -209,20 +211,11 @@ Here are the steps:
209
211
* Ensure the host application can find and load the \*.awsxclbin AWS FPGA binary file.
210
212
211
213
* Source the Runtime Environment & Execute your Host Application
212
-
* Xilinx SDx 2017.4:
213
-
```
214
-
$ sudo sh
215
-
# source /opt/Xilinx/SDx/2017.4.rte.dyn/setup.sh # Other runtime env settings needed by the host app should be setup after this step
216
-
# ./helloworld
217
-
```
218
-
219
-
* Xilinx SDx 2018.2:
220
214
```
221
215
$ sudo sh
222
-
# source /opt/xilinx/xrt/setup.sh # Other runtime env settings needed by the host app should be setup after this step
216
+
# source $AWS_FPGA_REPO_DIR/sdaccel_runtime_setup.sh # Other runtime env settings needed by the host app should be setup after this step
Copy file name to clipboardExpand all lines: SDAccel/docs/Create_Runtime_AMI.md
+28-10
Original file line number
Diff line number
Diff line change
@@ -51,25 +51,43 @@
51
51
52
52
## 2. Copy required Xilinx SDAccel Runtime Libraries to the Instance and Reboot your Runtime Instance.
53
53
54
-
* Using an instance running [FPGA Developer AMI](https://aws.amazon.com/marketplace/pp/B06VVYBLZZ) or an on-premises machine with access to a Xilinx SDAccel Tools Installation, run the following:
54
+
* Using an instance running [FPGA Developer AMI](https://aws.amazon.com/marketplace/pp/B06VVYBLZZ) or an on-premises machine with access to a Xilinx SDAccel Tools Installation, first source $AWS_FPGA_REPO_DIR/sdaccel_setup.sh and then run following commands:
55
+
56
+
* if using Ubuntu or debian distribution set GLIBPATH env variable to Ubuntu. If using any other OS distribution set GLIBPATH to default.
57
+
58
+
* set env variable 'XLNXRTE' to intended runtime install directory path.
* You may need to update path in $XLNXRTE/setup.sh and $XLNXRTE/setup.csh script to match your runtime instance.
79
+
* Copy $XLNXRTE directory created to $HOME on your Runtime Instance.
64
80
65
-
* Copy xlnxrte directory created to $HOME on your Runtime Instance.
66
-
81
+
### **For Vivado SDX 2018.2**
67
82
83
+
please refer to [Installing the Xilinx Runtime](https://www.xilinx.com/html_docs/xilinx2018_2_xdf/sdaccel_doc/ejy1538090924727.html) for instructions on how to install runtime on your AMI.
84
+
85
+
68
86
## 3. Install Runtime Drivers and run your FPGA accelerated application on your Runtime Instance.
69
87
* Log back on to the Runtime Instance:
70
88
71
89
```
72
-
$ export XILINX_SDX=$HOME/xlnxrte
90
+
$ export XILINX_SDX=$HOME/$XLNXRTE
73
91
````
74
92
* You should be able to [run your FPGA accelerated application as described here](https://github.com/aws/aws-fpga/tree/master/SDAccel#runonf1), without needing to launch a new F1 instance
0 commit comments