Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
programmable-logic:guides:hierarchical-blocks [2021/05/14 23:04] – ↷ Page moved from reference:programmable-logic:guides:hierarchical-blocks to programmable-logic:guides:hierarchical-blocks Arthur Brownprogrammable-logic:guides:hierarchical-blocks [2022/10/04 11:38] (current) – external edit 127.0.0.1
Line 8: Line 8:
   * A Digilent FPGA development board.   * A Digilent FPGA development board.
   * A computer with Vivado installed.   * A computer with Vivado installed.
-    * //See the [[reference:programmable-logic:guides:installation]] guide for more information.//+    * //See the [[programmable-logic:guides:installing-vivado-and-vitis]] guide for more information.//
   * Familiarity with Vivado IP Integrator and a base block design to work from.   * Familiarity with Vivado IP Integrator and a base block design to work from.
-    * //Following the [[reference:programmable-logic:guides:getting-started-with-ipi]] guide will result in a design that fits all requirements.//+    * //Following the [[programmable-logic:guides:getting-started-with-ipi]] guide will result in a design that fits all requirements.//
 ===== Guide ===== ===== Guide =====
 ==== Setting Up Dependencies ==== ==== Setting Up Dependencies ====
Line 48: Line 48:
 **Note**: //The design must contain a processor and a peripheral that can be used for stdout. In the case of Microblaze, a UART IP must be connected to the board's USBUART interface. In the case of Zynq, the PS UART is used by default.// **Note**: //The design must contain a processor and a peripheral that can be used for stdout. In the case of Microblaze, a UART IP must be connected to the board's USBUART interface. In the case of Zynq, the PS UART is used by default.//
  
-Completing the [[reference:programmable-logic:guides:getting-started-with-ipi]] guide will result in a design that fits the requirements for using these hierarchical blocks.+Completing the [[programmable-logic:guides:getting-started-with-ipi]] guide will result in a design that fits the requirements for using these hierarchical blocks.
 </WRAP> <WRAP COLUMN HALF> </WRAP> <WRAP COLUMN HALF>
 {{ :learn:programmable-logic:tutorials:vivado-hierarchical-blocks:base-bd.png?600 |}} {{ :learn:programmable-logic:tutorials:vivado-hierarchical-blocks:base-bd.png?600 |}}
Line 113: Line 113:
 ---- ----
 === Constraining the Design === === Constraining the Design ===
-This step works a little differently depending on whether the peripheral targeted by the hierarchical block is a [[reference:zmod:start|Zmod]] or a [[reference:pmod:start|Pmod]]. Select the dropdown for the chosen peripheral:+This step works a little differently depending on whether the peripheral targeted by the hierarchical block is a [[zmod:start|Zmod]] or a [[pmod:start|Pmod]]. Select the dropdown for the chosen peripheral:
  
 --> Pmod# --> Pmod#
Line 165: Line 165:
 ==== Baremetal Software ==== ==== Baremetal Software ====
 <WRAP round center important> <WRAP round center important>
-Zmod Hierarchical Blocks are supported in software by the Zmod Library. If using a Zmod, see the [[reference:zmod:zmodbaselibraryuserguide|Zmod Base Library User Guide]], and skip the rest of this guide. If Petalinux support for the added hierarchy is desired, first see the [[reference:programmable-logic:eclypse-z7:customizing-zmods-os|Zmod Petalinux Configuration Guide]]+Zmod Hierarchical Blocks are supported in software by the Zmod Library. If using a Zmod, see the [[zmod:zmodbaselibraryuserguide|Zmod Base Library User Guide]], and skip the rest of this guide. If Petalinux support for the added hierarchy is desired, first see the [[programmable-logic:eclypse-z7:customizing-zmods-os|Zmod Petalinux Configuration Guide]]
 </WRAP> </WRAP>
  
Line 173: Line 173:
  
 <WRAP GROUP> <WRAP GROUP>
-{{page>reference:programmable-logic:guides:vivado-export-fixed-platform&noheader}}+{{page>programmable-logic:guides:vivado-export-fixed-platform&noheader}}
 </WRAP> </WRAP>
  
Line 181: Line 181:
  
 <WRAP GROUP> <WRAP GROUP>
-{{page>reference:programmable-logic:guides:vitis-launch&noheader}}+{{page>programmable-logic:guides:vitis-launch&noheader}}
 </WRAP> </WRAP>
  
Line 189: Line 189:
  
 <WRAP GROUP> <WRAP GROUP>
-{{page>reference:programmable-logic:guides:vitis-create-app&noheader}}+{{page>programmable-logic:guides:vitis-create-app&noheader}}
 </WRAP> </WRAP>
  
Line 197: Line 197:
  
 <WRAP GROUP> <WRAP GROUP>
-{{page>reference:programmable-logic:guides:vitis-add-hierarchy-example&noheader}}+{{page>programmable-logic:guides:vitis-add-hierarchy-example&noheader}}
 </WRAP> </WRAP>
  
Line 205: Line 205:
  
 <WRAP GROUP> <WRAP GROUP>
-{{page>reference:programmable-logic:guides:vitis-launch-app&showheader}}+{{page>programmable-logic:guides:vitis-launch-app&showheader}}
 </WRAP> </WRAP>
  
Line 215: Line 215:
 The Vitis sources provided with the hierarchical blocks are set up such that they can be easily included in any design using that block. The subfolder below sdk_sources contains all necessary drivers for the block. The Vitis sources provided with the hierarchical blocks are set up such that they can be easily included in any design using that block. The subfolder below sdk_sources contains all necessary drivers for the block.
  
-For more reference materials and guides on the Digilent products being used, navigate to their resource centers, which can be found through this wiki's [[reference:programmable-logic:start]] page.+For more reference materials and guides on the Digilent products being used, navigate to their resource centers, which can be found through this wiki's [[programmable-logic:start]] page.
  
 For technical support, please visit the [[https://forum.digilentinc.com|Digilent Forums]]. For technical support, please visit the [[https://forum.digilentinc.com|Digilent Forums]].