ZU＋ Example - Deep Sleep with Periodic Wake-up

August 11, 2017, 5:02 am

≫ Next: ZU＋ Example - PM Hello World

≪ Previous: ZU＋ Example - Deep Sleep with PS SysMon in Sleep Mode

$

0

0

...

Start with an empty RPU application (like the Hello World example here).
Configure the RPU to run from TCM (see above.)
(If(Default HDF has split mode, So RPU will run in split mode. If application doesn't

...

need to changedivide the size of the TCMsections for ATCM and BTCM memory from 0x10000 to 0x30000regions in lscript.ld file.)file. For more information please see Table 4-5: TCM Address Map in TRM. When running in split mode, each R5 processor has 64KB ATCM and 64KB BTCM. So, user has to divide sections across ATCM and BTCM. As per below snapshot vectors and text sections are in ATCM and other sections are in BTCM) {tcm_sections.png}
Replace the main.c with this file:
{rpu_deep_sleep_with_periodic_wakeup.c}

...

[pmufw_image] pmufw.elf
[bootloader,destination_cpu=a53-0] zynqmp_fsbl.elf
[bootloader,destination_cpu=r5-lockstep][bootloader,destination_cpu=r5-0] rpu.elf
[destination_cpu=a53-0, exception_level=el-3,trustzone] bl31.elf
[destination_cpu=a53-0, exception_level=el-2] u-boot.elf

---

ZU＋ Example - PM Hello World

August 11, 2017, 5:02 am

≫ Next: ZU＋ Example - Deep Sleep with Periodic Wake-up

≪ Previous: ZU＋ Example - Deep Sleep with Periodic Wake-up

$

0

0

...

Steps to modify code memory
Open lscript.ld file.

...

shown below. {ss8.png}
(Default HDF has split mode, So RPU will run in split mode. If RPU running in split mode than user has to select "psu_r5_0_atcm_MEM_0" or
"psu_r5_0_btcm_MEM_0". If RPU running in lock step mode than user has to select "psu_r5_tcm_ram_0_MEM_0".)
{ss8.png}
Save lscript.ld file and build the project.
Note: To run this example on board, FSBL and PMU needs to be run along with application elf.

ZU＋ Example - Deep Sleep with Periodic Wake-up

August 11, 2017, 6:54 am

≫ Next: Getting started with Yocto Xilinx layer

≪ Previous: ZU＋ Example - PM Hello World

$

0

0

...

echo request_wakeup 8 1 0 1 > /sys/kernel/debug/zynqmp_pm/power
echo force_powerdown 8 > /sys/kernel/debug/zynqmp_pm/power
echo release_node 69 > /sys/kernel/debug/zynqmp_pm/power
echo MMIO_WRITE 0xFFD80064 1 1 > /sys/kernel/debug/zynqmp_pm/power
The DS50 LED will on for 2 seconds when RPU wakes up, after that RPU goes down to sleep for 2 seconds. RPU wakes up again and same cycle repeats every time. One can change LED on time (or do another task instead of LED on/off) and RPU sleep time according to requirement.

Getting started with Yocto Xilinx layer

August 14, 2017, 1:58 pm

≫ Next: ZU＋ Example - Deep Sleep

≪ Previous: ZU＋ Example - Deep Sleep with Periodic Wake-up

$

0

0

Repo Tool overview
Repo is a repository management tool that is built on top of Git. Repo unifies the many Git repositories when necessary, and automates parts of the development workflow. Repo is not meant to replace Git, only to make it easier to work with Git in the context of development.The repo command is an executable Python script that you can put anywhere in your path. In working with the source files, you will use Repo for across-network operations. For example, with a single Repo command you can download files from multiple repositories into your local working directory.
More details about repo tool is present at
https://source.android.com/source/developing.html
Step 1: Preparing the Build Environment
Install Repo
#Download the Repo script:
$ curl https://storage.googleapis.com/git-repo-downloads/repo > repo
#Make it executable:
$ chmod a+x repo
#Move it on to your local home directory path:
$ mv repo ~/bin/
#Add it to your path
$ PATH=$PATH:~/bin
#If it is correctly installed, you should see a Usage message when invoked with the help flag.
$ repo --help
Fetch all sources
Release 2017.1 and above :
#repo init to the project of desire
$ repo init -u git://github.com/Xilinx/yocto-manifests.git -b <current-release>
#repo sync to get all sources
$ repo sync
#repo start a branch
$ repo start <current-release> --all
Release 2016.3 or below :
#repo init to the project of desire
$ repo init -u git://github.com/Xilinx/yocto-manifests.git -m meta-petalinux.xml -b <current-release>
#repo sync to get all sources
$ repo sync
#repo start a branch
$ repo start <current-release> --all
where current-release is rel-v2016.3 or rel-v2016.1 etc
Source environment
#source the environment to build using bitbake
$ source setupsdk
# for 2016.1 and 2016.2 release use
$ source pkgsetup
Edit configuration files
You should be in the 'build' directory at this point. You may need to edit the following files in the 'conf' directory:
Edit bblayers.conf so that it has the appropriate layers for your build.
Edit local.conf to reflect your choices for the build. If using the sstate-cache downloaded above, you need these lines:
SSTATE_DIR ?= "${TOPDIR}/../sstate-rel-v2017.2/aarch64/sstate-cache"
DL_DIR ?= "${TOPDIR}/../sstate-rel-v2017.2/downloads"
Step 2: Build using bitbake
You can choose between 'petalinux-image', 'petalinux-image-minimal' and 'petalinux-image-full' below.
$ MACHINE=zynqmp-generic bitbake petalinux-image
$ MACHINE=zynq-generic bitbake petalinux-image
$ MACHINE=microblazeel-v10.0-bs-cmp-ml-generic bitbake petalinux-image
$ MACHINE=microblazeel-v10.0-bs-cmp-mh-div-generic bitbake petalinux-image
Similarly build for other machine (ZC702, ZC706 etc)
Release 2016.1 to 2016.4:
Below information is applicable only to Releases 2016.1 to 2016.4
Following has to be present in your configuration to use XIlinx SDK toolchain (local.conf or override.conf)
DISTRO = "petalinux"
PACKAGE_CLASSES = "package_rpm"
TCMODE = "external-xilinx"
XILINX_VER_MAIN = "<current-release>"
EXTERNAL_TOOLCHAIN_zynq = "<path-to-xilinx-SDK>/SDK/<current-version>/gnu/aarch32/lin/gcc-arm-linux-gnueabi"
EXTERNAL_TOOLCHAIN_microblaze = "<path-to-xilinx-SDK>/SDK/<current-version>/gnu/microblaze/linux_toolchain/lin32_le"
EXTERNAL_TOOLCHAIN_aarch64 = "<path-to-xilinx-SDK>/SDK/<current-version>/gnu/aarch64/lin/aarch64-linux"
XILINX_SDK_TOOLCHAIN = "<path-to-xilinx-SDK>/SDK/<current-version>"
<current-version> will be 2016.3, 2016.1 etc
<current-release> will be 2016.3, 2016.1 etc
Re-running bitbake
If you need to run bitbake again, for example if your build failed the first time, source setupsdk like in Step 1 and rerun bitbake
Related Links
Xilinx Yocto

