Quantcast
Channel: Xilinx Wiki : Xilinx Wiki - all changes
Viewing all 11776 articles
Browse latest View live

sw6_setup.JPG


Zynq UltraScale+MPSoC Graphics- GPU application debugging using ARM Mali Graphics Debugger tool

$
0
0
...
Insert SD card into the SD card slot J100.
Set the SW6 switches as shown. This configures the boot settings to boot from SD:
{RevD_sw6.JPG} Fig:zcu102 Rev-B/Rev-C/Rev-D boards sw6 setups > {Rev1_sw6.JPG} Fig: zcu102 Rev-1.0 board sw6 setup{sw6_setup.JPG}
Connect 12V Power to the ZCU102 6-Pin Molex connector.
Connect the monitor using DisplayPort cable to U50.

Zynq UltraScale+ MPSoC Graphics - 3D Vehicle Model

$
0
0
...
1. Connect the Micro USB cable into the ZCU102 Board Micro USB port J83, and the other end into an open USB port on the windows PC. This cable will be used for UART over USB communication.
2. Insert SD card into the SD card slot J100.
...
switches as shown.shown for the different boards. This configures
...
boot mode.
{sd_mode1.PNG} Fig: Switch selection for SD boot mode

{sw6_setup.JPG}

4. Connect 12V Power to the ZCU102 6-Pin Molex connector.
5. Connect the Display monitor using DisplayPort cable to U50 connector of the board.

Zynq UltraScale+ MPSoC Graphics - 3D Vehicle Model

$
0
0

Zynq UltraScale+MPSoC Graphics- GPU application debugging using ARM Mali Graphics Debugger tool

$
0
0

Zynq UltraScale+ MPSoC USB 3.0 CDC Device Class Design

$
0
0
...
2. Designed for ZCU102 Rev1.0 and RevB/C/D Boards
Summary
...
any given time.Thetime. The USB 3.0
The CDC design example block diagram and overview
How to configure all the Zynq® ultrascale +™ MPSoC Linux kernel and dependent files for the CDC class reference
...
--
Files Provided
Zynqmp_CDC_Design_files.zipZynqmp_CDC_design_files_2016_4.zip
See Appendix A for the descriptions of the files
Block Diagram
...
Go to Device Drivers -->
USB Support --> enable required drivers as shown in figure below
{usb_kernel_config.jpg} Figure 3:2: Linux kernel
Go to File Systems -->
Pseudo filesystems --> enable Userspace-driven configuration filesystems as shown in figure below.
{filesystem_configuratioj.png} Figure 4:3: Linux kernel
Ensure that parameters shown in the below figure are selected in the kernel source tree and save & exit the configuration file.
As this Tech Tip is intends to configure the Zynq® UltraScale+™ MPSoC USB 3.0 controller in device mode. Add below mentioned node at end of system-top.dts file present at "<project_name>/project-spec/meta-user/recipes-dt/device-tree/files/"
...
g_serial.ko from following path “<project_name>/build/tmp/work/plnx_aarch64-xilinx-linux/petalinux-user-image/1.0-r0/rootfs/lib/modules/4.6.0-xilinx/kernel/drivers/usb/gadget/legacy"
Image.ub from “<project_name>/images/linux”
...
use other prebuiltpre-built modules. Refer
...
about design file.files.
ZCU102 Board Setup:
...
the ZCU102 board.board(Rev1.0 /B/C/D). Do not
Connect the Micro USB cable into the ZCU102 Board Micro USB port J83, and the other end into an open USB port on the host Machine as shown in figure below.
{zcu102_board_setup_device_mode.png} Figure 6:4: ZCU102 board
Make sure the switches are set as shown in figure 7(ZCU102 Rev B/C/D) and figure 8(ZCU102 Rev1.0), which allows the ZCU102 board to boot from the SD-MMC card.
{sd_boot_mode_switch_settings.jpg} Figure 7:5: SD boot
...
B/C/D Board {zcu102_rev1_sd_boot_mode.png}
{zcu102_rev1_sd_boot_mode.png}
Figure 8:6: SD boot
To operate board in device mode, OFF J7 jumper as shown in board figure 6 (ZCU102 board setup in device mode).
Testing Linux Zynq® UltraScale+™ MPSoC USB 3.0 communication device class functionality on Windows host PC:
...
insmod g_serial.ko
Now the Zynq® UltraScale+™ MPSoC USB 3.0 gadget serial device is ready.
{zynqmp_cdc_console_2016_4.png} Figure 9:8: Zynqmp linux
Now connect USB 3.0 cable between board and host machine. Conenct type A male side end to host machine USB3.0 port and Micro B male side end of cable to USB3.0 connector (J96) on ZCU102 board as shown in figure 6 ZCU102 board setup.
Host PC tries to enumerate the Zynq® UltraScale+™ MPSoC USB 3.0 as a communication class device and try to install the appropriate windows driver from network.
...
This will open Device manager wizard window. Check for other devices. Right click on Gadget Serial v2.4 and click to Update Driver Software as shown in figure below. Make sure that host machine is connected over network.
After installing the driver software successfully the Zynq® UltraScale+™ MPSoC USB 3.0 device is detected as a virtual communication port (PI USB to Serial Port) at the host PC side and on the other side i.e. target side. USB serial gadget driver is registered as /dev/ttyGS0.
{pl_usb_com_driver.jpg} Figure 10:9: Gadget driver
Start the installed UART terminal program on your host PC (e.g. Tera Term on a Windows PC) with this newly detected virtual COM port.
Use the UART configuration as: Baud rate = 115200, bits = 8=, parity =none, and stop bits =1.
In order to send data from the target device we need to use the USB serial gadget drive device file ‘/dev/ttyGS0’. We can use echo command as shown below to send the data from the device to the windows PC.
$ echo Hello >/dev/ttyGS0
...
port (ex: COM58)COM9) as shown
...

