Skip to content

Commit c646348

Browse files
committed
Updated branding and link placement for more consistency
1 parent 3357b32 commit c646348

File tree

8 files changed

+21
-15
lines changed

8 files changed

+21
-15
lines changed

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@
1212

1313
## Getting Started
1414

15-
Learn how to [develop accelerated applications using SDAccel Development Tools](docs/sdaccel-getting-started/).
15+
Learn how to [develop accelerated applications using SDAccel™ Environment Development Tools](docs/sdaccel-getting-started/).
1616

1717
[![Pathways](docs/sdaccel-getting-started/images/pathway.png)](docs/sdaccel-getting-started/)
1818

@@ -32,7 +32,7 @@ Learn how to [develop accelerated applications using SDAccel Development Tools](
3232
<tr>
3333
<td align="center"><a href="docs/mixing-c-rtl-kernels/README.md">Mixing C and RTL</a></td>
3434
<td align="center">C and RTL</td>
35-
<td>This tutorial demonstrates working with an application containing RTL and OpenCL™ kernels to familiarize yourself with the SDAccel environment flow, along with various design analysis features.</td>
35+
<td>This tutorial demonstrates working with an application containing RTL and OpenCL™ kernels to familiarize yourself with the SDAccel environment flow, along with various design analysis features.</td>
3636
</tr>
3737
<tr>
3838
<td align="center"><a href="docs/using-multiple-cu/README.md">Using Multiple Compute Units</a></td>

docs/controlling-vivado-impl/README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -18,15 +18,15 @@ The SDAccel™ environment XOCC compiler creates kernel objects from the source
1818

1919
This tutorial shows you how to control the Vivado tool flows when implementing your project and guides you through the steps in the command line flow.
2020

21-
The SDAccel environment provides two methods to control the Vivado tool flow:
21+
The SDAccel environment provides two methods to control the Vivado tool flow:
2222

2323
1. When compiling or linking for a system build, you can pass Vivado synthesis and implementation options using the XOCC `--xp` switch.
2424

2525
>**NOTE:** It can take hours to complete a system run.
2626
2727
2. If your application has already been compiled, then you can:
2828

29-
* Optimize the design with the Vivado® Design Suite.
29+
* Optimize the design with the Vivado Design Suite.
3030
* Generate a new routed checkpoint.
3131
* Reuse this checkpoint to generate a new platform file (xclbin).
3232

@@ -153,7 +153,7 @@ Starting FPGA bitstream generation.
153153

154154
# Putting it All Together
155155

156-
The following section summarizes all the steps to control Vivado implementation with the XOCC command, optimize design with the Vivado tool, and reuse implemented dcp to generate the platform file. You might use it as a quick reference for commands.
156+
The following section summarizes all the steps to control Vivado tools implementation with the XOCC command, optimize design with the Vivado tools, and reuse implemented dcp to generate the platform file. You might use it as a quick reference for commands.
157157

158158
1. Set up the environment and working directory.
159159

docs/getting-started-rtl-kernels/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ This tutorial provides the following reference files:
3232
- The host enqueues the RTL kernel (executed on the FPGA), which reads the buffer of the DDR, performs `B[i] = A[i]+B[i]`, and then writes the result back to the DDR.
3333
- The host reads back the data to compare the results.
3434

35-
Using these reference files, the tutorial will guide you from the first step of creating an SDx™ project to the final step of building and running your project.
35+
Using these reference files, the tutorial will guide you from the first step of creating an SDx™ environment project to the final step of building and running your project.
3636

3737
# Before You Begin
3838

docs/mixing-c-rtl-kernels/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@
1212

1313
# Introduction
1414

15-
In the SDAccel™ development environment framework, an application program is split between a host application and hardware accelerated kernels. The host application is developed in C/C++ with OpenCL™ API calls. The hardware kernels, on the other hand, can be developed in C/C++, OpenCL C, or RTL. In fact, SDAccel applications can use any combination of kernels developed in the different languages. The host code is indifferent to how the kernel was developed; it uses the same function call.
15+
In the SDAccel™ development environment framework, an application program is split between a host application and hardware accelerated kernels. The host application is developed in C/C++ with OpenCL™ API calls. The hardware kernels, on the other hand, can be developed in C/C++, OpenCL C, or RTL. In fact, SDAccel environment applications can use any combination of kernels developed in the different languages. The host code is indifferent to how the kernel was developed; it uses the same function call.
1616

1717
# Tutorial Overview
1818

docs/my-first-sdaccel-application/building_application.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -128,8 +128,8 @@ After the functional correctness and host-kernel integration has been verified u
128128
1. For hardware, rebuild the kernels using the `-t hw` XOCC option.
129129

130130
```bash
131-
xocc -t hw_emu --platform xilinx_u200_xdma_201830_1 -g -c -k vadd -I'../src' -o'vadd.xilinx_u200_xdma_201830_1.xo' './src/vadd.cpp'
132-
xocc -t hw_emu --platform xilinx_u200_xdma_201830_1 -g -l --nk vadd:1:vadd_1 -o'vadd.xilinx_u200_xdma_201830_1.xclbin' vadd.xilinx_u200_xdma_201830_1.xo
131+
xocc -t hw --platform xilinx_u200_xdma_201830_1 -g -c -k vadd -I'../src' -o'vadd.xilinx_u200_xdma_201830_1.xo' './src/vadd.cpp'
132+
xocc -t hw --platform xilinx_u200_xdma_201830_1 -g -l --nk vadd:1:vadd_1 -o'vadd.xilinx_u200_xdma_201830_1.xclbin' vadd.xilinx_u200_xdma_201830_1.xo
133133
```
134134

135135
2. Ensure the environment variable XCL_EMULATION_MODE is not set.

docs/sdaccel-execution-model/README.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,9 @@ The SDAccel environment execution model can be broken down into the following st
3838

3939
## Next Steps
4040

41-
Install and configure a development system to write and build host programs and hardware kernels using the SDAccel development environment. Install and configure the Alveo accelerator cards in development, or deployment systems. [Read more...](/docs/alveo-getting-started/)
41+
Install and configure a development system to write and build host programs and hardware kernels using the SDAccel development environment. Install and configure the Alveo accelerator cards in development, or deployment systems.
42+
43+
[Read more...](/docs/alveo-getting-started/)
4244

4345
</br>
4446
<hr/>

docs/sdaccel-getting-started/README.md

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -18,11 +18,15 @@
1818

1919
### 1. Programming and Execution Model
2020

21-
In the SDAccel™ environment framework, an application is split into a host program and hardware accelerated kernels, with a communication channel between them for data transfer. The host application, written in C/C++ and using API calls like OpenCL, runs on an x86 server; the hardware accelerated kernels run within the Xilinx FPGA on an Alveo accelerator card. [Read more...](/docs/sdaccel-execution-model/)
21+
In the SDAccel™ environment framework, an application is split into a host program and hardware accelerated kernels, with a communication channel between them for data transfer. The host application, written in C/C++ and using API calls like OpenCL™, runs on an x86 server; the hardware accelerated kernels run within the Xilinx FPGA on an Alveo™ Data Center accelerator card.
22+
23+
[Read more...](/docs/sdaccel-execution-model/)
2224

2325
### 2. Setting up the Alveo Accelerator Cards and SDAccel Tools
2426

25-
Xilinx® Alveo™ Data Center accelerator cards provide compute acceleration performance and flexibility for Data Centers looking to increase throughput. You can install Alveo accelerator cards in deployment systems for running accelerated applications, or in SDAccel development systems, you can develop, debug, and optimize applications running on Alveo accelerator cards. [Read more...](/docs/alveo-getting-started/)
27+
Alveo Data Center accelerator cards provide compute acceleration performance and flexibility for Data Centers looking to increase throughput. You can install Alveo accelerator cards in deployment systems for running accelerated applications, or in SDAccel development systems, you can develop, debug, and optimize applications running on Alveo accelerator cards.
28+
29+
[Read more...](/docs/alveo-getting-started/)
2630

2731
### 3. Building the Accelerated Application - Essential Concepts
2832

@@ -50,13 +54,13 @@ In this tutorial, you will learn how to do the following:
5054

5155
[Read more...](/docs/my-first-sdaccel-application/)
5256

53-
### 5. Optimizing Accelerated FPGA Applications - Based on SDAccel Methodology
57+
### 5. Optimizing Accelerated FPGA Applications Based on SDAccel Environment Methodology
5458

5559
The methodology for developing optimized accelerated applications is comprised of two major phases: architecting the application, and developing the hardware kernels. In the first phase, you make key decisions about the application architecture by determining which software functions should be accelerated onto FPGA kernels, how much parallelism can be achieved, and how to deliver it in code. In the second phase, you implement the kernels by structuring the source code, and applying the necessary compiler options and pragmas to create the kernel architecture needed to achieve the optimized performance target.
5660

5761
In this tutorial, you will learn how to do the following:
5862

59-
- Create an SDAccel application from the C application.
63+
- Create an SDAccel environment application from the C application.
6064
- Optimize memory transfers.
6165
- Optimize using fixed point data types.
6266
- Optimize with dataflow.

docs/using-multiple-cu/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ This tutorial demonstrates a flexible kernel linking process to increase the num
1616

1717
# Tutorial Overview
1818

19-
By default, the SDAccel™ tool creates one CU for each kernel. A host program can use the same kernel multiple times for different sets of data. In these cases, it is useful to generate multiple CUs of the kernel to let those CUs run concurrently, and improve the performance of the overall system.
19+
By default, the SDAccel™ environment tool creates one CU for each kernel. A host program can use the same kernel multiple times for different sets of data. In these cases, it is useful to generate multiple CUs of the kernel to let those CUs run concurrently, and improve the performance of the overall system.
2020

2121
For more information, see [Multiple Instances of a Kernel](https://www.xilinx.com/html_docs/xilinx2019_1/sdaccel_doc/pni1524163195211.html#yzb1524519238289) in the _SDAccel Environment Programmers Guide_ ([UG1277](https://www.xilinx.com/html_docs/xilinx2019_1/sdaccel_doc/vno1533881025717.html)).
2222

0 commit comments

Comments
 (0)