ZU＋ Example - Deep Sleep

August 14, 2017, 4:27 pm

≫ Next: PetaLinux Yocto Tips

≪ Previous: Getting started with Yocto Xilinx layer

$

0

0

...

SDK (2017.1 release)
Petalinux (2017.1 release)
Known Issue
With production silicon, the PMU is driven by the SysOsc, which normally runs at 200 MHz. This is different from pre-production silicon where the PMU is driven by the 33 MHz PS Ref clock instead, and consumes much lower power. This means that for the production silicon to get to the target deep sleep power (35 mW), the SysMon must be powered down. Refer to this design example on how to power down the SysMon:
http://www.wiki.xilinx.com/ZU%EF%BC%8B+Example+-+Deep+Sleep+with+PS+SysMon+in+Sleep+Mode during deep sleep.
Vivado: Generate HDF with Isolation config
This section explains procedure to create new project in Vivado, isolation configuration and exporting bit-stream/HDF files.

PetaLinux Yocto Tips

August 14, 2017, 4:29 pm

≫ Next: reVISION Getting Started Guide 2017.2

≪ Previous: ZU＋ Example - Deep Sleep

$

0

0

...

FILES_${PN} = "${libdir}/*.so.* ${includedir}/*"
FILES_${PN}-dev = "${libdir}/*.so"

...

tools as
APP = sample
LIBSOURCES=*.c

...

}
FILES_${PN} += "sampleapp"

...

tools as
#include <stdio.h>
#include <SAMPLE/sample.h> // From above libs <TARGET_ROOTFS>/usr/lib/SAMPLE/sample.h

reVISION Getting Started Guide 2017.2

August 14, 2017, 8:54 pm

≫ Next: reVISION Getting Started Guide 2017.2

≪ Previous: PetaLinux Yocto Tips

$

0

0

