Skip to content

Commit 49e22b8

Browse files
authored
Update ERRATA.md
1 parent 632eab1 commit 49e22b8

File tree

1 file changed

+7
-18
lines changed

1 file changed

+7
-18
lines changed

ERRATA.md

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

22
# AWS EC2 FPGA HDK+SDK Errata
33

4-
## Release 1.2.1
4+
## Release 1.3.0
55

6-
Any items in this release marked as WIP (Work-in-progress) or NA (Not avaiable yet) are not currently supported by the 1.2.0 release.
7-
8-
## Integrated DMA in Beta Release. AWS Shell now includes DMA capabilities on behalf of the CL
9-
* The DMA bus toward the CL is multiplexed over sh_cl_dma_pcis AXI4 interface so the same address space can be accessed via DMA or directly via PCIe AppPF BAR4
10-
* DMA usage is covered in the new [CL_DRAM_DMA example](./hdk/cl/examples/cl_dram_dma) RTL verification/simulation and Software
11-
* A corresponding AWS Elastic DMA ([EDMA](./sdk/linux_kernel_drivers/edma)) driver is provided.
12-
* [EDMA Installation Readme](./sdk/linux_kernel_drivers/edma/edma_install.md) provides installation and usage guidlines
13-
* The initial release supports a single queue in each direction
14-
* DMA support is in Beta stage with a known issue for DMA READ transactions that cross 4K address boundaries. See [Kernel_Drivers_README](./sdk/linux_kernel_drivers/edma/README.md) for more information on restrictions for this releas
15-
16-
## Implementation Restrictions
6+
### Preview Only (temporary) Restrictions (as of 6/27) - Features not currently supported:
7+
* CL examples: simulation and runtime
8+
* Chipscope
9+
* create-fpga-image
10+
* F1 Runtime
1711

12+
### Implementation Restrictions
1813
* PCIE AXI4 interfaces between Custom Logic(CL) and Shell(SH) have following restrictions:
1914
* All PCIe transactions must adhere to the PCIe Exress base spec
2015
* 4Kbyte Address boundary for all transactions(PCIe restriction)
@@ -26,8 +21,6 @@ Any items in this release marked as WIP (Work-in-progress) or NA (Not avaiable y
2621
* AXI lock, memory type, protection type, Quality of service and Region identifier are not supported
2722

2823
## Unsupported Features (Planned for future releases)
29-
30-
* PCI-M AXI interface is not supported in this release.
3124
* FPGA to FPGA communication over PCIe for F1.16xl
3225
* FPGA to FPGA over the 400Gbps Ring for F1.16xl
3326
* Aurora and Reliabile Aurora modules for the FPGA-to-FPGA
@@ -37,8 +30,4 @@ Any items in this release marked as WIP (Work-in-progress) or NA (Not avaiable y
3730

3831
## Known Bugs/Issues
3932

40-
* The PCI-M AXI interface is not supported in this release. The interface is included in cl_ports.vh and required in a CL design, but not enabled for functional use in this release.
41-
42-
* The integrated DMA function is in Beta stage. There is a known issue with DMA READ addresses crossing 4K page boundaries. The failure can be triggered by READ transfers that start on an address other than 4K aligned AND cross the 4K page boundary. READ transfers that do not cross the 4K boundary OR transfers that start at the beginning of a 4K page and greater than 4K size are not susceptible to the error. WRITE transfers are not affected by this issue Developers should use 4K aligned address boundaries on any READ transfer that can cross a 4K boundary to avoid the issue. Additionally CL designs synthesized to 125Mhz or greater should limit DMA transaction sizes to 16KB or less.
4333

44-
* aws_dcp_verify flow (aws_dcp_verify.tcl) does not work. The script will be fixed in a future release. Currently the script will always give an error even if the DCP is OK.

0 commit comments

Comments
 (0)