At this point, we are done with Vivado and it can be closed. Save the project for future reference if prompted.
Important! Tag this page with: techtip-Building the Softwarex-Building the SoftwareBuilding the Software
the software developed in an earlier Tech Tip in this series to move steps; building a new boot filesfile that includeincludes the hardware and interrupt service software infor the base PetaLinux systemXADC block and then
Building the boot files:BOOT.BIN file:
For this XADC block. For compatibility withTherefore, the other Tech Tips in this series, modificationsonly boot file that needs to be built is the base PetaLinux system are included. No specific action byBOOT.BIN as it contains the user is required at this time.
Because we previously added an interface tobitstream which has the new hardware system fromin the user application and using interrupts,PL. In the device tree structure (dts) that isprevious Tech Tip "Zynq-7000 AP SoC Spectrum Analyzer part 6 - Accelerating Software - Accelerating an FFT with ACP Coprocessor Tech Tip 2014.3" the PetaLinux SDK was used to describebuild both the system to the kernel at boot time must be modified. Information on how user space device drivers operateBOOT.BIN and their basic implementationimage.ub files. For this Tech Tip, we can be founduse Vivado SDK because we are not building the slide set "Linux User Space Device Drivers" located inimage.ub file. Since we are only changing the Xilinx forums. Other resources such as the PetaLinux Tools Reference Guide describe various aspects of both modificationbitstream portion of the dts as well as importing new hardware and building newBOOT.BIN, we will use a first stage boot loader (fsbl) and u-boot.elf files used by the PetaLinux system for the ZC702.
We assume thatsame operation.
The base TRD for the ZC702 that utilizes PetaLinux SDK has been installed on an appropriate Linux system. See section 5 ofis described in the technical article Zynq Base TRD 2014.2 forFollow the instructions on installingfound there to download the PetaLinux system.software from the Xilinx web site. Unzip the set of files to a convenient place on your computer. In addition, be sure that Qtour case, we put them in our "Projects" folder:
G:\Projects\rdf0286-zc702-zvik-base-trd-2014-2
If we look inside this folder, we can see a variety of files but a fsbl and Qwt are properly installed according to the Qt and Qwt Base Libraries Build Instructions. If Qt and Qwtu-boot.elf are not properly installed,readily apparent. However, there is a large file with the buildextension of .bsp that is in the boot files will failpetalinux folder. Normally this is used to run properly for either the TRD or other graphics applications.
Start by creatingset up a new project (UG1124 page 21).
We then importwithin the hardware description from Vivado into PetaLinux development environment. For our use, we are going to configureextract the needed boot files from this project. Recall that.bsp file.
G:\Projects\rdf0286-zc702-zvik-base-trd-2014-2\software\petalinux\bsp\Xilinx-zc702-trd-v2014_2.bsp
While we exportedcould extract the hardware from Vivado, saving itcontents at the current location, to be sure we do not disturb the file system_top_wrapper.hdf.
NOTE:
Asintegrity of the 2014.2 release, Vivado exportsTRD, we simply copy the hardware description in.bsp file to another location. Once that is done, change the hdf (hardware description file) whereas previous versions exportedextension to .tar (this file is really a XML file. Similarly, PetaLinux now expectscompressed Linux compatible file). Then we can use a standard tool to import"un-compress" the hdf format only.
Followfile, resulting in the instructions on page 23following set of UG1124 to importfolders withing the hardwareextracted archive.
{ExtractedBSPfolders.PNG}
If we then drill into the just created project.
Followpre-built folder to linux and then images, we can find the instructions in section 5following set of files
{PrebuiltBootFiles.PNG}
From within SDK, we will simply use the Zynq Base TRD 2014.2 for re-building the PetaLinux systemnow readily visible zynq_fsbl.elf and creatingu-boot.elf files along with the new boot.bin and image.ub files. Be surebitstream to usebuild the bitstream and hdf file created by Vivado for the design that includes the hardware FFT block and associated control logic.required new BOOT.BIN file.
The new bootBOOT.BIN file now and FFT blocks and accompanying DMA engines as well as ablocks. At this point we have not modified device tree blobthe PetaLinux system that enables interruptsgets loaded from the DMA blockimage.ub file so there is no need to be servicedmodify it. The application built in user space within Linux.the following section will simply be invoked as an application running on the PetaLinux after it has booted.
Important! Tag this page with: techtip-Building the Software-Building the Application:Building the Application:
the new boot files, and the dts modified to include interrupts from the DMA enginesBOOT.BIN file we can with the hardware using interrupts.hardware.
List all the steps to run the design. This includes hardware, software and tools needed.
Expected Results