{under.jpg}
This page is under construction until this banner has been removed.
1 Introduction
The Xilinx reVISION stack includes a broad range of development resources for platform, algorithm and application development. This includes support for the most popular neural networks including AlexNet, GoogLeNet, VGG, SSD, and FCN. Additionally, the stack provides library elements including pre-defined and optimized implementations for CNN network layers, required to build custom neural networks (DNN/CNN). The machine learning elements are complemented by a broad set of acceleration ready OpenCV functions for computer vision processing. For application level development, Xilinx supports industry standard frameworks and libraries including Caffe for machine learning and OpenCV for computer vision. The reVISION stack also includes development platforms from Xilinx and third parties, including various types of sensors. For more information go to the Xilinx reVISION webpage.
2 Overview
The below figure shows a block diagram of the ZCU102 reVISION architecture:
video sources (or capture pipelines) are highlighted in blue color
computer vision accelerators implemented as memory-to-memory (m2m) pipelines in red color and
video sinks (or output/display pipelines) in green color
{reVISION_bd.png}
A simple command line based application controls the design over a serial terminal emulator. It constructs a video pipeline graph consisting of one source, one accelerator (optional), and one sink. It is responsible for initializing the capture, m2m, and display pipelines as well as managing the video buffer flow through the pipeline stages.
2.1 Platform
The ZCU102 reVISION platform supports the following video interfaces:
Sources:
USB2/3 camera up to 1080p60 or stereo 1080p30
The USB controller is part of the processing system (PS). It uses the standard Linux Universal Video Class (UVC) driver.
HDMI Rx up to 4k60
The HDMI capture pipeline is implemented in the programmable logic (PL) and consists of HDMI Rx Subsystem, Video Processing Subsystem (Scaler only configuration), and Frame Buffer Write. The HDMI Rx subsystem receives and decodes the HDMI data stream from an HDMI source and converts it to AXI4-Stream. The Video Processing Subsystem converts the incoming color format (one of RGB, YUV444, YUV422) to YUV422 and optionally scales the image to the target resolution. The Frame Buffer Write IP writes the YUV422 stream to memory as packed YUYV format. The HDMI capture pipeline uses the V4L Linux framework.
MIPI CSI via optional FMC card up to 4k60
The MIPI capture pipeline is implemented in the PL and consists of Sony IMX274 image sensor, MIPI CSI2 Subsystem, Demosaic, Gamma, Video Processing Subsystem (CSC configuration), Video Processing Subsystem (Scaler only configuration), and Frame Buffer Write. The IMX274 image sensor provides raw image data over the camera sensor interface (CSI) link. The MIPI CSI2 Subsystem receives and decodes the incoming data stream to AXI4-Stream. The Demosaic IP converts the raw image format to RGB. The Gamma IP provides per-channel gamma correction functionality. The VPSS-CSC provides color correction functionality. The VPSS-Scaler converts the RGB image to YUV422. The Frame Buffer Write IP writes the YUV422 stream to memory as packed YUYV format. The MIPI capture pipeline uses the V4L Linux framework.
Sinks:
HDMI Tx up to 4k60
The HDMI display pipeline is implemented in the PL and consists of a Video Mixer and HDMI Tx Subsystem. The Video Mixer is configured to read one ARGB and two YUYV layers from memory. In the provided design examples, only a single YUYV layer is used. The video layers are then composed and alpha-blended into a single output frame which is sent to the HDMI Tx Subsystem via AXI4-Stream. The HDMI Tx Subsystem encodes the incoming video into an HDMI data stream and sends it to the HDMI display. The HDMI display pipeline uses the DRM/KMS Linux framework.
DP Tx up to 4k30
The DP display pipeline is configured for dual-lane mode and is part of the PS. It includes a simple two-layer blender with run-time programmable color format converters per layer. The two layers are always full screen matching the target display resolution. The DP display pipeline uses the DRM/KMS Linux framework.
2.2 Design Examples
The platform ships with 5 file I/O and 2 live I/O design examples demonstrating popular OpenCV functions accelerated on the programmable logic:
Live I/O:
Dense Optical Flow - requires LI-IMX274MIPI-FMC or HDMI source or See3CAM_CU30 USB camera
This algorithm uses two successive images in time, and calculates the direction and magnitude of motion at every pixel position in the image. The calculation is a simple implementation of the Lucas–Kanade method for optical flow estimation. The optical flow algorithm returns two signed numbers at each pixel position, representing up or down motion in the vertical direction, and left or right motion in the horizontal direction. The brightness of the false-color output, from black up to bright color, indicates the magnitude of the motion, and the color indicates the direction.
Stereo Vision (Depth Detection) - requires ZED USB stereo camera
This algorithm uses two side-by-side images from the stereo camera taken at the same moment in time, and calculates the depth, or distance from the camera, at every pixel position in the image. The stereo block-matching algorithm calculates depth based on binocular parallax, similar to the way human eyes perceive depth. The depth map is coded in false colors. Objects far away appear deep blue. Closer and closer objects appear in rainbow succession green, yellow, orange, red, purple and finally white, closest to the camera.
File I/O:
Bilateral Filter
Harris Filter
Dense Optical Flow
Stereo Vision (Depth Detection)
Warp Transformation
3 Software Tools and System Requirements
3.1 Hardware
Required:
ZCU102 Evaluation Board
rev 1.0 with ES2 silicon or
rev 1.0 with production silicon
Micro-USB cable, connected to laptop or desktop for the terminal emulator
SD card
Optional (only needed for live I/O examples):
Monitor with DisplayPort or HDMI input supporting one of the following resolutions:
3840x2160 or
1920x1080 or
1280x720
Display Port cable (DP certified) or HDMI cable
Leopard LI-IMX274MIPI-FMC
Stereolabs ZED USB stereo camera
e-con Systems See3CAM_CU30_CHL_TC USB camera
Xilinx USB3 micro-B adapter
adapter shipped with ZCU102 rev 1.0 + production silicon
adapter needs to be purchased separately from Whizz for ZCU102 rev 1.0 + ES2 silicon
HDMI video source with output supporting one of the following resolutions:
3840x2160 or
1920x1080 or
1280x720
3.2 Software
Required:
Linux or Windows host machine for tool flow tutorials (see UG1238 for supported OS version).
SDSoC Development Environment version 2017.1 (see UG1238 for installation instructions)
Serial terminal emulator e.g. teraterm
ZCU102 Production Silicon reVISION Package: Includes SDSoC platform, design examples,and pre-built SD card images OR
ZCU102 ES2 Silicon reVISION Package: Includes SDSoC platform, design examples,and pre-built SD card images.
3.3 Licensing
Important: Certain material in this reference design is separately licensed by third parties and may be subject to the GNU General Public License version 2, the GNU Lesser General License version 2.1, or other licenses.
The Third Party Library Sources zip file provides a copy of separately licensed material that is not included in the reference design.
You will need only the SDSoC license to build the design. You can evaluate for 60-days or purchase it here.
Steps to generate the license:
Log in here with your work E-mail address (If you do not yet have an account, follow the steps under Create Account)
Generate a license from “Create New Licenses” by checking "SDSoC Environment, 60 Day Evaluation License"
{license.png}
Under system information, give the host details.
Proceed until you get the license agreement and accept it.
The License (.lic file) will be sent to the email-id mentioned in the login details.
Copy the license file locally and give the same path in the SDSoC license manager.
3.4 Compatibility
The reference design has been tested successfully with the following user-supplied components.
Monitors:
Make/Model
Native Resolution
Viewsonic VP2780-4K
3840x2160
Acer S277HK
3840x2160
Dell U2414H
1920x1080
HDMI Sources:
Make/Model
Resolutions
Nvidia Shield TV
3840x2160, 1920x1080
OTT TV BOX M8N
3840x2160, 1920x1080, 1280x720
Roku 2 XS
1920x1080, 1280x720
TVix Slim S1 Multimedia Player
1920x1080, 1280x720
USB3 Cameras:
Make/Model
Resolutions
ZED stereo camera
3840x1080, 2560x720
See3CAM_CU30
1920x1080, 1280x720
DisplayPort Cables:
Cable Matters DisplayPort Cable-E342987
Monster Advanced DisplayPort Cable-E194698
4 Design File Hierarchy
The Zynq UltraScale+ MPSoC reVISION Platform zip file is released with the binary and source files required to create Xilinx SDx projects and build the sample applications. The provided samples include 5 file I/O examples and 2 live I/O examples. The file I/O examples read an input image file and produce an output image file whereas the live I/O examples take live video input from a video source and output live video on a display.
For the advanced user who wants to create their own platform, a PetaLinux BSP is included as well as the sources for the video_lib library which provides APIs to interface with video sources, sinks, and accelerators. Basic README files are provided in the respective directories.
Pre-built SD card images are included that enable the user to run the two live I/O examples applications on the ZCU102 board.
The top-level directory structure:
zcu102_[es2_]reVISION
├── hw
│ ├── vivado
│ └── zcu102_[es2_]reVISION.hpfm
├── IMPORTANT_NOTICE_CONCERNING_THIRD_PARTY_CONTENT.txt
├── README.txt
├── samples
│ ├── file_IO
│ │ ├── bilateral_fileio
│ │ ├── harris_fileio
│ │ ├── opticalflow_fileio
│ │ ├── steoreolbm_fileio
│ │ └── warptransform_fileio
│ └── live_IO
│ ├── optical_flow
│ └── stereo_vision
├── sd_card
│ ├── optical_flow
│ └── stereo_vision
├── sw
│ ├── aarch64-linux-gnu
│ ├── boot
│ ├── image
│ ├── petalinux_bsp
│ ├── prebuilt
│ ├── video_lib
│ └── zcu102_[es2_]reVISION.spfm
└── zcu102_[es2_]reVISION.xpfm
5 Installation and Operating Instructions
5.1 Board Setup
Required:
Connect power supply to the 12V power connector.
Display
Connect a DisplayPort cable to DisplayPort connector on the board; connect the other end to a monitor OR
Connect an HDMI cable to HDMI Tx connector (top) on the board; connect the other end to a monitor
Note: Certain monitors have multiple HDMI ports supporting different HDMI standards. Make sure you choose an HDMI 2.0 capable port (if available) for 4k60 performance
Note: Make sure you only connect either DP or HDMI Tx on the board, not both, otherwise the design might malfunction.
Connect micro-USB cable to the USB-UART connector; use the following settings for your terminal emulator:
Baud Rate: 115200
Data: 8 bit
Parity: None
Stop: 1 bit
Flow Control: None
Insert SD card (FAT formatted) with pre-built image copied from one of the following directories:
Optical Flow: zcu102_[es2_]reVISION/sd_card/optical_flow
Stereo Block Matching: zcu102_[es2_]reVISION/sd_card/stereo_vision
Optional:
Connect an HDMI cable to HDMI Rx connector (bottom) on the board; connect the other end to an HDMI source
Connect the See3CAM_CU30 or ZED USB camera to the USB3 micro-AB connector via the Xilinx USB3 micro-B adapter
Connect the LI-IMX274MIPI-FMC module to the HPC0 FMC connector on the board
Note: Vadj needs to be set to 1.8V (default) for correct operation of the daughter card. If the FMC card does not seem functional, please follow the instructions explained in Answer Record AR67308 for rev 1.0 and beyond to check and/or set Vadj.
Jumpers & Switches:
Set boot mode to SD card
SW6[1:4]: on,off,off,off
Configure USB jumpers for host mode
J110: 2-3
J109: 1-2
J112: 2-3
J7: 1-2
J113: 1-2
{zcu102_reVISION_2017.1.png}
5.2 Run the Application
Download and unzip the reference design zip file matching your silicon version (ES2 vs production). If you are using Windows, we recommend using the 7zip utility. Select Auto Rename when prompted to resolve file name conflicts, see figure below.
{rv_unzip_7zip.png}
Tutorial - run the Dense Optical Flow sample application:
Copy all files from the release package directory
./zcu102_[es2_]reVISION/sd_card/optical_flow
onto your SD card and insert it into the SD card slot on the zcu102 board.
Power on the board; make sure the large "INIT_B" LED and the "DONE" LED next to it go green after a few seconds.
Control the system via your computer: start a terminal session using TeraTerm, PuTTY or the like. Use the settings mentioned above under Board Setup. With the USB-UART cable connected and the board powered up, you can locate the COM port that is responsive. You'll see several pages of Linux bootstrap and debug messages scroll by, finishing at the linux command line prompt:
root@plnx_aarch64:~#
The files on your sd_card are present in directory /media/card/. That directory is already specified in the PATH environment variable, so you are not required to "cd" to that directory.
Run the Optical Flow app:
root@plnx_aarch64:~# of2.elf
The system initializes and displays the command line menu. The menu appears, allowing you to select the video input source, and to turn on/off the Optical Flow processing.
Three things may be controlled, either from the menu, or from command-line switches when the app in launched.
Video Input Source - MIPI FMC camera, HDMI input or USB camera. The default is the MIPI camera.
Filter mode - OFF (video pass-through) or HW (hardware accelerated optical flow processing). The default is OFF.
Video Output - Display Port or HDMI output. The default is Display Port.
So, if you run the app as shown above, with no command-line switches, you'll get the defaults: MIPI camera input passed through to Display Port output. You should see live video from your MIPI camera on the output monitor. The menu displayed is shown below.
Video Control application:
------------------------
Display resolution: 3840x2160
--------------- Select Video Source ---------------
1 : MIPI CSI2 Rx (*)
2 : HDMI Input
3 : USB Webcam
4 : Virtual Video Device
--------------- Select Filter Type ----------------
5 : Optical Flow (*)
--------------- Toggle Filter Mode ----------------
6 : Filter OFF/HW (off)
--------------- Exit Application ------------------
0 : Exit
Enter your choice :
Activate the HW accelerated Optical Flow processing with command "6" <enter>. The "Filter Mode" changes to "hardware," and the false-color optical flow output appears on the monitor.
Note that the menu numbers may vary, depending on the number of video sources plugged into your board.
Enter your choice : 6
...
--------------- Toggle Filter Mode ----------------
4 : Filter OFF/HW (hardware)
...
Enter your choice :
When Optical Flow processing is activated, the output shows bright colors where there is the greatest motion from one input frame to the next, and black where there is no motion. The optical flow algorithm returns 2 signed numbers at each pixel position, representing up or down motion in the vertical direction, and left or right motion in the horizontal direction. The brightness of the output, from black up to bright color, indicates the magnitude of the motion, and the color indicates the direction. +/- vertical motion is mapped onto the V color component, and +/- horizontal motion is mapped onto the U color component. To see a nice graph of the range of colors this produces, refer to the wikipedia page on YUV colors.
Repeating the command "6" turns off the processing.
Select the HDMI input using the command "2".
Again, toggle processing on/off using command "6".
Switch back to MIPI input using the command "1".
Again, toggle processing on/off using command "6".
Exit the app with command "0".
A number of command-line switches are available for selecting video input, filter mode, and video output when the app is launched. To do this you must know the ID number of the choices for each one of these catagories. Note that these IDs differ from the menu command numbers discussed above.
Query the available video Sources with switch "-S"
# of2.elf -S
The system responds with the ID numbers of the video Sources
VIDEO SOURCE ID
MIPI CSI2 Rx 0
HDMI Input 1
USB Webcam 2
Virtual Video Device 3
Query the available filter Modes with switch "-M"
# of2.elf -M
The system responds with the ID numbers of the filter Modes
FILTER MODE ID
off 0
hardware 2
These ID numbers are used with the "-s" and "-m" switches (lower case) on the command line to select the video input and the filter mode when the app is launched.
Launch the app selecting the HDMI video input - the system comes up with HDMI input, in pass-through, to Display Port output.
# of2.elf -s 1
Launch the app selecting the HDMI input, mode "hardware" - the system comes up with HDMI input, optical flow activated, to Display Port output.
# of2.elf -s 1 -m 2
Launch the app selecting the MIPI input, mode "hardware" - the system comes up with MIPI input, optical flow activated, to Display Port output.
# of2.elf -s 0 -m 2
To control the video output, the command line switch is "-d". ID "0" selects Display Port output, and ID "1" selects HDMI output. There is no query command for these IDs, because they do not vary.
Launch the app selecting the HDMI input, optical flow activated, HDMI output.
# of2.elf -s 1 -m 2 -d 1
These switches are independent of each other and may be used in any combination and in any order. If you do not specify a switch, the default ID "0" is used" : i.e. "MIPI" input, filter mode "off", "Display Port" output.
The desired image resolution in terms of width and height (in pixels) of the input video may be selected with the "-i" switch. In general the output resolution is the same as the input resolution. If the resolution is possible, meaning the input source is capable of supplying video in that resolution, it will use that resolution. Otherwise is will refuse to run and display a message to that effect.
Launch the app selecting the MIPI input, in 1920x1080 resolution, pass-through, to Display Port. Note that resolution is specified as WIDTHxHEIGHT with no spaces.
# of2.elf -i 1920x1080
Launch the app selecting the HDMI input, in 1920x1080 resolution, optical flow active, to HDMI output.
# of2.elf -s 1 -i 1920x1080 -m 2 -d 1
Note that the USB camera mentioned in section 3.4 above, the See3CAM_CU30 from e-con Systems, has an unusual pixel format called "UYVY". The pixel format describes the ordering of the luma and chroma data stored in memory for each pixel. By far the most common 4:2:2 pixel format is "YUYV" which is the default for the reVISION platform and for the MIPI and HDMI video input sources. To use the USB See3CAM_CU30 camera as source for Optical Flow, this special pixel format must be specified by attaching "@UYVY" to the input resolution WIDTHxHEIGHT string.
Start the app in 1920x1080 resolution, in "UYVY" format, from the USB video input
# of2.elf -s 2 -i 1920x1080@UYVY
Note that ONLY Display Port output (not HDMI output) will function with the UYVY format. Also, if you attempt to select the MIPI or HDMI inputs with the UYVY format, the system will refuse to do so.
Run the Stereo Vision sample application:
Copy all files from the release package directory
./zcu102_es2_reVISION/sd_card/stereo_vision
onto your SD card and insert it into the SD card slot on the zcu102 board.
In general, the steps and details explained above in the Optical Flow tutorial apply here in the same way.
However, the stereo vision demo is special in several ways. First, you MUST use the ZED stereo camera connected to the USB video input. Second, and quite particular to this app, the width of the input image resolution is twice the width of the output resolution. The input actually consists of two images side-by-side, the synchronized left and right stereo input supplied by the camera. Two cases are possible: 2560x720 in to 1280x720 out, and 3840x1080 in to 1920x1080 out. For this we need to use the input resolution switch "-i" and the output resolution switch "-o". The default 3840x2160 output resolution is not supported by the Stereo Vision app. Also, you may NOT toggle between modes OFF and HW in this case, because in the pass-through case the output and input must be the same resolution, not true when Stereo Vision processing is active.
The other special thing about this app is that a configuration file corresponding to the camera you have connected to your system must be used. Each StereoLabs ZED camera has a unique parameters file associated with it. This text file comes from StereoLabs, and must be present on the SD Card for the Stereo Vision demo to work properly. You need the file unique to your camera, identified by its Serial Number (found on the ZED camera box and also on a black tag near the USB plug of the ZED camera itself). This number will be, e.g., S/N 000012345. The parameter file for that camera would be named SN12345.conf. To download your parameter file, enter this URL into your browser:
http://calib.stereolabs.com/?SN=12345 (using your serial number in place of 12345)
This will download your configuration file to your computer. Copy this file to the SD Card root directory. Also, you must specify this file on the command line when you run the app, as :
--filter-sv-cam-params /media/card/SN12345.conf
The stereo vision app is called stv.elf. Launch the app selecting the USB input, in 1920x1080 output resolution, stereo vision active, to HDMI output.
# stv.elf -s 2 -m 2 -d 1 -i 3840x1080 -o 1920x1080 -filter-sv-cam-params /media/card/SN12345.conf
Launch the app selecting the USB input, in 1280x720 output resolution, stereo vision active, to HDMI output.
# stv.elf -s 2 -m 2 -d 1 -i 2560x720 -o 1280x720 -filter-sv-cam-params /media/card/SN12345.conf
The stereo block-matching algorithm calculates depth based on binocular parallax, similar to the way human eyes perceive depth. The depth map is coded in false colors. Objects far away appear deep blue. Closer and closer objects appear in rainbow succession green, yellow, orange, red, purple and finally white at about two feet from the camera in the 720p case, and about five feet away in the 1080p case. Any object closer than that cannot be tracked, and smooth areas with no texture in the image cannot be tracked, and show up as black. Areas with a lot of detail (especially with lots of vertical edges) are tracked best. It is normal that a large area on the left is black - this is 128 pixels wide, representing the range of the horizontal search for best match between the right and left binocular images.
Commandline Options
The full list of supported command line switches is:
-d, --dri-card N DRI card number N (default N=0)
-h, --help Show this help screen
-i, --input-format WxH[@FMT] Input Width'x'Height@Fmt
-o, --output-format WxH[-HZ][@FMT] Output Width'x'Height-Hz@Fmt
-f, --fps N/D Capture frame rate
-I, --non-interactive Non-interactive mode
-S, --list-sources List video sources
-L, --list-filters List filters
-M, --list-filter-modes List filter modes
-s, --video-source Video source ID
-l, --filter Set filter
-m, --filter-mode Set filter mode
-P, --plane <id>[:<w>x<h>[+<x>+<y>]] Use specific plane
-b, --buffer-count Number of frame buffers
--filter-sv-cam-params File for stereo camera parameters
The dri-card switch should be set corresponding to the connected monitor, where 0 corresponds to Display Port and 1 to HDMI.
The list commands - S, M and L, output a list of sources, modes and filters, and their IDs that then can be set directly from the commandline using a corresponding s, m or l option. Example list output:
VIDEO SOURCE ID
MIPI CSI2 Rx 0
HDMI Input 1
USB Webcam 2
USB Webcam 3
Virtual Video De 4
FILTER ID
Optical Flow 0
FILTER MODE ID
off 0
hardware 2
The input and output options allow specifying the resolution and pixel format for source and sink device. The pixel format needs to be specified as fourcc code.
The plane option allows selecting a specific plane and its resolution, which does not have to match the screen resolution. I.e. if the resolution provided in to the output option is greater (in both dimensions) than the resolution provided to the plane option, the input video (which has to match the plane resolution) is displayed in a window on the screen. This enables pass-through of the Zed camera video on HDMI monitors (the Display Port hardware does not support cases where plane resolution != output resolution).
A list of valid planes and their supported video formats can be obtained through
modetest -M xilinx_drm -D amba:xilinx_drm_hdmi -p
CRTCs:
id fb pos size
30 35 (0,0) (3840x2160)
3840x2160 30 3840 4016 4104 4400 2160 2168 2178 2250 flags: phsync, pvsync; type: driver
props:
Planes:
id crtc fb CRTC x,y x,y gamma size possible crtcs
26 0 0 0,0 0,0 0 0x00000001
formats: BG24
props:
5 type:
flags: immutable enum
enums: Overlay=0 Primary=1 Cursor=2
value: 0
27 0 0 0,0 0,0 0 0x00000001
formats: YUYV
props:
5 type:
flags: immutable enum
enums: Overlay=0 Primary=1 Cursor=2
value: 0
24 alpha:
flags: range
values: 0 256
value: 256
28 0 0 0,0 0,0 0 0x00000001
formats: YUYV
props:
5 type:
flags: immutable enum
enums: Overlay=0 Primary=1 Cursor=2
value: 0
24 alpha:
flags: range
values: 0 256
value: 256
29 30 35 0,0 0,0 0 0x00000001
formats: AR24
props:
5 type:
flags: immutable enum
enums: Overlay=0 Primary=1 Cursor=2
value: 1
24 alpha:
flags: range
values: 0 256
value: 256
25 bg_color:
flags: range
values: 0 16777215
value: 16711680
Run the File I/O Examples
Please refer to UG1233, page 8 for instructions.
Note: The SD card file system is mounted as read-only. To re-mount the file-system as read-write which is required to save the output image back to the SD card file system, run the following command before executing the sample elf file:
# remount
6 Tool Flow Tutorials
Build the Optical Flow sample application:
Firstly, the SDx Development Environment, version 2017.1, must be installed and working on your host computer, either the Linux or the Windows version. Further, it is assumed that you have already downloaded zcu102_es2_reVISION.zip and extracted its contents. The top-level directory name of the platform is 'zcu102_es2_reVISION'.
Before starting SDx, set the SYSROOT environment variable to point to the Linux root file system delivered with the EV platform, for example:
Linux:
export SYSROOT=<local>/zcu102_es2_reVISION/sw/aarch64-linux-gnu/sysroot
Windows:
Start->Control Panel->System->Advanced->Environment Variables
Create environment variable SYSROOT with value <local>\zcu102_es2_reVISION\sw\aarch64-linux-gnu\sysroot
The following steps are virtually identical whether you are running the Linux or Windows version of SDx 2017.1.
Start SDx and create a new workspace. Make sure you use the same shell to run SDx as the one where you have set $SYSROOT.
Close the Welcome screen and select 'File'→ 'New'→ 'Xilinx SDx Project'... from the menu bar. This brings up the Create a New SDx Project dialog box. Enter Project name "of2" meaning "optical flow, 2 pixels/clock".
{create_new.png}
Leave the "Use default location" box checked, hit Next>, this opens the "Choose Hardware Platform" page.
Select the platform. The very first time you do this for a new workspace, you must hit Add Custom Platform..., and browse to ./zcu102-es2_reVISION, hit OK, note that "zcu102-es2_reVISION (custom)" now appears in the Name column.
{choose_hw.png}
Select your newly added custom platform "zcu102_es2_reVISION (custom)", hit Next>, this opens the "Choose Software Platform and Target CPU" page.
{choose_sw.png}
Leave everything as is, hit Next>, this opens the "Templates" page.
Select Dense Optical Flow (2PPC), hit Finish
{templates.png}
The dialog box closes, and you now see the SDx Project Settings pane in the center of the SDx GUI. Notice the progress bar in the lower right border of the pane, saying "C/C++ Indexer" - wait a few moments for this to finish. Locate the "Active build configuration:" in the upper right corner of the pane, which says "Debug" - click it and select Release. Your window should now look something like this:
{sdx_project.png}
In the left hand "Project Explorer" pane, select the of2 project, click right on it, then select Build Project. In the small Build Project dialog that opens, you may hit the "Run in Background" button. That causes the small dialog box to disappear, though you can still see a progress icon in the lower right part of the GUI, showing that work is in progress. Select the Console tab in the lower central pane of the GUI to observe the steps of the build process as it progresses. The build process may take tens of minutes, up to several hours, depending on the power of your host machine, whether you are running on Linux or Windows, and of course the complexity of your design. By far the most time is spent processing the routines that have been tagged for realization in hardware - note the "HW functions" window in the lower part of the SDx Project Settings pane. In our example above, the routines read_optflow_input, xFDenseNonPyrLKOpticalFlow, and write_optflow_output are tagged to be built in hardware. The synthesis of the C code found in these routines into RTL, and the Placement and Routing of that RTL into the programmable logic in the Zynq MPSoC, are the steps that take most of the time.
Once the Build completes, you will find an sd_card directory has been created, with all the files you need to copy to your SD card and run your application on the zcu102 board, as explained in section 5.2 above. This directory is found in:
.\<workspace>\of2\Release\sd_card
Build the Stereo Vision sample application:
The Stereo Vision project may be created and built in the same way just explained for the Optical Flow project. All the steps are analogous. For the Project name, use stv.
In the Templates dialog box, select the Stereo Vision template.
7 Other Information
7.1 Known Issues
SDSoC accelerator code runs very slowly in pure software implementation when Debug configuration is used.
Solution: Set project build configurations to Release which sets sdsoc compiler to optimize most (-O3).
When building the optical_flow sample app, you will see a number of warnings, such as: "WARNING: [SDSoC 0-0] No size pragma specified for pointer argument f0Stream".
Solution: These can be ignored.
SDSoC reports the design did no meet timing constraints when running under Windows.
Solution: Clean the project and build it again.
7.2 Limitations
Make sure you don't have both HDMI Tx and DP Tx connected at the same time, otherwise the design might malfunction.
HDMI Rx:
Does not support YUV 4:2:0 input.
Does not support HDCP encrypted input.
Does not support hotplug or dynamic resolution changes while the application is running.
8 Support
To obtain technical support for this reference design, go to the:
Xilinx Answers Database to locate answers to known issues
Xilinx Community Forums to ask questions or discuss technical details and issues. Please make sure to browse the existing topics first before filing a new topic. If you do file a new topic, make sure it is filed in the sub-forum that best describes your issue or question e.g. Embedded Linux for any Linux related questions. Please include "ZCU102 reVISION" and the release version in the topic name along with a brief summary of the issue.
9 References
Additional material that is not hosted on the wiki:
Base TRD User Guide: Contains information about system, software and hardware architecture which is similar to the reVISION platform.
Xilinx OpenCV User Guide: Contains detailed description of Xilinx OpenCV functions and file I/O design examples.
Xilinx Fast OpenCV on Github
Xilinx Linux Drivers:
Frame Buffer Write
Video PHY
Xilinx V4L Pipeline
MIPI CSI
VPSS CSC
VPSS Scaler
Demosaic
Gamma
HDMI Rx
Xilinx DRM
Video Mixer
HDMI Tx
DP159
SI5324