{windows_cdc_2016_4_result1.png} Figure 12:10: Serial terminal
...
host machine
n

In
the similar
...
terminal (ex: COM58)COM9) opened on
...

{windows_cdc_2016_4_result2.png} Figure 12:11: Serial terminal
Testing Linux Zynq® UltraScale+™ MPSoC USB 3.0 communication device class functionality on Linux host PC:
The CDC ACM only driver that comes with the Linux kernel is supported on Linux host PC.
Once the device is attached inspect the log to obtain the device file names used on the host by entering the following command on the terminal window of Linux (Red hat/ Ubuntu) machine.
$ dmesg | tail -n 20
{driver_detection_ttyacm0.png} Figure 13:12: Inspecting log
The serial communication port get registered as 'ttyACM0' meaning it will show up as '/dev/ttyACM0'.
In order to send data from the target device we need to use the USB serial gadget driver device file '/dev/ttyGS0'. We can echo command to send data from the device to the Linux host computer.
{linux_cdc_2016_4_result1_new.png} Figure 14:13: Sending data
...
3.0 ttyGS0
se

Use
the following
...

{usb_linux_2nd_host_op.png} Figure 15:14: Reading data
In the similar way if we want to send data from the host computer to the device we should first send the data from host by running following command
{linux_cdc_2016_4_result2.png} Figure 16: Sending data over ttyACM0
Read it on the device using "$cat /dev/ttyGS0" command.
{linux_cdc_2016_4_result3.png} Figure 17:15: Reading data
...
target at ttyGS0
Appendix
ttyGS0Appendix A: If
...
be added
Zynqmp_CDC_Design_files.zip

Zynqmp_CDC_design_files_2016_4.zip

Design_files
BOOT_rev1.0.BIN

Zynq UltraScale+ MPSoC USB 3.0 CDC Device Class Design

$
0
0

This Page is under construction
Document History
Date
...
Connect the Micro USB cable into the ZCU102 Board Micro USB port J83, and the other end into an open USB port on the host Machine as shown in figure below.
{zcu102_board_setup_device_mode.png} Figure 4: ZCU102 board setup for Communication device class
...
in figure 7(ZCU102 Rev B/C/D) and figure 8(ZCU102 Rev1.0),below. which allows
...
SD-MMC card.
Figure 5 shows SD boot mode settings for ZCU102 Rev-B/C/D board

