Skip to content

Commit 28ce2a1

Browse files
authored
Merge pull request #49 from aws/kristopk-patch-3
Errata updates
2 parents 42c5627 + ec996a0 commit 28ce2a1

File tree

2 files changed

+56
-1
lines changed

2 files changed

+56
-1
lines changed

ERRATA.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,6 +43,7 @@ Any items in this release marked as WIP (Work-in-progress) or NA (Not avaiable y
4343

4444
* The integrated DMA function is in Beta stage. Known issues:
4545
* 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.
46-
* Integrated DMA with large transfer sizes (16KB or greater) can cause timeouts between the Shell and CL if the Shell can’t respond with all data before the timeout. Transfer sizes of 8KB or less are supported with the integrated DMA engine for this revision of the Shell. Shell-CL interface timeouts can be detected by checking metrics using this command: `sudo fpga-describe-local-image -S 0 -M`
46+
* Transfer sizes of 8KB or less are supported with the integrated DMA engine for this revision of the Shell. Integrated DMA with large transfer sizes (16KB or greater) can cause timeouts between the Shell and CL if the Shell can’t respond with all data before the timeout. Please see documentation on how to [detect a timeout has occured](./hdk/docs/HOWTO_detect_shell_timeout.md)
47+
4748

4849

Lines changed: 54 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,54 @@
1+
2+
# How to detect a shell timeout has occured
3+
4+
* Shell-CL interface timeouts can be detected by checking for non-zero timeout counters. These metrics can be read using this command:
5+
```
6+
$sudo fpga-describe-local-image -S 0 -M
7+
AFI 0 agfi-0f0e045f919413242 loaded 0 ok 0 0x04151701
8+
AFIDEVICE 0 0x1d0f 0xf000 0000:00:1d.0
9+
sdacl-slave-timeout=0
10+
virtual-jtag-slave-timeout=0
11+
ocl-slave-timeout=0
12+
bar1-slave-timeout=0
13+
dma-pcis-timeout=0
14+
pcim-range-error=0
15+
pcim-axi-protocol-error=0
16+
pcim-axi-protocol-4K-cross-error=0
17+
pcim-axi-protocol-bus-master-enable-error=0
18+
pcim-axi-protocol-request-size-error=0
19+
pcim-axi-protocol-write-incomplete-error=0
20+
pcim-axi-protocol-first-byte-enable-error=0
21+
pcim-axi-protocol-last-byte-enable-error=0
22+
pcim-axi-protocol-bready-error=0
23+
pcim-axi-protocol-rready-error=0
24+
pcim-axi-protocol-wchannel-error=0
25+
sdacl-slave-timeout-addr=0x0
26+
sdacl-slave-timeout-count=0
27+
virtual-jtag-slave-timeout-addr=0x0
28+
virtual-jtag-slave-timeout-count=0
29+
ocl-slave-timeout-addr=0x8001
30+
ocl-slave-timeout-count=0
31+
bar1-slave-timeout-addr=0x2001
32+
bar1-slave-timeout-count=0
33+
dma-pcis-timeout-addr=0x0
34+
dma-pcis-timeout-count=0
35+
pcim-range-error-addr=0x0
36+
pcim-range-error-count=0
37+
pcim-axi-protocol-error-addr=0x0
38+
pcim-axi-protocol-error-count=0
39+
pcim-write-count=0
40+
pcim-read-count=0
41+
DDR0
42+
write-count=0
43+
read-count=0
44+
DDR1
45+
write-count=0
46+
read-count=0
47+
DDR2
48+
write-count=29797854199
49+
read-count=4
50+
DDR3
51+
write-count=0
52+
read-count=0
53+
```
54+
* For detailed infomation on metrics, see [Amazon FPGA Image Management Tools README](../../sdk//userspace/fpga_mgmt_tools/README.md)

0 commit comments

Comments
 (0)