v1.3.4 release (#373)

* v1.3.4 release

* release notes updates for v1.3.4

* Test sdaccel builds by default

* Update RELEASE_NOTES.md

* Update RELEASE_NOTES.md

Author: kristopk

.gitignore

@@ -41,6 +41,35 @@ nohup.out
 # Shell DCP files are stored in S3 and downloaded by hdk_setup.sh
 hdk/common/shell_*/build/checkpoints/from_aws/SH_CL_BB_routed.dcp*
 
+# HDK generated files
+hdk/cl/examples/*/build/create-afi/
+hdk/cl/examples/*/build/scripts/.srcs/
+hdk/cl/examples/*/software/runtime/sh_dpi_tasks
+hdk/cl/examples/cl_hello_world/software/runtime/test_hello_world
+hdk/cl/examples/cl_hello_world_vhdl/software/runtime/test_hello_world_vhdl
+hdk/cl/examples/cl_hello_world_vhdl/software/runtime/test_hello_world_vhdl
+hdk/cl/examples/cl_uram_example/software/runtime/test_uram_example
+hdk/cl_uram_example/software/runtime/test_uram_example
+hdk/common/shell_*/build/debug_probes/
+hdk/common/verif/models/sh_bfm/cl_ports_sh_bfm.vh
+
+# SDAccel generated files
+SDAccel/**/*.d
+SDAccel/**/*.o.cmd
+SDAccel/aws_platform/xilinx_aws-*/hw/xilinx_aws-vu9p-*.dsa*
+SDAccel/tools/*.d
+SDAccel/tools/*.o
+SDAccel/tools/xbsak
+
+# SDK generated files
+sdk/linux_kernel_drivers/edma/.*.o.cmd
+sdk/linux_kernel_drivers/edma/.*.ko.cmd
+sdk/linux_kernel_drivers/edma/.tmp_versions
+sdk/linux_kernel_drivers/xdma/.*.o.cmd
+sdk/linux_kernel_drivers/xdma/.*.ko.cmd
+sdk/linux_kernel_drivers/xdma/.tmp_versions
+sdk/userspace/lib/
+
 # Generated checkpoints
 checkpoints
 
@@ -56,5 +85,13 @@ vivado*.log
 # Pycharm projects
 .idea/
 
+# Eclipse projects
+.project
+.pydevproject
+.settings
+
 # Python compiled code
-*.pyc
+*.pyc
+
+# pytest artifacts
+.cache/

FAQs.md

@@ -139,7 +139,7 @@ Use [delete-fpga-image](./hdk/docs/delete_fpga_image.md) carefully. Once all AFI
 
 **Q: Can I bring my own bitstream for loading on an F1 FPGA?**
 
-No. There is no mechanism for loading a bitstream directly onto the FPGAs of an F1 instance. All Custom Logic is loaded onto the FPGA by calling `$ fpga-local-load-image` tool at [AWS FPGA SDK](https://github.com/aws/aws-fpga/sdk). 
+No. There is no mechanism for loading a bitstream directly onto the FPGAs of an F1 instance. All Custom Logic is loaded onto the FPGA by calling `$ fpga-local-load-image` tool at [AWS FPGA SDK](./sdk). 
 
 Developers create an AFI by creating a Vivado Design Checkpoint (DCP) and submitting that DCP to AWS using `aws ec2 create-fpga-image` API. AWS creates the AFI and bitstream from that DCP and returns a unique AFI ID referencing that AFI.
 
@@ -211,7 +211,7 @@ Yes, examples are in the [examples directory](./hdk/cl/examples):
 
 The [cl_hello_world example](./hdk/cl/examples/cl_hello_world) is an RTL/Verilog simple example to build and test the Custom Logic development process, it does not use any of the external interfaces of the FPGA except the PCIe to "peek" and "poke" registers in the memory space of the CL inside the FPGA.
 
-The [cl_dram_dma example](.hdk/cl/examples/cl_dram_dma) provides expanded features that demonstrates the use and connectivity for many of the Shell/CL interfaces and functionality.
+The [cl_dram_dma example](./hdk/cl/examples/cl_dram_dma) provides expanded features that demonstrates the use and connectivity for many of the Shell/CL interfaces and functionality.
 
 
 **Q: How do I get access to AWS FPGA Developer AMI?**
@@ -288,7 +288,7 @@ Both. The FPGA PCIe memory address space can be mmap() to both kernel and usersp
 
 **Q: How do I change what AFI is loaded in an FPGA?**
 
-Changing the AFI loaded in an FPGA is done using the `fpga-clear-local-image` and `fpga-load-local-image` APIs from the [FPGA Image Management tools](./sdk/userspace/fpga_mgmt_tools). Note that to ensure your AFI is loaded to a consistent state, a loaded FPGA slot must be cleared with `fpga-clear-local-image` before loading another FPGA image.  The `fpga-load-local-image` command takes the AFI ID and requests it to be programmed into the identified FPGA. The AWS infrastructure manages the actual FPGA image and programming of the FPGA using Partial Reconfiguration capabilities of the FPGA. The AFI image is not stored in the F1 instance nor AMI. The AFI image can’t be read or modified by the instance as there isn't a direct access to programming the FPGA from the instance. A user may call `fpga-load-local-image` at any time during the life of an instance, and may call `fpga-load-local-image` any number of times.
+Changing the AFI loaded in an FPGA is done using the `fpga-clear-local-image` and `fpga-load-local-image` APIs from the [FPGA Image Management tools](./sdk/userspace/fpga_mgmt_tools). The `fpga-load-local-image` command takes the AFI ID and requests it to be programmed into the identified FPGA. The AWS infrastructure manages the actual FPGA image and programming of the FPGA using Partial Reconfiguration capabilities of the FPGA. The AFI image is not stored in the F1 instance nor AMI. The AFI image can’t be read or modified by the instance as there isn't a direct access to programming the FPGA from the instance. A user may call `fpga-load-local-image` at any time during the life of an instance, and may call `fpga-load-local-image` any number of times.
 
 
 
@@ -446,6 +446,10 @@ You would need a valid [on premise license](./hdk/docs/on_premise_licensing_help
 >    * The license included on FPGA Developer AMI Versions 1.3.0_a and earlier expires on October 31 2017.
 >    * If you see the above error, please update to FPGA Developer AMI Version 1.3.3 or later.
 >    * All FPGA Developer AMI Versions 1.3.0_a and earlier will be deprecated once Version 1.3.3 is released.
+>    * 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`
+>    * If you still face the above error, please contact us on the forums and we'd be happy to help further.
 
-* 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`
-* If you still face the above error, please contact us on the forums and we'd be happy to help further.
+**Q: Why does Vivado in GUI mode show up blank ? or Why does Vivado in GUI mode show up as an empty window?**
+
+We have seen this issue when running RDP in 32 bit color mode where Vivado shows up as a blank window.
+Please modify RDP options to choose any color depth less than 32 bit and try re-connecting.