Show page
Old revisions
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
connect-hls [2017/02/24 05:42] zzhao1 |
connect-hls [2017/10/31 00:30] (current) zzhao1 |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | =====Using Vivado-HLS for Structural Design: a NoC Case Study===== | ||
| + | |||
| There have been ample successful examples of applying Xilinx Vivado's "function-to-module" high-level synthesis (HLS) where the subject is algorithmic in nature. In CONNECT-HLS project, we carried out a design study to assess the effectiveness of applying Vivado-HLS in structural design, where precise bit- and cycle- level control is a must. We succeeded in using Vivado-HLS to produce router and NoC modules that are exact cycle- and bit-accurate replacements of our reference [[http://users.ece.cmu.edu/~mpapamic/connect|CONNECT]] RTL-based router and NoC modules. The routers and NoCs resulting from HLS and RTL are comparable in resource utilization and critical path delay. Our experience subjectively suggests that HLS is able to | There have been ample successful examples of applying Xilinx Vivado's "function-to-module" high-level synthesis (HLS) where the subject is algorithmic in nature. In CONNECT-HLS project, we carried out a design study to assess the effectiveness of applying Vivado-HLS in structural design, where precise bit- and cycle- level control is a must. We succeeded in using Vivado-HLS to produce router and NoC modules that are exact cycle- and bit-accurate replacements of our reference [[http://users.ece.cmu.edu/~mpapamic/connect|CONNECT]] RTL-based router and NoC modules. The routers and NoCs resulting from HLS and RTL are comparable in resource utilization and critical path delay. Our experience subjectively suggests that HLS is able to | ||
| simplify the design effort even though much of the structural details had to be provided in the HLS description through a combination of coding discipline and explicit pragmas. | simplify the design effort even though much of the structural details had to be provided in the HLS description through a combination of coding discipline and explicit pragmas. | ||
| - | For more details, please see our technical report and source code below. Please contact [[zzhao1@andrew.cmu.edu|Zhipeng Zhao at zzhao1@andrew.cmu.edu]] | + | For more details, please see our technical report, poster and source code below. Please contact [[zzhao1@andrew.cmu.edu|Zhipeng Zhao at zzhao1@andrew.cmu.edu]] |
| for any questions or bug reports. | for any questions or bug reports. | ||
| <html> | <html> | ||
| - | <font size=4><b>Technical Report</b></font> | + | <font size=4><b>Technical Report and Poster</b></font> |
| <hr> | <hr> | ||
| </html> | </html> | ||
| - | **{{http://www.ece.cmu.edu/~coram/connect-hls/Tech_Report.pdf|Using Vivado-HLS for Structural Design: a NoC Case Study}}**\\ | + | **{{http://arxiv.org/abs/1710.10290|Using Vivado-HLS for Structural Design: a NoC Case Study}}**\\ |
| + | **{{http://www.ece.cmu.edu/~coram/connect-hls/Poster.pdf|Poster}}**\\ | ||
| \\ | \\ | ||
