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
Pulling in PR: 466, 468, 470, 471 from aws-fpga (#586)
* Remove duplicate line (#468)
* Correct path for helloworld example (#466)
In xilinx_2019.1 @ 0ec1aef (and not previous versions) the hello world example is located in $SDACCEL_DIR/examples/xilinx/getting_started/hello_world/helloworld_ocl/ rather than $SDACCEL_DIR/examples/xilinx/getting_started/host/helloworld_ocl/
* Update path (#470)
* Update path
Attempting to change directories into this path (i.e., `/home/centos/src/project_data/aws-fpga/SDAccel/examples/xilinx_2017.4/getting_started/host/helloworld_ocl`) draws an error because the `xilinx_2017.4` directory is empty, now, and `xilinx` is a symbolic link that points to the latest release (i.e., `/home/centos/src/project_data/aws-fpga/SDAccel/examples/xilinx_2019.1`). Additionally: `helloworld_ocl` is no longer a sub-directory of `host`; it's now a sub-directory of `hello_world`: so this part of the path should be updated as well.
* Fix unset flags
The alphanumeric part of these flags (i.e., `f`) are preceded by en dashes, when they should be hyphens; as using the former instead of the later results in errors (`-bash: unset: ``–f': not a valid identifier`).
* Update path to workspace directory
This change is consistent with 48c3048, and the basename of the image, but has a different filename extension because of the transparency.
* Update figures 1, 2, and 3 for SDx 2019.1 (#471)
* Update gui_fig_2.png and gui_fig_3.png to SDx 2019.1
SDx's welcome screen has stratified the option (read: clickable button)
to `Create SDx Project` into two new ones: `Create Platform Project`
and `Create Library Project`. These changes are rendered in Figure 2,
while Figure 3 captures cosmetic differences to the user interface.
* Add Figure 2
* Add Figure 3
Copy file name to clipboardExpand all lines: SDAccel/README.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -89,7 +89,7 @@ For CPU-based (SW) emulation, both the host code and the FPGA binary code are co
89
89
The instructions below describe how to run the SDAccel SW Emulation flow using the Makefile provided with a simple "hello world" example
90
90
91
91
```
92
-
$ cd $SDACCEL_DIR/examples/xilinx/getting_started/host/helloworld_ocl/
92
+
$ cd $SDACCEL_DIR/examples/xilinx/getting_started/hello_world/helloworld_ocl/
93
93
$ make clean
94
94
$ make check TARGETS=sw_emu DEVICES=$AWS_PLATFORM all
95
95
```
@@ -104,7 +104,7 @@ The SDAccel hardware emulation flow enables the developer to check the correctne
104
104
The instructions below describe how to run the HW Emulation flow using the Makefile provided with a simple "hello world" example:
105
105
106
106
```
107
-
$ cd $SDACCEL_DIR/examples/xilinx/getting_started/host/helloworld_ocl/
107
+
$ cd $SDACCEL_DIR/examples/xilinx/getting_started/hello_world/helloworld_ocl/
108
108
$ make clean
109
109
$ make check TARGETS=hw_emu DEVICES=$AWS_PLATFORM all
110
110
```
@@ -118,7 +118,7 @@ The SDAccel system build flow enables the developer to build their host applicat
118
118
The instructions below describe how to build the Xilinx FPGA Binary and host application using the Makefile provided with a simple "hello world" example:
119
119
120
120
```
121
-
$ cd $SDACCEL_DIR/examples/xilinx/getting_started/host/helloworld_ocl/
121
+
$ cd $SDACCEL_DIR/examples/xilinx/getting_started/hello_world/helloworld_ocl/
122
122
$ make clean
123
123
$ make TARGETS=hw DEVICES=$AWS_PLATFORM all
124
124
```
@@ -198,7 +198,7 @@ For help with AFI creation issues, see [create-fpga-image error codes](../hdk/do
198
198
* Depending on the host code, the \*.awsxclbin may need to named \<hostcodename>.hw.\<platformname>.awsxclbin .For Example: ```vector_addition.hw.xilinx_aws-vu9p-f1-04261818_dynamic_5_0.awsxclbin```
199
199
* Copy any data files required for execution to the new instance
200
200
*[Clone the github repository to the new F1 instance and install runtime drivers](#gitsetenv)
201
-
* Clone the github repository to the new F1 instance and install runtime drivers
Copy file name to clipboardExpand all lines: SDAccel/docs/README_GUI.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ The SDAccel examples from the github are downloaded by the above steps. However,
29
29
30
30
First change directory to **helloworld_ocl** example.
31
31
```
32
-
$ cd <git area>/SDAccel/examples/xilinx_2017.4/getting_started/host/helloworld_ocl
32
+
$ cd <git area>/SDAccel/examples/xilinx/getting_started/hello_world/helloworld_ocl
33
33
```
34
34
The github examples use common header files and those needs to be copied in the local project source folder to make it easier to use.
35
35
Type the command **make local-files** to copy all necessary files in the local directory.
@@ -46,9 +46,9 @@ To debug using gdb inside from SDX gui few additional commands are needed to exe
46
46
47
47
```
48
48
$ mv /usr/local/Modules/init init.bak
49
-
$ unset –f switchml
50
-
$ unset –f _moduleraw
51
-
$ unset –f module
49
+
$ unset -f switchml
50
+
$ unset -f _moduleraw
51
+
$ unset -f module
52
52
$ sdx
53
53
```
54
54
@@ -62,7 +62,7 @@ We will now cover the following steps:
62
62
Add workspace inside the current directory named "GUI_test" as shown below. A new directory **GUI_test** will be created and used to store all logfiles of our runs.
63
63
64
64
65
-

65
+

66
66
67
67
<br>
68
68
@@ -71,15 +71,15 @@ You will get a Welcome screen. You need to set Platform path by selecting **Add
0 commit comments