reVISION Getting Started Guide 2017.2

August 14, 2017, 8:58 pm

≫ Next: reVISION Getting Started Guide 2017.2

≪ Previous: reVISION Getting Started Guide 2017.2

$

0

0

---

reVISION Getting Started Guide 2017.2

August 14, 2017, 9:00 pm

≫ Next: reVISION Getting Started Guide 2017.2

≪ Previous: reVISION Getting Started Guide 2017.2

$

0

0

...

Connect the See3CAM_CU30 or ZED USB camera to the USB3 micro-AB connector via the Xilinx USB3 micro-B adapter
Connect the LI-IMX274MIPI-FMC module to the HPC0 FMC connector on the board

...

set to 1.8V (default)1.2V for correct
Jumpers & Switches:
Set boot mode to SD card

reVISION Getting Started Guide 2017.2

August 14, 2017, 9:06 pm

≫ Next: reVISION Getting Started Guide 2017.2

≪ Previous: reVISION Getting Started Guide 2017.2

$

0

0

...

zcu102_[es2_]reVISION
├── hw
│├── vivado
│└── zcu102_[es2_]reVISION.hpfmzcu102_[es2_]rv_ss.dsa
├── IMPORTANT_NOTICE_CONCERNING_THIRD_PARTY_CONTENT.txt
├── README.txt

