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: docs/Foundations.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,9 +7,9 @@ To develop on Xilinx FPGAs, there are a couple of workflows:
7
7
1. Legacy HLS -> Vivado workflow
8
8
2. Vitis Kernel workflow (newest)
9
9
10
-
The first workflow is general and works in most of the use cases, independently if the FPGA is intended for Cloud, Edge or instrumental use (like Spartan and Artix). The key artifact is a bitstream (.bit) used for configuring the FPGA, requiring only Vitis/Vivado HLS and Vivado Design Suite.
10
+
The first workflow is general and works in most use cases, independently of the FPGA is intended for Cloud, Edge or instrumental use (like Spartan and Artix). The key artifact is a bitstream (.bit) used for configuring the FPGA, requiring only Vitis/Vivado HLS and Vivado Design Suite.
11
11
12
-
The second workflow is most specific for acceleration. It is used in modern MPSoCs and cloud-grade FPGAs. The key artifact is a binary (.xclbin) that is produced by a long chain of: Vitis HLS, Vivado Design Suite, Petalinux and Vitis. As you may notice, it's more tedious and require more tooling, consuming more storage in the development machine.
12
+
The second workflow is most specific for acceleration. It is used in modern MPSoCs and cloud-grade FPGAs. The key artifact is a binary (.xclbin) that is produced by a long chain of: Vitis HLS, Vivado Design Suite, Petalinux and Vitis. As you may notice, it's more tedious and requires more tooling, consuming more storage in the development machine.
13
13
14
14
PYNQ, particularly, has been characterised by its simplicity, only requiring the bitstream to work. It has also proved to be effective in a wide variety of boards, namely ZYNQ MPSoC and Alveo cards. In contrast, the new workflow requires more expertise in the tooling but produces better applications in terms of performance. However, the former one sacrifices a lot of the simplicity.
15
15
@@ -29,7 +29,7 @@ Within our plans, we want to:
29
29
* Complete the support for XRT interoperability.
30
30
* Provide a library with math kernels.
31
31
32
-
This first release is a huge advance towards simplicity and we expect that many users look at CYNQ as the chance that they were waiting for to get started into the FPGA world, as seen in PYNQ.
32
+
This first release is a huge advance towards simplicity and we expect that many users look at CYNQ as the chance that they were waiting for to get started in the FPGA world, as seen in PYNQ.
<divclass="fragment"><divclass="line">@misc{blabla,</div><divclass="line"> author = {{León-vega, Luis G.</div><divclass="line"> AND Ávila-Torres, Diego</div><divclass="line"> AND Castro-Godínez, Jorge</div><divclass="line"> }},</div><divclass="line"> title = {{CYNQ (v0.1)}},</div><divclass="line"> year = {2023},</div><divclass="line"> url = {https://github.com/ECASLab/cynq},</div><divclass="line">} </div></div><!-- fragment --></div></div><!-- contents -->
134
+
<divclass="fragment"><divclass="line">@misc{cynq,</div><divclass="line"> author = {{León-vega, Luis G.</div><divclass="line"> AND Ávila-Torres, Diego</div><divclass="line"> AND Castro-Godínez, Jorge</div><divclass="line"> }},</div><divclass="line"> title = {{CYNQ (v0.1)}},</div><divclass="line"> year = {2023},</div><divclass="line"> url = {https://github.com/ECASLab/cynq},</div><divclass="line">} </div></div><!-- fragment --></div></div><!-- contents -->
135
135
</div><!-- doc-content -->
136
136
<!-- start footer part -->
137
137
<divid="nav-path" class="navpath"><!-- id is needed for treeview function! -->
Copy file name to clipboardExpand all lines: docs/html/md__media_lleon95_data_Personal_cynq_docs_Foundations.html
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -101,8 +101,8 @@
101
101
<li>Legacy HLS -> Vivado workflow</li>
102
102
<li>Vitis Kernel workflow (newest)</li>
103
103
</ol>
104
-
<p>The first workflow is general and works in most of the use cases, independently if the FPGA is intended for Cloud, Edge or instrumental use (like Spartan and Artix). The key artifact is a bitstream (.bit) used for configuring the FPGA, requiring only Vitis/Vivado HLS and Vivado Design Suite.</p>
105
-
<p>The second workflow is most specific for acceleration. It is used in modern MPSoCs and cloud-grade FPGAs. The key artifact is a binary (.xclbin) that is produced by a long chain of: Vitis HLS, Vivado Design Suite, Petalinux and Vitis. As you may notice, it's more tedious and require more tooling, consuming more storage in the development machine.</p>
104
+
<p>The first workflow is general and works in most use cases, independently of the FPGA is intended for Cloud, Edge or instrumental use (like Spartan and Artix). The key artifact is a bitstream (.bit) used for configuring the FPGA, requiring only Vitis/Vivado HLS and Vivado Design Suite.</p>
105
+
<p>The second workflow is most specific for acceleration. It is used in modern MPSoCs and cloud-grade FPGAs. The key artifact is a binary (.xclbin) that is produced by a long chain of: Vitis HLS, Vivado Design Suite, Petalinux and Vitis. As you may notice, it's more tedious and requires more tooling, consuming more storage in the development machine.</p>
106
106
<p>PYNQ, particularly, has been characterised by its simplicity, only requiring the bitstream to work. It has also proved to be effective in a wide variety of boards, namely ZYNQ MPSoC and Alveo cards. In contrast, the new workflow requires more expertise in the tooling but produces better applications in terms of performance. However, the former one sacrifices a lot of the simplicity.</p>
107
107
<h2>Our Proposal</h2>
108
108
<p>Looking at that, we want to propose a new library based on PYNQ to allow users to code efficient C++ application while keeping the simplicity of PYNQ, allowing even more features like:</p>
@@ -119,7 +119,7 @@ <h2>Our Proposal</h2>
119
119
<li>Complete the support for XRT interoperability.</li>
120
120
<li>Provide a library with math kernels.</li>
121
121
</ul>
122
-
<p>This first release is a huge advance towards simplicity and we expect that many users look at CYNQ as the chance that they were waiting for to get started into the FPGA world, as seen in PYNQ.</p>
122
+
<p>This first release is a huge advance towards simplicity and we expect that many users look at CYNQ as the chance that they were waiting for to get started in the FPGA world, as seen in PYNQ.</p>
123
123
<h2>How does CYNQ work?</h2>
124
124
<p>An application is mounted on top of an abstract interface to make the API feel agnostic. In this case, CYNQ is composed of four major components:</p>
0 commit comments