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:using-github-releases [2021/05/14 23:04] – ↷ Page moved from reference:programmable-logic:guides:using-github-releases to programmable-logic:guides:using-github-releases Arthur Brownprogrammable-logic:guides:using-github-releases [2022/10/04 11:38] (current) – external edit 127.0.0.1
Line 16: Line 16:
 --> Open a Vivado Project from a Release # --> Open a Vivado Project from a Release #
 <WRAP group> <WRAP group>
-{{page>reference:programmable-logic:guides:vivado-launch&showheader}}+{{page>programmable-logic:guides:vivado-launch&showheader}}
  
 <WRAP group> <WRAP group>
Line 29: Line 29:
 --> Build a Vivado Project # --> Build a Vivado Project #
 <WRAP group> <WRAP group>
-{{section>reference:programmable-logic:guides:getting-started-with-vivado#generate_a_bitstream&showheader}}+Note that if your project already has a generated bitstream, as indicated by the status in the top right corner of the window reading "write_bitstream Complete!", then you can skip this section. 
 + 
 +{{ :programmable-logic:guides:write-bitstream-complete.png |}} 
 + 
 +{{section>programmable-logic:guides:getting-started-with-vivado#generate_a_bitstream&showheader}}
 </WRAP> </WRAP>
 <-- <--
Line 35: Line 39:
 --> Program a Bitstream onto an FPGA Board # --> Program a Bitstream onto an FPGA Board #
 <WRAP group> <WRAP group>
-{{page>reference:programmable-logic:guides:vivado-hardware-manager}}+{{page>programmable-logic:guides:vivado-hardware-manager}}
 </WRAP> </WRAP>
 <-- <--
Line 59: Line 63:
 **Important:** //When selecting a workspace to open Vitis into, the use of the extracted software archive's "ws" folder is recommended. The use of this folder simplifies the process of invoking the script that recreates the projects.// **Important:** //When selecting a workspace to open Vitis into, the use of the extracted software archive's "ws" folder is recommended. The use of this folder simplifies the process of invoking the script that recreates the projects.//
  
-{{page>reference:programmable-logic:guides:vitis-launch&noheader}}+{{page>programmable-logic:guides:vitis-launch&noheader}}
  
 <WRAP group> <WRAP column half> <WRAP group> <WRAP column half>
Line 94: Line 98:
 --> Import Vitis Projects from a Release # --> Import Vitis Projects from a Release #
 <WRAP group> <WRAP group>
-{{page>reference:programmable-logic:guides:vitis-launch&noheader}}+{{page>programmable-logic:guides:vitis-launch&noheader}}
  
 <WRAP group> <WRAP column half> <WRAP group> <WRAP column half>
Line 113: Line 117:
 --> Build a Vitis Application # --> Build a Vitis Application #
 <WRAP group> <WRAP group>
-{{page>reference:programmable-logic:guides:vitis-build-software&noheader}}+{{page>programmable-logic:guides:vitis-build-software&noheader}}
 </WRAP> </WRAP>
 <-- <--
Line 129: Line 133:
 --> Import Vitis Projects from a Release # --> Import Vitis Projects from a Release #
 <WRAP group> <WRAP group>
-{{page>reference:programmable-logic:guides:vitis-launch&noheader}}+{{page>programmable-logic:guides:vitis-launch&noheader}}
  
 <WRAP group> <WRAP column half> <WRAP group> <WRAP column half>
Line 148: Line 152:
 --> Launch a Vitis Application # --> Launch a Vitis Application #
 <WRAP group> <WRAP group>
-{{page>reference:programmable-logic:guides:vitis-launch-app&noheader}}+{{page>programmable-logic:guides:vitis-launch-app&noheader}}
 </WRAP> </WRAP>
 <-- <--
Line 156: Line 160:
 --> Open a Block Design Project in Vivado # --> Open a Block Design Project in Vivado #
 <WRAP group> <WRAP group>
-{{page>reference:programmable-logic:guides:vivado-launch&showheader}}+{{page>programmable-logic:guides:vivado-launch&showheader}}
  
 <WRAP group> <WRAP column half> <WRAP group> <WRAP column half>
Line 170: Line 174:
 </WRAP> </WRAP> </WRAP> </WRAP>
 ---- ----
-Making changes to the design is out of the scope of this particular document. More information on how to use IP Integrator to create or modify a project can be found through [[reference:programmable-logic:guides:getting-started-with-ipi]]. The remainder of this document will discuss how to generate a bitstream, export a new hardware platform, and load it into Vitis.+Making changes to the design is out of the scope of this particular document. More information on how to use IP Integrator to create or modify a project can be found through [[programmable-logic:guides:getting-started-with-ipi]]. The remainder of this document will discuss how to generate a bitstream, export a new hardware platform, and load it into Vitis.
 ---- ----
-{{page>reference:programmable-logic:guides:vivado-validate-block-design}}+{{page>programmable-logic:guides:vivado-validate-block-design}}
 </WRAP> </WRAP>
 <-- <--
 --> Build a Vivado Project # --> Build a Vivado Project #
 <WRAP group> <WRAP group>
-{{page>reference:programmable-logic:guides:vivado-generate-bitstream}}+{{page>programmable-logic:guides:vivado-generate-bitstream}}
 </WRAP> </WRAP>
 <-- <--
 --> Export a Hardware Platform # --> Export a Hardware Platform #
 <WRAP group> <WRAP group>
-{{page>reference:programmable-logic:guides:vivado-export-fixed-platform}}+{{page>programmable-logic:guides:vivado-export-fixed-platform}}
 </WRAP> </WRAP>
 <-- <--
 --> Update a Hardware Platform in Vitis # --> Update a Hardware Platform in Vitis #
 <WRAP group> <WRAP group>
-{{page>reference:programmable-logic:guides:vitis-update-hardware-specification}}+{{page>programmable-logic:guides:vitis-update-hardware-specification}}
 </WRAP> </WRAP>
 <-- <--
Line 200: Line 204:
 --> Open a Petalinux Project from a Release # --> Open a Petalinux Project from a Release #
 <WRAP group> <WRAP group>
-Open a terminal and run the following commands. The install path is /opt/pkg/petalinux/ as exemplified in [[https://www.xilinx.com/support/documentation/sw_manuals/xilinx2020_1/ug1144-petalinux-tools-reference-guide.pdf|UG1144 v.2020.1]]. This will set up the Petaliunx environment for this terminal only.+Open a terminal and run the following commands. The install path is /opt/pkg/petalinux/ as exemplified in [[https://docs.xilinx.com/v/u/2020.1-English/ug1144-petalinux-tools-reference-guide|UG1144 v.2020.1]]. This will set up the Petalinux environment for this terminal only.
 <code> <code>
 source <path-to-installed-PetaLinux>/settings.sh source <path-to-installed-PetaLinux>/settings.sh
Line 254: Line 258:
 ===== Petalinux Configurations ===== ===== Petalinux Configurations =====
  
-**Note:** //This a brief summary of what Petalinux can do. For more details please refer to the [[https://www.xilinx.com/support/documentation/sw_manuals/xilinx2020_1/ug1144-petalinux-tools-reference-guide.pdf|UG1144 v.2020.1]]//+**Note:** //This a brief summary of what Petalinux can do. For more details please refer to the [[https://docs.xilinx.com/v/u/2020.1-English/ug1144-petalinux-tools-reference-guide|UG1144 v.2020.1]]//
  
 There are some components that can be modified in Petalinux in order to customize your Linux environment. These include the user space application, kernel drivers, u-boot configuration, generic Petalinux settings, and Hardware update components. Most of these changes can be done by executing the //petalinux-config// command with different parameters. There are some components that can be modified in Petalinux in order to customize your Linux environment. These include the user space application, kernel drivers, u-boot configuration, generic Petalinux settings, and Hardware update components. Most of these changes can be done by executing the //petalinux-config// command with different parameters.
Line 267: Line 271:
 --> Open a Block Design Project in Vivado # --> Open a Block Design Project in Vivado #
 <WRAP group> <WRAP group>
-{{page>reference:programmable-logic:guides:vivado-launch&showheader}}+{{page>programmable-logic:guides:vivado-launch&showheader}}
  
 <WRAP group> <WRAP column half> <WRAP group> <WRAP column half>
Line 281: Line 285:
 </WRAP> </WRAP> </WRAP> </WRAP>
 ---- ----
-Making changes to the design is out of the scope of this particular document. More information on how to use IP Integrator to create or modify a project can be found through [[reference:programmable-logic:guides:getting-started-with-ipi]]. The remainder of this document will discuss how to generate a bitstream, export a new hardware platform, and load it into Vitis.+Making changes to the design is out of the scope of this particular document. More information on how to use IP Integrator to create or modify a project can be found through [[programmable-logic:guides:getting-started-with-ipi]]. The remainder of this document will discuss how to generate a bitstream, export a new hardware platform, and load it into Vitis.
 ---- ----
-{{page>reference:programmable-logic:guides:vivado-validate-block-design}}+{{page>programmable-logic:guides:vivado-validate-block-design}}
 </WRAP> </WRAP>
 <-- <--
 --> Build a Vivado Project # --> Build a Vivado Project #
 <WRAP group> <WRAP group>
-{{page>reference:programmable-logic:guides:vivado-generate-bitstream}}+{{page>programmable-logic:guides:vivado-generate-bitstream}}
 </WRAP> </WRAP>
 <-- <--
 --> Export a Hardware Platform # --> Export a Hardware Platform #
 <WRAP group> <WRAP group>
-{{page>reference:programmable-logic:guides:vivado-export-fixed-platform}}+{{page>programmable-logic:guides:vivado-export-fixed-platform}}
 </WRAP> </WRAP>
 <-- <--
Line 357: Line 361:
 <WRAP round important> <WRAP round important>
 ==Warning== ==Warning==
-After configuring some of the previous settings might be lost. This is a known issue in Petalinux 2019.2 and 2020.1; more information about the workaround can be found here [[https://forums.xilinx.com/t5/Embedded-Linux/2020-1-Kernel-config-always-overwritten/td-p/1139697|Xilinx Forum]]+After configuring some of the previous settings might be lost. This is a known issue in Petalinux 2019.2 and 2020.1; more information about the workaround can be found here: [[https://support.xilinx.com/s/question/0D52E00006iHqLBSA0/20201-kernel-config-always-overwritten|Xilinx Support Case]]
 </WRAP> </WRAP>
 ---- ----