Wiki

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
resources:tools-software:linux-software:build-the-zynqmp-boot-image [30 Apr 2020 16:42] – Updated cygwin configuration to include microblaze compiler path Adrian Costinaresources:tools-software:linux-software:build-the-zynqmp-boot-image [10 Jan 2022 09:24] – [Usage] Stefan-Robert Raus
Line 40: Line 40:
  
 <code> <code>
-usage: build_zynqmp_boot_bin.sh system_top.hdf u-boot.elf (download | bl31.elf | <path-to-arm-trusted-firmware-source>) [output-archive]+usage: build_zynqmp_boot_bin.sh system_top.xsa u-boot.elf (download | bl31.elf | <path-to-arm-trusted-firmware-source>) [output-archive]
 </code> </code>
-  * Path to ''system_top.hdf'' and ''u-boot.elf'' are required parameters.+  * Path to ''system_top.xsa'' and ''u-boot.elf'' are required parameters.
   * The 3rd argument must either be ''download'' (which will git clone the ATF repository), ''bl31.elf'' or the file system ''path'' to the Arm Trusted Firmware source code repository   * The 3rd argument must either be ''download'' (which will git clone the ATF repository), ''bl31.elf'' or the file system ''path'' to the Arm Trusted Firmware source code repository
   * An optionally 4th ''name'' parameter can be given to tar.gz the output directory. (''name''.tar.gz)   * An optionally 4th ''name'' parameter can be given to tar.gz the output directory. (''name''.tar.gz)
   * Build output is located in a local directory named: output_boot_bin.   * Build output is located in a local directory named: output_boot_bin.
-  * This script requires Xilinx XSDK and bootgen in the PATH.\\+  * This script requires Xilinx Vitis and bootgen in the PATH.\\
     * A simple way is to source vivado settings[32|64].sh for Linux:     * A simple way is to source vivado settings[32|64].sh for Linux:
 <code> <code>
-$ source /opt/Xilinx/Vivado/201x.x/settings64.sh+$ source /opt/Xilinx/Vivado/202x.x/settings64.sh
 </code> </code>
  
Line 55: Line 55:
  
 <code> <code>
-export PATH=$PATH:/cygdrive/c/Xilinx/Vivado/201x.x/bin +export PATH=$PATH:/cygdrive/c/Xilinx/Vivado/202x.x/bin 
-export PATH=$PATH:/cygdrive/c/Xilinx/SDK/201x.x/bin +export PATH=$PATH:/cygdrive/c/Xilinx/Vitis/202x.x/bin 
-export PATH=$PATH:/cygdrive/c/Xilinx/SDK/2019.1/gnu/microblaze/nt/bin+export PATH=$PATH:/cygdrive/c/Xilinx/Vitis/202x.x/gnu/microblaze/nt/bin
 </code> </code>
  
- <WRAP left tip round box 100%>**NOTE: u-boot.elf**\\+<WRAP left tip round box 100%>**NOTE: u-boot.elf**\\
 For those who don't want to build u-boot themselves.\\  For those who don't want to build u-boot themselves.\\ 
 The **u-boot.elf** can be extracted from the project folder on the [[resources/tools-software/linux-software/zynq_images#download_linux_image|SD Card image]], **bootgen_sysfiles.tgz**  The **u-boot.elf** can be extracted from the project folder on the [[resources/tools-software/linux-software/zynq_images#download_linux_image|SD Card image]], **bootgen_sysfiles.tgz** 
  
 </WRAP> </WRAP>
resources/tools-software/linux-software/build-the-zynqmp-boot-image.txt · Last modified: 20 Mar 2023 12:41 by Iulia Moldovan