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: ERRATA.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,8 @@ Shell errata is [documented here](./hdk/docs/AWS_Shell_ERRATA.md)
7
7
## HDK
8
8
* Multiple SDE instances per CL is not supported in this release. Support is planned for a future release.
9
9
* DRAM Data retention is not supported for CL designs with less than 4 DDRs enabled
10
-
* Combinatorial loops in CL designs are not supported.
10
+
* Combinatorial loops in CL designs are not supported.
11
+
* We will display a `UNKNOWN_BITSTREAM_GENERATE_ERROR` on detection of a combinatorial loop in the CL design and an AFI will not be generated.
11
12
* Connecting one of the clocks provided from the shell (clk_main_a0, clk_extra_a1, etc...) directly to a BUFG in the CL is not supported by the Xilinx tools and may result in a non-functional clock. To workaround this limitation, it is recommended to use an MMCM to feed the BUFG (clk_from_shell -> MMCM -> BUFG). Please refer to [Xilinx AR# 73360](https://www.xilinx.com/support/answers/73360.html) for further details.
Copy file name to clipboardExpand all lines: Vitis/README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -200,7 +200,7 @@ For help with AFI creation issues, see [create-fpga-image error codes](../hdk/do
200
200
$ cd $AWS_FPGA_REPO_DIR
201
201
$ source vitis_runtime_setup.sh # Other runtime env settings needed by the host app should be setup after this step
202
202
# Wait till the MPD service has initialized. Check systemctl status mpd
203
-
$ ./host ./vadd.awsxclbin
203
+
$ ./hello_world ./vadd.awsxclbin
204
204
```
205
205
* The runtime setup script also starts the Xilinx XRT Message Proxy Daemon(MPD) service. To learn more about the XRT implementation, check the [XRT Instructions](./docs/XRT_installation_instructions.md#mpd)
Copy file name to clipboardExpand all lines: Vitis/docs/Alveo_to_AWS_F1_Migration/example/README.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -46,7 +46,7 @@ The [`u200`](./u200) and The [`u200`](./u200) and [`f1`](./f1) directories cont
46
46
sp=vadd_1.out:DDR[1]
47
47
```
48
48
49
-
* The `platform` option specifies which acceleration platform is targeted for the build. Here we are using the U200 shell.
49
+
* The `platform` option specifies which acceleration platform is targeted for the build. Here we are using the U200 shell.
50
50
* The `sp` options are used to specify the assignment of kernel arguments to DDR banks. In this case, we are mapping all three kernel arguments to DDR[1], which is the DDR interface located in the shell on Alveo U200.
51
51
52
52
> Putting all the platform-specific options in one file is not mandatory but it is very convenient and facilitates the porting process. With this approach, the main command line can be reused as is for all platforms. Refer to the [Vitis Documentation](https://www.xilinx.com/html_docs/xilinx2020_1/vitis_doc/kme1569523964461.html) for more information on v++ related commands and options.
@@ -70,7 +70,8 @@ In order to port the vector-add example from Alveo U200 to AWS F1, the only chan
70
70
sp=vadd_1.out:DDR[0]
71
71
```
72
72
73
-
* The `platform` option is set to target the AWS F1 shell. The string used corresponds to the name of the latest shell which can be found [here](https://github.com/aws/aws-fpga/tree/master/Vitis/aws_platform) on the aws-fpga repo.
73
+
* The `platform` option is set to target the AWS F1 shell. The string used corresponds to the name of the latest shell which can be found [here](https://github.com/aws/aws-fpga/tree/master/Vitis/aws_platform) on the aws-fpga repo. Point the platform to the xpfm file. For example,
74
+
```platform=$AWS_PLATFORM```
74
75
* The `sp` options are set to connect the kernel arguments to DDR[0], which is the DDR interface located in the AWS F1 shell. Keeping the same settings as the U200 would produce a working design on AWS F1. But in order to produce exactly the same configuration and target the DDR interface located in the AWS F1 shell, the sp options are modified to use DDR[0].
75
76
76
77
These changes are the only ones needed to port this project from U200 to F1.
@@ -84,7 +85,7 @@ In order to port the vector-add example from Alveo U200 to AWS F1, the only chan
*NOTE: The PLATFORM_REPO_PATHS environment variable is used to specify the directory where the AWS platform (xilinx_aws-vu9p-f1_shell-v04261818_201920_2) is installed.*
0 commit comments