...

│ └── stereo_vision
├── sw
│ ├── aarch64-linux-gnua53_linux
│ |├── boot
│ |├── image
│ |├── petalinux_bspinc
│ |├── prebuiltlib
│ | └── qemu
│ ├── petalinu_bsp
│ ├── sysroot
│ ├── video_lib
│ └── zcu102_[es2_]reVISION.spfmzcu102_[es2_]rv_ss.spfm
└── zcu102_[es2_]reVISION.xpfmzcu102_[es2_]rv_ss.xpfm
5 Installation and Operating Instructions
5.1 Board Setup

reVISION Getting Started Guide 2017.2

August 14, 2017, 9:07 pm

≫ Next: reVISION Getting Started Guide

≪ Previous: reVISION Getting Started Guide 2017.2

$

0

0

reVISION Getting Started Guide

August 14, 2017, 9:08 pm

≫ Next: reVISION Getting Started Guide 2017.2

≪ Previous: reVISION Getting Started Guide 2017.2

$

0

0

...

Connect the See3CAM_CU30 or ZED USB camera to the USB3 micro-AB connector via the Xilinx USB3 micro-B adapter
Connect the LI-IMX274MIPI-FMC module to the HPC0 FMC connector on the board

...

set to 1.8V (default)1.2V for correct
Jumpers & Switches:
Set boot mode to SD card