{sd_boot_mode_switch_settings.jpg} Figure 5: SD boot mode switch setting for ZCU102 Rev B/C/D Board
{zcu102_rev1_sd_boot_mode.png} Figure 6:Figure 6 shows SD boot mode switch settings for ZCU102 Rev1.0 board
To
baord
{zcu102_rev1_sd_boot_mode.png}
To
operate board
...
board figure 64 (ZCU102 board
Testing Linux Zynq® UltraScale+™ MPSoC USB 3.0 communication device class functionality on Windows host PC:
Load the SD card into the ZCU102 board, in the J100 connector
...
{windows_cdc_2016_4_result1.png} Figure 10: Serial terminal shows successful transfer of data from target board to host machine
In the similar way if we want to send data from the host computer to the device write some string (ex: Hello) on the virtual terminal (ex: COM9) opened on the host computer. Read the data at the device side by opening the serial gadget driver device file using "cat /dev/ttyGS0" command as shown in figure below
...
to target board
Testing
boardTesting Linux Zynq®
The CDC ACM only driver that comes with the Linux kernel is supported on Linux host PC.
Once the device is attached inspect the log to obtain the device file names used on the host by entering the following command on the terminal window of Linux (Red hat/ Ubuntu) machine.

Zynq UltraScale+MPSoC Graphics- GPU Profiling using ARM Streamline performance analyzer

$
0
0
...
Preparing the FSBL
Preparing the BOOT.bin file
...
ZCU102 BSP from the path and ZCU102 BSP for corresponding board.
{petalinux_download.JPG} {bsp_download.JPG}
Note:Download the bsp based on the board you have.Download the ZCU102 BSP for Rev-B/Rev-C/Rev-D boards and ZCU102 ES2.0 Rev1.0 for Rev-1.0 board.

Zynq UltraScale+ MPSoC Ubuntu part 2 - Building and Running the Ubuntu Desktop From Sources

$
0
0
Zynq UltraScale+ MPSoC Ubuntu part 2 - Building and Running the Ubuntu Desktop From Sources
Note: This page is under construction ,changes are expected !!!
1. Document History
Date
...
Rajesh Gugulothu
Updated for 2016.3 tool version
3.0
Rajesh Gugulothu
Updated with 2016.4 tools Release and Added design
files to support zcu102 Rev-B/Rev-C/Rev-D ,Rev-1.0 boards

2. Summary
Zynq® UltraScale+™ MPSoC delivers unprecedented levels of heterogeneous multi-processing and combines seven user programmable processors including Quad-core ARM® Cortex™-A53 Application Processing Unit (APU), Dual-core 32-bit ARM® Cortex™-R5 Real Time Processing Unit (RPU), and ARM® Mali™-400 MP2 Graphics Processing Unit (GPU). It is Industry’s First All Programmable Multi-Processor SoC delivering 5x system level performance-per-watt and any-to-any connectivity.
...
4. Procedure to build from sources:
This section covers the following topics
...
the Petalinux 2016.32016.4
BSP Creation
Kernel Configuration
...
ZCU102 Board setup
Steps to execute the Demo
...
the Petalinux 2016.32016.4
This section
...
of version 2016.3.2016.4.
4.1.1. Download the Petalinux petalinux-v2016.3-final-installer.runpetalinux-v2016.4-installer.run and ZCU102 BSP from the below path
http://www.xilinx.com/support/download/index.html/content/xilinx/en/downloadNav/embedded-design-tools/2016-3.html
{plnx_installar_download.GIF} Petalinux SDK Installer and BSP
for corresponding board.
{petalinux_download.JPG} {bsp_download.JPG}

4.1.1.1.Install the Petalinux by running the above downloaded installer
. /petalinux-v2016.3-final-installer.run/petalinux-v2016.4-installer.run
Note: please refer the Petalinux user guide.
4.1.1.2.After installation is done set the Petalinux environment by running below command in bash shell

Zynq UltraScale+ MPSoC USB 3.0 Mass Storage Device Class Design

$
0
0
...
Rutuja Chavan & Rajesh Gugulothu
Initial Version
17/02/2017
1.1
Rutuja Chavan
1. Updated to 2016.4 tool version
2. Designed for ZCU102 Rev1.0 and RevB/C/D Boards

Summary
The Zynq® UltraScale+™ MPSoC USB 3.0 controller consists of two independent dual-role device (DRD) controllers. Both can be individually configured to work as host or device at any given time. The USB 3.0 DRD controller provides an eXtensible host controller interface (xHCI) to the system software through the advanced eXtensible interface (AXI) slave interface. An internal DMA engine is present in the controller and it utilizes the AXI master interface to transfer data. There are four primary types of communication defined by the USB protocol, based on which any required application can be built without changing the firmware or underlying hardware for different applications. These transfer types are Control Transfer, Bulk Transfer, Isochronous transfer and Interrupt transfer. Zynq® UltraScale+™ MPSoC USB3.0 controller supports all four types of transfers.This Tech Tip explains how to enable all the configuration options, step by step procedure to use the Zynq® UltraScale+™ MPSoC USB 3.0 controller in device mode and make use of bulk transfer type for mass storage device using the USB 3.0. For complete specifications of USB protocol and class specific specifications refer: http://www.usb.org/developers/docs/
...
USB 3.0 Controller
Boards/Tools
ZCU102 Board(B/C/D)
ZCU102 Rev 1.0
Board
Xilinx Tools Version
...
petalinux SDK 2016.32016.4 or latest
Other Details
--
Files Provided
Zynqmp_mass_storage_Design_files.zipZynqmp_mass_storage_design_files_2016_4.zip
See Appendix A for the descriptions of the design files
Block Diagram
...
Configuring and building the Linux for Mass storage gadget driver support using PetaLinux SDK:
Follow the PetaLinux SDK installation user guide in this document to install and configure Petalinux SDK. Execute the steps till the PetaLinux Working Environment Setup section for installing PetaLinux SDK to your Linux machine.
...
PetaLinux version 2016.3.2016.4. It recommend
...
installer version 2016.32016.4 from Xilinx website. This example uses the ZCU102 PetaLinux BSP to create a PetaLinux project. For Rev1 board download ZCU102,ES2,Rev1.0 BSP and for Rev B/C/D boards, download ZCU102 BSP from xilinx website.
After
...
–n <project_name> -s <path-to-bsp> command
Above command will create a project with the user provided name under the PetaLinux installed directory. Change the directory to project directory which is created above. $ cd <project_name>
Configure the Linux source to support USB mass storage gadget driver by executing PetaLinux command $ petalinux-config -c kernel
...
{filesystem_configuratioj.png} Figure 3: Linux kernel configuration to enable userspace driven configuration
Ensure that parameters shown in the above figures are selected in the kernel source tree. Save and exit the configuration file.
...
device mode. Change the USB device treeAdd below mentioned node property “dr_mode“ in the device tree source code as “peripheral" which controls the modeat end of the device driver. The respective device treesystem-top.dts file named as pcw.dtsi can be found under the path “<petalinux_installed_path>/<project_name>/subsystems/linux/configs/device-tree”.
{device_tree_configuration.jpg} Figure 4: Device tree modification to configure USB 3.0 in device mode
present at "<project_name>/project-spec/meta-user/recipes-dt/device-tree/files/"&dwc3_0 {
dr_mode = "peripheral";
status = "okay";
};

With the above changes in kernel configuration, build petalinux using command "$ petalinux-build". This builds the image.ub executable and some other USB mass storage gadget driver support modules.
Create BOOT.BIN using petalinux SDK tool, change directory to images/linux (cd images/linux) directory and run below command.
...
Preparing SD card:
copy the following files into the SD card
...
present at “<petalinux_installed_directory>/<project_name>/images/linux”“<project_name>/images/linux”
libcomposite.ko file
...
following path “<petalinux_installed_directory>/<project_name>/build/linux/kernel/xlnx-4.6/drivers/usb/gadget/”.“<project_name>/build/tmp/work/plnx_aarch64-xilinx-linux/petalinux-user-image/1.0-r0/rootfs/lib/modules/4.6.0-xilinx/kernel/drivers/usb/gadget/”
g_mass_storage.ko file
...
following path “<petalinux_installed_directory>/<project_name>/build/linux/kernel/xlnx-3.17/drivers/usb/gadget/legacy”.“<project_name>/build/tmp/work/plnx_aarch64-xilinx-linux/petalinux-user-image/1.0-r0/rootfs/lib/modules/4.6.0-xilinx/kernel/drivers/usb/gadget/legacy”.
usb_f_mass_storage.ko from following path “<petalinux_installed_directory>/<project_name>/build/linux/kernel/xlnx-3.17/drivers/usb/gadget/function”.“<project_name>/build/tmp/work/plnx_aarch64-xilinx-linux/petalinux-user-image/1.0-r0/rootfs/lib/modules/4.6.0-xilinx/kernel/drivers/usb/gadget/function”.
Image.ub from “<petalinux_installed_directory>/<project_name>/images/linux”.“<project_name>/images/linux”.
Note: For
...
provided along with this Tech Tip. Download the design files archive released with this Tech Tip and extract it under the convenient location of host machine. Find the SD card images under the path Design_files/pre_built_images/. User canDesign_files/pre_built_images/ of your extracted directory. For Rev1.0 board copy BOOT_rev1.0.BIN into SD card and for Rev B/C/D boards, copy BOOT_revBCD.BIN file into SD card and use these imagesother pre-built modules. Refer to appendix A for quick test.more information about design files.
ZCU102 Board Setup:
...
the ZCU102 board.board(Rev1.0 /B/C/D). Do not
Connect the Micro USB cable into the ZCU102 Board Micro USB port J83, and the other end into an open USB 3.0 port on the host Machine as shown in figure below.
{zynqmp_zcu102_connection_diagram.png} Figure 5:4: ZCU102 board
Make sure the switches (SW6) are set as shown in figure below which allows the ZCU102 board to boot from the SD-MMC card.
{sd_boot_mode_switch_settings.jpg}Figure 6 shows SD boot mode settings for ZCU102 Rev-B/C/D board
{sd_boot_mode_switch_settings.jpg} Figure 5: SD boot mode switch setting for ZCU102 board
Figure 6 shows SD boot mode settings for ZCU102 Rev1.0 baord
{zcu102_rev1_sd_boot_mode.png}
Figure 6:
...
for ZCU102 Rev1.0 board
To
...
board figure 54 (ZCU102 board
Testing Linux Zynq® UltraScale+™ MPSoC USB 3.0 mass storage device functionality on Windows host PC:
Load the SD card into the ZCU102 board, in the J100 connector
...
dd if=/dev/zero of=/tmp/test.img bs=1M count=256
insmod g_mass_storage.ko file=/tmp/test.img removable=1
...
in figure 5.4.
Above inserted modules configures the Zynq® UltraScale+™ MPSoC USB 3.0 as a mass storage device. When it is detected as mass storage device, host PC will install all the required drivers on the host side(make sure that you are connected to network). A 256MB size of disk image will be mounted on the host pc.
In case of windows host PC a Microsoft windows disk formatting wizard gets popped up. Click on Format disk and start formatting the disk. After completion of formatting disk perform the read and write operations like file copy, update and open etc from host PC to disk pace created vice versa.
...
In case of Linux (Ubuntu) host PC the Zynq® UltraScale+™ MPSoC USB 3.0 appears as a mass storage device of 256MB. Perform read and write operations from Linux PC to the disk space created vice versa.
Appendix A: Design File structure
Zynqmp_mass_storage_Design_files.zipZynqmp_mass_storage_design_files_2016_4.zip
Design_files
pre_built_images
BOOT.BINBOOT_rev1.0.BIN
BOOT_revBCD.BIN

image.ub
Kernel modules listed below

Zynq UltraScale+ MPSoC USB 3.0 CDC Device Class Design

$
0
0
...
Configure the Linux source to support communication device class driver by executing PetaLinux command $ petalinux-config -c kernel
Go to Device Drivers -->
...
Support --> enable
USB Gadget Support-->
enable
required drivers
{usb_kernel_config.jpg} Figure 2: Linux kernel configuration withUSB 3.0 device mode CDC ACM support
Go to File Systems -->
...
Now the Zynq® UltraScale+™ MPSoC USB 3.0 gadget serial device is ready.
{zynqmp_cdc_console_2016_4.png} Figure 8: Zynqmp linux console after successful installation
...
in figure 64 ZCU102 board
Host PC tries to enumerate the Zynq® UltraScale+™ MPSoC USB 3.0 as a communication class device and try to install the appropriate windows driver from network.
Note: if automatic driver installation fails and it shows a popup windows of Device driver software was not successfully installed. In that case try to install the windows driver for Zynq® UltraScale+™ MPSoC USB 3.0 device on host machine by following the below procedure.

Zynq UltraScale+ MPSoC USB 3.0 CDC Device Class Design

$
0
0
...
{sd_boot_mode_switch_settings.jpg} Figure 5: SD boot mode switch setting for ZCU102 Rev B/C/D Board
Figure 6 shows SD boot mode settings for ZCU102 Rev1.0 baord
{zcu102_rev1_sd_boot_mode.png} Figure 6: SD boot mode settings for ZCU102 Rev1.0 board
To operate board in device mode, OFF J7 jumper as shown in board figure 4 (ZCU102 board setup in device mode).
Testing Linux Zynq® UltraScale+™ MPSoC USB 3.0 communication device class functionality on Windows host PC:
...
insmod g_serial.ko
Now the Zynq® UltraScale+™ MPSoC USB 3.0 gadget serial device is ready.
{zynqmp_cdc_console_2016_4.png} Figure 8:7: Zynqmp linux
Now connect USB 3.0 cable between board and host machine. Conenct type A male side end to host machine USB3.0 port and Micro B male side end of cable to USB3.0 connector (J96) on ZCU102 board as shown in figure 4 ZCU102 board setup.
Host PC tries to enumerate the Zynq® UltraScale+™ MPSoC USB 3.0 as a communication class device and try to install the appropriate windows driver from network.
...
In the windows host machine, click on the start button and Search for Device Manager and click on it to select.
This will open Device manager wizard window. Check for other devices. Right click on Gadget Serial v2.4 and click to Update Driver Software as shown in figure below. Make sure that host machine is connected over network.
...
Zynq® UltraScale+™ MPSoC USB 3.0 deviceMPSoCUSB 3.0device is detected
...

{pl_usb_com_driver.jpg} Figure 9:8: Gadget driver
Start the installed UART terminal program on your host PC (e.g. Tera Term on a Windows PC) with this newly detected virtual COM port.
Use the UART configuration as: Baud rate = 115200, bits = 8=, parity =none, and stop bits =1.
...
$ echo Hello >/dev/ttyGS0
After that you should see the Hello on the virtual communication port (ex: COM9) as shown below figure.
{windows_cdc_2016_4_result1.png} Figure 10:9: Serial terminal
In the similar way if we want to send data from the host computer to the device write some string (ex: Hello) on the virtual terminal (ex: COM9) opened on the host computer. Read the data at the device side by opening the serial gadget driver device file using "cat /dev/ttyGS0" command as shown in figure below
{windows_cdc_2016_4_result2.png} Figure 11:10: Serial terminal
The CDC ACM only driver that comes with the Linux kernel is supported on Linux host PC.
Once the device is attached inspect the log to obtain the device file names used on the host by entering the following command on the terminal window of Linux (Red hat/ Ubuntu) machine.
$ dmesg | tail -n 20
{driver_detection_ttyacm0.png} Figure 12:11: Inspecting log
The serial communication port get registered as 'ttyACM0' meaning it will show up as '/dev/ttyACM0'.
In order to send data from the target device we need to use the USB serial gadget driver device file '/dev/ttyGS0'. We can echo command to send data from the device to the Linux host computer.
{linux_cdc_2016_4_result1_new.png} Figure 13:12: Sending data
Use the following command to display data received over the USB serial connection from the USB device on the Linux host machine
{usb_linux_2nd_host_op.png} Figure 14:13: Reading data
In the similar way if we want to send data from the host computer to the device we should first send the data from host by running following command
{linux_cdc_2016_4_result2.png} Figure 16:14: Sending data
Read it on the device using "$cat /dev/ttyGS0" command.
{linux_cdc_2016_4_result3.png} Figure 15: Reading data on target at ttyGS0Appendix A: If other items need to be added

Zynq UltraScale MPSoC Base TRD 2016.4 - Design Module 9

$
0
0
...
Copy the content of the generated sd_card folder to the dm9 SD card directory.
% cd $TRD_HOME/apu/video_app
...
cp -rf filter2d/Release/sd_cardfilter2d/Release/sd_card/* $TRD_HOME/images/dm9
Copy the generated bitstream to the PetaLinux directory or alternatively use the pre-built bitstream already bundled with the PetaLinux BSP.
% cp -f filter2d/Release/libfilter2d.so.bit $TRD_HOME/apu/petalinux_bsp/images/linux

Zynq UltraScale MPSoC Base TRD 2016.4 - Design Module 8

$
0
0
...
{base-trd-2016-3-dm7-sdx-filter2d-build.png}
Copy the content of the generated sd_card folder to the dm8 SD card directory
% mkdir -p $TRD_HOME/images/dm8/bin
%
cp -rf filter2d/Release/sd_cardfilter2d/Release/sd_card/* $TRD_HOME/images/dm8
Video Qt Application
There is no need to rebuild the video_qt2 application if you have already built it in module 7, otherwise follow the instructions from module 7.

PS and PL based Ethernet in Zynq MPSoC

$
0
0
...
Netperf , Netperf page
Appendix A
How to patch Device Tree in petalinux2016.4:
Create PetaLinux BSP for PS-EMIO and PL Ethernet project
This section describes how to create PetaLinux BSP from scratch. It is assumed that PetaLinux environment is set properly.
NOTE : The instructions remain the same for both PL Ethernet and PS EMIO designs.
1 Create Ethernet project
bash> petalinux-create -t project -n <project-name>
bash> cd <project-name>
2 Sync HW description
bash> petalinux-config --get-hw-description=<path-to-hw-description-hdf>
Point to SDK Export directory for the relevant design.
Set one of local directory as tmp directory of petalinux and Save the changes and exit.
3. Petalinux Configuration
a. Disable kernel autoconfig settings
bash> petalinux-config
Auto Config Settings --->
[ ] kernel autoconfig
Uncheck kernel autoconfig
b. Ethernet Setting -- >Subsystem AUTO Hardware Settings ---> Ethernet Settings --->
[ ] Obtain IP address automatically
Unchecked obtain IP address automatically
4. Configure petalinnux to apply patch in FSBL and kernel
a. How
to patch
To patch Linux kernel instruct tool to clone Linux kernel from git and then apply patch on it.
To do that, copy patch file in <PROJ_DIR>\project-spec\meta-user\recipes-kernel\linux\linux-xlnx location.
...
Third line is name of patch file which to be applied on this cloned kernel. This should have same name as the file present in <PROJ_DIR>\project-spec\meta-user\recipes-kernel\linux\linux-xlnx.
In the project, the patch name is 0001-kernel-10G-axienet.patch.
Howb. How to patch
To patch FSBL we must instruct tool to apply patch on it. FSBL soruce code is part of project only. There is not need of extra cloning of the same.
To do that, copy patch file in <PROJ_DIR>\project-spec\meta-user\recipes-fsbl\fsbl\files location.
...
This should have same name as the file present in <PROJ_DIR>\project-spec\meta-user\recipes-fsbl\fsbl\.
In my case, the patch name is 0001-fsbl-si570-clk.patch.
Howc. How to patch
...
Tree in petalinux2016.4:
Create PetaLinux BSP for PS-EMIO
petalinux2016.4
Open DT file from <PROJ_DIR>\project-spec\meta-user\recipes-dt/files directory
and PL Ethernetremove all SI570 nodes.
5 Build the Petalinux
project
This section describes how

bash> petalinux-build -v
6 Create Zynqmp Boot image
Bellow command will create image.ub.
bash> petalinux-package --image
To create boot.bin, go to <petalinux_project>/images/linux
Create bif file with below content
Add bif file here
run below command in same directory
to create PetaLinuxboot.img
bash> bootgen -arch zynqmp -image boot.bif -w -o boot.bin
7 Package
BSP from scratch. It is assumed that PetaLinux environment is set properly.
NOTE : The instructions remain the same for both PL Ethernet and PS EMIO designs.
1 Create Ethernet project

bash> petalinux-create -t project -npetalinux-package --bsp -p<project-name>
bash> cd <project-name>
2 Sync HW description
petalinux-config --get-hw-description=<path-to-hw-description-hdf>
Set one of local directory as tmp directory of petalinux and Save the changes and exit.
-o <project-name>.bsp
SRC_URI += "file://0001-fsbl-si570-clk-156MHz.patch"
$XAPP_HOME/xapp1305-ps-pl-ethernet-based-solution

PS and PL based Ethernet in Zynq MPSoC

$
0
0

PS and PL Ethernet Performance for Zynq Ultrascale+ MPSoC
1. Introduction
...
and PL. In addition to this, it also includes throughput numbers for all combinations. The designs provided with this application note enable the use of Ethernet ports and provide kernel mode Linux device drivers.
The design provided with this application note enable the use of multiple Ethernet ports and provide kernel-mode Linux device drivers. In addition, this document includes Ethernet performance measurement with checksum offload support enable.
This page discusses the following.
...
Relevant constraints file is also associated with the design.
NOTE : In this design "GEM3" is also enabled along with GEM0 in ZYNQ UltraScale+ GUI.
...
is connected tpto PL through
{ps_emio_eth_1g_1.JPG}
3. In the Flow Navigator Panel, click on 'Generate Bitstream' to implement the design and get a bitstream (see below Figure).
...
Navigate to hardware/vivado/scripts/pl_eth_10g for PL Ethernet 10G BASE-R design
$ vivado -source pl_eth_10g_top.tcl
...
the design lloadedeeloaded below Figure).
{pl_eth_10g_1.JPG}
3. In the Flow Navigator panel, click on 'Generate Bitstream' to implement the design and get a bitstream.

Zynq UltraScale+ MPSoC Graphics - 3D Vehicle Model

$
0
0
...
Rajesh Gugulothu
Updated with 2016.4 tools Release and Added design
...
support zcu102 Rev-B/Rev-C/Rev-DRev-B/Rev-D ,Rev-1.0 boards
Summary:
Zynq® UltraScale+™ MPSoC delivers unprecedented levels of heterogeneous multi-processing and combines seven user programmable processors including Quad-core ARM® Cortex™-A53 Application Processing Unit (APU), Dual-core 32-bit ARM® Cortex™-R5 Real Time Processing Unit (RPU), and ARM® Mali™-400 MP2 Graphics Processing Unit (GPU). It is Industry’s First All Programmable Multi-Processor SoC delivering 5x system level performance-per-watt and any-to-any connectivity.
...
DDR controller,UART,SD/eMMC interface, USB 3.0,DisplayPort
Boards/Tools
zcu102 Rev-C,Rev-DRev-B,Rev-D
Xilinx Tools Version
SDK 2016.22016.4
Other Details
Host Type
...
Procedure to build Linux Images
This section describes how to build the Linux boot images for Zynq® UltraScale+™ MPSoC. This section covers the following topics
...
the Petalinux 2016.22016.4
BSP Creation
Kernel Configuration

Zynq UltraScale+ MPSoC Graphics - 3D Vehicle Model

$
0
0

pmufw.JPG

Zynq UltraScale+ MPSoC Graphics - 3D Vehicle Model

$
0
0
...
SDK 2016.4
Other Details
1080p /4K display.
Host Type
Ubuntu Linux 16.04 LTS
...
Highlights of the demo Execution:
Boots SMP Linux on APU subsystem.
...
using OSG middlewaremiddle-ware which executes
X-server windowing system is used to display the rendered graphics application on to Sink device (Monitor) using Processing System DisplayPort controller
GPU offloads the APU for the OpenGL ES2 API based applications, rendering a 3D vehicle graphics model written in OSG format.
...
Preparing the FSBL
Preparing the BOOT.bin file
...
the http://www.wiki.xilinx.com/Zynq+UltraScale%EF%BC%8BMPSoC+Graphics-+GPU+Profiling+using+ARM+Streamline+performance+analyzer techTech Tip"compiling and
...
create the images.
2.Copy the BOOT.bin
below images and image.ubcopy them on to athe SD card.Makecard.
BOOT.bin
image.ub
2.make
sure that , final SD card has the below images before going to follow the below section.contains fallowing images.
BOOT.bin
image.ub
Viewing all 11776 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>