Getting Started Guide for Xilinx Zynq Ultrascale+
On this page you are going to find all the necessary information to start from scratch to use the RidgeRun SDK on your Ultrascale+ zynq ZCU102 board.
- First section, configure serial access, tftp and NFS.
- Second sections, instructions on how to install required software like Xilinx SDK, RidgeRun EVAL/Professional SDK.
- Third section, SDK configuration.
Basic preliminary work
Setting up serial access to the Linux console
You can use termnet to control u-boot and linux. For this purpose, the board needs to be connected to the same network as the host computer. This is useful because the board doesn't have to be directly connected to the PC containing the SDK.
If you use the serial port to control u-boot and Linux. The picocom terminal emulator work well for this purpose.
Setting up a TFTP server
If you are planning to use the SDK's installer to install images generated by the SDK in SPI-NOR, installing a TFTP server you will speed up downloads to the target hardware by using TFTP.
Setting up a NFS server
For application development, it is convenient to use root NFS mount file system for the target hardware. This allows you to rebuild your application on the host and immediately run the application on the target hardware with no interveining steps. You host PC needs to be configured as a NFS server for this in order to work properly.
Installing Toolchains and XSDK
Need to download Xilinx SDK "XSDK" for getting toolchain and image generator software. XSDK can be downloaded from: https://www.xilinx.com/support/download/index.html/content/xilinx/en/downloadNav/embedded-design-tools.html
Select SDK 2016.3: Linux Self Extracting Web Installer You need to complete Xilinx registration process in order to download. File is around 1.3Gb
Change permissions to XSDK installer and execute:
cd ~/Downloads/ chmod 777 Xilinx_SDK_2016.3_1011_1_Lin64.bin ./Xilinx_SDK_2016.3_1011_1_Lin64.bin
Install XSDK 2016.3 at /opt/Xilinx/Downloads.
XSDK Install process images:
After installing a directory structure similar to the one shown below will be obtained:
ls /opt/Xilinx/SDK/2016.3 bin data doc eclipse gnu lib scripts settings64.csh settings64.sh tps
Ultrascale+ File System
Ridgerun SDK is able to use different types of file systems:
- Basic file system created by Ridgerun SDK
- Ridgerun SDK is in charge of building basic applications to deploy this filesystem.
- This is a limited fs, but SDK has all Ridgerun classes to add more applications if needed.
- Very small footprint.
- File system with Busybox and Gstreamer.
- Basic Debian precompiled file system created by Ridgerun SDK (Still not available)
- Ridgerun provides a debian precompiled file system that is able to get packages with apt-get for aarch64
- Able to get applications from Debian repositories.
- Small footprint, allows the user to install packages as required
- Precompiled file system for ARM
- User just needs to indicate path for file system.
- Just available for Network File System (NFS).
- Any ARM file system can be used, but a precompiled and very complete File System can be obtained from: http://www.wiki.xilinx.com/Zynq+UltraScalePlus+MPSoC+-+Ubuntu+Desktop+Step+by+Step+Guide
- Instructions for using precompiled File System:
cd ~/Downloads unzip Ubuntu_Source_Release.zip chown $USER /opt/ mkdir /opt/ridgerun/downloads/ mkdir /opt/Xilinx/UbuntuFS cd /opt/Xilinx/UbuntuFS cpio -idv < ~/Downloads/Ubuntu_Source_Release/Linux_Files/rootfs_cpio/ZCU102_Ubuntu_2_rootfs.cpio
At the end you will obtain FS at the directory:
/opt/Xilinx/UbuntuFS$ ls @! dev home lost+found proc run sbin usr bin etc include media qt run_cube_del.sh srv var boot ffmpeg lib mnt QT_cube run_cube.sh sys cube_new glmark2.png log opt root run_desktop.sh tmp
Ridgerun SDK config, build and install
Please skip below two steps (3.1 and 3.2) in TOC and jump to 3.3 if you have purchased a Professional SDK.
Getting the RidgeRun's EVAL SDK Irazu
If you want to get the RidgeRun's EVAL SDK Irazu you need to go to our Evaluation SDK Download Link and select the Evaluation SDK you need. You will be asked for your email address and some information. Once you have submitted the required information you will receive an email with the following information:
Sequence of evaluation sdk download events:
You have to follow the steps below :
When you select and click on the name of evaluation sdk you want to download, shopping cart page will display with the price $0.00 (for eval sdk's)
-> click on 'Go to Checkout'. It will display 'Your Shopping Bag' page
-> click on 'Checkout'. You will get a form to enter your email id and other info
-> click on 'Continue'. It will display a 'Place Order' page
-> click on 'Place Order'. And then Please check your email with a link to download the tar file for the evaluation SDK you have selected.
Installing the EVAL SDK version
RidgeRun delivers the SDK in either two ways: a tar file for x86 platforms, or for customers with a established development relationship through a custom SCM (typically GIT) repository. If you are using a shared SCM repository, please contact RidgeRun for a detailed instructions.
Listed below are the minimum recommended requirements for installing and using the RidgeRun SDK:
- A host computer with a 686 or better family processor
- 1 GB free hard disk space
- A Linux distribution configured on the host computer.
- Target hardware for the SDK
- Optional: a network card installed and configured on the host computer
- Optional: Internet connection for SDK updates
Once you have downloaded the tar file of the evaluation SDK you can untar it by running the following command:
tar -xvzf <name of the tar file downloaded>.tar.gz
You may find it convenient to untar the evaluation SDK more than once. For example, you might want one version to be unmodified and another version to be your working development directory. RidgeRun suggests you untar the SDK development directories in your $HOME/work/ directory. When you have more than one development directory installed, just remember to have the DEVDIR shell variable set properly. To set the DEVDIR shell variable use the `make env` command specified at RidgeRun_Irazu_SDK_User_Guide#Build_SDK
On the rest of this document, we refer as $DEVDIR to the path where the RidgeRun Eval SDK for Ultrascale+ Zynq ZCU102 EVM is installed.
Installing the Professional SDK version
When all the purchase process is done, RidgeRun will provide you a GitHub repository access. For that, the GitHub user ID and other information might be requested. Once you provide that information, you must clone the given repository URL, using the next command:
git clone email@example.com:RidgeRun/<customer>.git
This would have the proper <customer> space modified. With this, you will have the SDK installed on the directory you were when executed the clone command.
RidgeRun suggests you install the SDK development directories in your $HOME/work/ directory. When you have more than one development directory installed, just remember to have the DEVDIR shell variable set properly. To set the DEVDIR shell variable use the `make env` command specified at RidgeRun_Irazu_SDK_User_Guide#Build_SDK
On the rest of this document, we refer as $DEVDIR to the path where the RidgeRun Professional SDK for Ultrascale+ Zynq ZCU102 EVM is installed.
1. Set your environment variables
cd $DEVDIR `make env`
2. Start build process
cd $DEVDIR make
Configuration menu will be deployed
By default the SDK is configured for creating a demo SD card image with NFS. Exit and save configuration, SDK will continue building.
After build process finishes, use make install in order to create SD card image at $(DEVDIR)/images/
And follow instructions to store sdcard.img at SD:
You can use the image file to flash an SD card: 1. Plug your SD card (say it is device /dev/sdX) 2. Unmount it ('sudo umount' should help) 3. Flash: sudo dd bs=1M if=$(DEVDIR)/images/sdcard.img of=/dev/sdX Installation complete