reVISION Getting Started Guide 2017.2

August 14, 2017, 9:13 pm

≫ Next: reVISION Getting Started Guide 2017.2

≪ Previous: reVISION Getting Started Guide

$

0

0

...

SDSoC Development Environment version 2017.1 (see UG1238 for installation instructions)
Serial terminal emulator e.g. teraterm
7zip utility to extract the design zip file
ZCU102 Production Silicon reVISION Package: Includes SDSoC platform, design examples,and pre-built SD card images OR
ZCU102 ES2 Silicon reVISION Package: Includes SDSoC platform, design examples,and pre-built SD card images.

...

{zcu102_reVISION_2017.1.png}
5.2 Run the Application

...

vs production). If you are using Windows, we recommend using the 7zip utility. Select Auto Rename when prompted to resolve file name conflicts, see figure below.
{rv_unzip_7zip.png}
Tutorial - run the Dense Optical Flow sample application:
Copy all files from the release package directory

reVISION Getting Started Guide 2017.2

August 14, 2017, 9:16 pm

≫ Next: reVISION Getting Started Guide 2017.2

≪ Previous: reVISION Getting Started Guide 2017.2

$

0

0

...

5.2 Run the Application
Download and unzip the reference design zip file matching your silicon version (ES2 vs production).
Tutorial - runRun the Dense
Copy all files from the release package directory
./zcu102_[es2_]reVISION/sd_card/optical_flow

...

Run the File I/O Examples
Please refer to UG1233, page 8 for instructions.
Note: The SD card file system is mounted as read-only. To re-mount the file-system as read-write which is required to save the output image back to the SD card file system, run the following command before executing the sample elf file:
# remount
6 Tool Flow Tutorials
Build the Optical Flow sample application:

...

already downloaded zcu102_es2_reVISION.zipzcu102_[es2_]rv_ss.zip and extracted

...

platform is 'zcu102_es2_reVISION'.'zcu102_[es2_]rv_ss'.
Before starting SDx, set the SYSROOT environment variable to point to the Linux root file system delivered with the EV platform, for example:
Linux:
export SYSROOT=<local>/zcu102_es2_reVISION/sw/aarch64-linux-gnu/sysrootSYSROOT=<local>/zcu102_[es2_]rv_ss/sw/sysroot
Windows:
Start->Control Panel->System->Advanced->Environment Variables

...

with value <local>\zcu102_es2_reVISION\sw\aarch64-linux-gnu\sysroot<local>\zcu102_[es2_]rv_ss\sw\sysroot
The following steps are virtually identical whether you are running the Linux or Windows version of SDx 2017.1.
Start SDx and create a new workspace. Make sure you use the same shell to run SDx as the one where you have set $SYSROOT.

reVISION Getting Started Guide 2017.2

August 14, 2017, 9:20 pm

≫ Next: reVISION Getting Started Guide 2017.2

≪ Previous: reVISION Getting Started Guide 2017.2

$

0

0

...

The Xilinx reVISION stack includes a broad range of development resources for platform, algorithm and application development. This includes support for the most popular neural networks including AlexNet, GoogLeNet, VGG, SSD, and FCN. Additionally, the stack provides library elements including pre-defined and optimized implementations for CNN network layers, required to build custom neural networks (DNN/CNN). The machine learning elements are complemented by a broad set of acceleration ready OpenCV functions for computer vision processing. For application level development, Xilinx supports industry standard frameworks and libraries including Caffe for machine learning and OpenCV for computer vision. The reVISION stack also includes development platforms from Xilinx and third parties, including various types of sensors. For more information go to the Xilinx reVISION webpage.
2 Overview

...

ZCU102 reVISION architecture:single sensor design:
video sources (or capture pipelines) are highlighted in blue color
computer vision accelerators implemented as memory-to-memory (m2m) pipelines in red color and

...

Pre-built SD card images are included that enable the user to run the two live I/O examples applications on the ZCU102 board.
The top-level directory structure:
zcu102_[es2_]reVISIONzcu102_[es2_]rv_ss
├── hw
│ └── zcu102_[es2_]rv_ss.dsa

...

Flow Control: None
Insert SD card (FAT formatted) with pre-built image copied from one of the following directories:
Optical Flow: zcu102_[es2_]reVISION/sd_card/optical_flowzcu102_[es2_]rv_ss/sd_card/optical_flow
Stereo Block Matching: zcu102_[es2_]reVISION/sd_card/stereo_visionzcu102_[es2_]rv_ss/sd_card/stereo_vision
Optional:
Connect an HDMI cable to HDMI Rx connector (bottom) on the board; connect the other end to an HDMI source

...

Run the Dense Optical Flow sample application:
Copy all files from the release package directory
./zcu102_[es2_]reVISION/sd_card/optical_flow./zcu102_[es2_]rv_ss/sd_card/optical_flow
onto your SD card and insert it into the SD card slot on the zcu102 board.
Power on the board; make sure the large "INIT_B" LED and the "DONE" LED next to it go green after a few seconds.

...

Run the Stereo Vision sample application:
Copy all files from the release package directory
./zcu102_es2_reVISION/sd_card/stereo_vision./zcu102_es2_rv_ss/sd_card/stereo_vision
onto your SD card and insert it into the SD card slot on the zcu102 board.
In general, the steps and details explained above in the Optical Flow tutorial apply here in the same way.

...

{create_new.png}
Leave the "Use default location" box checked, hit Next>, this opens the "Choose Hardware Platform" page.

...

browse to ./zcu102-es2_reVISION,./zcu102_[es2_]rv_ss, hit OK, note that "zcu102-es2_reVISION"zcu102_[es2_]rv_ss (custom)" now
{choose_hw.png}

...

custom platform "zcu102_es2_reVISION"zcu102_[es2_]rv_ss (custom)", hit
{choose_sw.png}
Leave everything as is, hit Next>, this opens the "Templates" page.

---

reVISION Getting Started Guide 2017.2

August 14, 2017, 9:27 pm

≫ Next: reVISION Getting Started Guide 2017.2

≪ Previous: reVISION Getting Started Guide 2017.2

$

0

0

...

5.2 Run the Application
Download and unzip the reference design zip file matching your silicon version (ES2 vs production).

...

Flow sample application:application
Copy all files from the release package directory
./zcu102_[es2_]rv_ss/sd_card/optical_flow

...

# of2.elf -s 2 -i 1920x1080@UYVY
Note that ONLY Display Port output (not HDMI output) will function with the UYVY format. Also, if you attempt to select the MIPI or HDMI inputs with the UYVY format, the system will refuse to do so.

...

Vision sample application:application
Copy all files from the release package directory
./zcu102_es2_rv_ss/sd_card/stereo_vision

...

Please refer to UG1233, page 8 for instructions.
6 Tool Flow Tutorials
Build the Optical Flow sample application:
Firstly, the SDx Development Environment, version 2017.1, must be installed and working on your host computer, either the Linux or the Windows version. Further, it is assumed that you have already downloaded zcu102_[es2_]rv_ss.zip and extracted its contents. The top-level directory name of the platform is 'zcu102_[es2_]rv_ss'.
Before starting SDx, set the SYSROOT environment variable to point to the Linux root file system delivered with the EV platform, for example:

...

Start->Control Panel->System->Advanced->Environment Variables
Create environment variable SYSROOT with value <local>\zcu102_[es2_]rv_ss\sw\sysroot
6.1 Build the Optical Flow sample application
The following steps are virtually identical whether you are running the Linux or Windows version of SDx 2017.1.
Start SDx and create a new workspace. Make sure you use the same shell to run SDx as the one where you have set $SYSROOT.

...

Once the Build completes, you will find an sd_card directory has been created, with all the files you need to copy to your SD card and run your application on the zcu102 board, as explained in section 5.2 above. This directory is found in:
.\<workspace>\of2\Release\sd_card
Build6.2 Build the Stereo Vision sample application:application
The Stereo Vision project may be created and built in the same way just explained for the Optical Flow project. All the steps are analogous. For the Project name, use stv.
In the Templates dialog box, select the Stereo Vision template.
6.3 Build the File IO sample applications
TODO
7 Other Information
7.1 Known Issues

reVISION Getting Started Guide 2017.2

August 14, 2017, 9:29 pm

≫ Next: reVISION Getting Started Guide 2017.2

≪ Previous: reVISION Getting Started Guide 2017.2

$

0

0

...

Required:
Linux or Windows host machine for tool flow tutorials (see UG1238 for supported OS version).

...

Environment version 2017.12017.2 (see UG1238
Serial terminal emulator e.g. teraterm
7zip utility to extract the design zip file

...

Please refer to UG1233, page 8 for instructions.
6 Tool Flow Tutorials

...

Environment, version 2017.1,2017.2, must be
Before starting SDx, set the SYSROOT environment variable to point to the Linux root file system delivered with the EV platform, for example:
Linux:

...

Create environment variable SYSROOT with value <local>\zcu102_[es2_]rv_ss\sw\sysroot
6.1 Build the Optical Flow sample application

...

version of SDx 2017.1.SDx.
Start SDx and create a new workspace. Make sure you use the same shell to run SDx as the one where you have set $SYSROOT.
Close the Welcome screen and select 'File'→ 'New'→ 'Xilinx SDx Project'... from the menu bar. This brings up the Create a New SDx Project dialog box. Enter Project name "of2" meaning "optical flow, 2 pixels/clock".

reVISION Getting Started Guide 2017.2

August 15, 2017, 10:01 am

≫ Next: reVISION Getting Started Guide 2017.2

≪ Previous: reVISION Getting Started Guide 2017.2

$

0

0

...

SDSoC Development Environment version 2017.2 (see UG1238 for installation instructions)
Serial terminal emulator e.g. teraterm

...

design zip filefile. Note: Other zip utilities might produce incorrect results!
ZCU102 Production Silicon reVISION Package:with production silicon: /proj/fisdata/fisusr/sandboxes/ckohn/2017.2/rc5/zcu102_rv_ss_rc5.zip: Includes SDSoC platform, design examples,andexamples, and pre-built SD

...

OR
ZCU102 with ES2 Silicon reVISION Package:silicon: /proj/fisdata/fisusr/sandboxes/ckohn/2017.2/rc5/zcu102_es2_rv_ss_rc5.zip: Includes SDSoC platform, design examples,andexamples, and pre-built SD
3.3 Licensing
Important: Certain material in this reference design is separately licensed by third parties and may be subject to the GNU General Public License version 2, the GNU Lesser General License version 2.1, or other licenses.

reVISION Getting Started Guide 2017.2

August 15, 2017, 10:03 am

≫ Next: 7zip-2.jpg

≪ Previous: reVISION Getting Started Guide 2017.2

$

0

0

...

Serial terminal emulator e.g. teraterm
7zip utility to extract the design zip file. Note: Other zip utilities might produce incorrect results!

...

images OR TODO: Update with public link
ZCU102 with

...

card images. TODO: Update with public link
3.3 Licensing
Important: Certain material in this reference design is separately licensed by third parties and may be subject to the GNU General Public License version 2, the GNU Lesser General License version 2.1, or other licenses.

7zip-2.jpg

August 15, 2017, 10:23 am

≫ Next: 7zip-1.jpg

≪ Previous: reVISION Getting Started Guide 2017.2

$

0

0

Uploaded