Ettus E3xx Getting Started Guide
User Manual:
Open the PDF directly: View PDF 
.
Page Count: 20
| Download | |
| Open PDF In Browser | View PDF |
OpenCPI
Ettus E3XX Getting Started Guide
Version 1.4
Figure 1: Top View (E310)
1
Ettus E3XX Getting Started Guide
ANGRYVIPER Team
Revision History
Revision
v1.3.1-E3XX
v1.4
Description of Change
Initial Release
Updated for Release
Date
3/2018
9/2018
2
Ettus E3XX Getting Started Guide
ANGRYVIPER Team
Table of Contents
1 References
4
2 Overview
5
3 Prerequisites
3.1 Installation of provided projects: core, assets and
3.2 Vendor Software Setup . . . . . . . . . . . . . . .
3.3 Building Required Projects . . . . . . . . . . . .
3.4 Hardware Setup . . . . . . . . . . . . . . . . . . .
4 SD
4.1
4.2
4.3
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
5
6
6
6
Card Setup
Make a backup image of factory SD card (assumes Linux host)
Format the SD card . . . . . . . . . . . . . . . . . . . . . . . .
Copy OpenCPI files to SD card . . . . . . . . . . . . . . . . . .
4.3.1 Copy Standalone Mode specific files to SD card . . . . .
4.3.2 Copy Network Mode specific files to SD card . . . . . .
4.3.3 SD Card Source . . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
8
8
8
8
8
8
8
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
9
. 9
. 9
. 9
. 10
5 Script Setup
5.1 Setting up the Network and Standalone Mode
5.1.1 Network Mode . . . . . . . . . . . . .
5.1.2 Standalone Mode . . . . . . . . . . . .
5.2 Setup system time reference . . . . . . . . . .
bsp_e310
. . . . . .
. . . . . .
. . . . . .
scripts
. . . .
. . . .
. . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6 Development Host Setup - Network Mode ONLY
11
6.1 Network Mounting Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
6.1.1 CentOS 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
6.1.2 CentOS 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
7 Configuring the runtime environment on the platform
13
7.1 Network Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
7.2 Standalone Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
8 Build an application
15
9 Run an Application
15
9.1 Network Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
9.2 Run an Application in Standalone Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
10 Running Reference Applications
18
Appendices
19
A Generating Boot Artifacts
19
A.1 BOOT.bin and u-boot.img . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
A.2 devicetree.dtb . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
A.3 uImage and uramdisk.image.gz . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
B Copying only required files to SD card
B.1 Copy embedded OS and boot files to SD card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B.2 Files needed for Standalone Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B.3 Files needed for Network Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3
20
20
20
20
Ettus E3XX Getting Started Guide
1
ANGRYVIPER Team
References
This document assumes a basic understanding of the Linux command line (or “shell”) environment. The reference(s)
in Table 1 can be used as an overview of OpenCPI and may prove useful.
Title
Getting Started
Installation Guide
Acronyms and Definitions
Overview
Published By
ANGRYVIPER Team
ANGRYVIPER Team
ANGRYVIPER Team
OpenCPI
Table 1: References
4
Link
Getting_Started.pdf
RPM_Installation_Guide.pdf
Acronyms_and_Definitions.pdf
http://opencpi.github.io/
Overview.pdf
Ettus E3XX Getting Started Guide
2
ANGRYVIPER Team
Overview
This document provides steps for configuring a factory provided Ettus USRP E310 with the OpenCPI runtime
environment for executing applications, configuring a development system to build OpenCPI bitstreams targeting
the e3xx platform, and examples of executing applications on the OpenCPI configured E310.
3
Prerequisites
This guide assumes that, at a minimum, the following RPMs are installed:
RPM Name
All prerequisite RPMs
angryviper-ide-*.x86 64.rpm
opencpi-*.x86_64.rpm
opencpi-devel-*.x86_64.rpm
opencpi-sw-platform-xilinx13_4-*.noarch.rpm
opencpi-hw-platform-e3xx-*.noarch.rpm
3.1
Description
These packages have OpenCPI-specific patches and are provided
as RPMs. This packaging ensures they will not conflict with
other installed copies by using a nonstandard installation location of /opt/opencpi/prerequisites.
The ANGRYVIPER IDE (Eclipse with plugins). See RPM
Installation Guide.pdf, Appendix D for an alternative method
to set up the IDE using an existing Eclipse installation.
Base installation RPM includes the runtime portion of the
Component Development Kit (CDK) and the source for the
ocpi.core and ocpi.assets Projects containing framework essential components, workers, platforms, etc.
Additional header files and scripts for developing new assets as
HDL and/or RCC.
Additional files necessary to build the framework targeting specific RCC/software platforms, independent of the final deployed
hardware.
Additional files necessary to build the framework targeting specific hard-ware platform "X" when running RCC platform "Y"
("Y" can be "no sw"). This RPM also includes hardware-specific
SD Card images when applicable.
Installation of provided projects: core, assets and bsp_e310
This guide assumes the user has executed ocpi-copy-projects, accepting the default settings, to copy and register the
core, assets, and bsp_e310 projects from the /opt/opencpi/projects for building bitstreams for the E310. Reference
the Getting Started Guide for details on ocpi-copy-projects. Although the projects are registered by
ocpi-copy-projects, changes to the registry can be made via ocpidev un/register project or the ANGRYVIPER
GUI.
$ ocpi-copy-projects
...
$ ls ~/ocpi_projects
assets bsp_e310 core
$ ocpidev show registry
Project registry is located at: /opt/opencpi/cdk/../project-registry
---------------------------------------------------------------------------------------| Project Package-ID | Path to Project
| Valid/Exists |
| ------------------ | --------------| ------------ |
| ocpi.core
| /home//ocpi_projects/core
| True
|
| ocpi.assets
| /home//ocpi_projects/assets
| True
|
| ocpi.bsp.e310
| /home//ocpi_projects/bsp_e310
| True
|
----------------------------------------------------------------------------------------
5
Ettus E3XX Getting Started Guide
3.2
ANGRYVIPER Team
Vendor Software Setup
The platform that is expected to be used is the Ettus Research/National Instruments Universal Software Radio
Peripheral (USRP) E310 (or E3XX) SDR (e.g. e3xx). This OpenCPI-enabled platform provides the capability of
deploying hardware and software workers while using Xilinx’s 13.4 distribution of Linux.
The synthesizers and cross-compilers required to build HDL and RCC Workers for this Platform are installed by
following the instructions found in the OpenCPI FPGA Vendor Tools Installation Guide. This document assumes
that the user has installed the appropriate versions of Vivado and the Xilinx SDK.
3.3
Building Required Projects
The core, assets, and bsp_e310 projects must be built in a specific order for this platform. This section outlines
how to build the relevant projects and provides the commands to do so.
For this document, the projects should be built as follows:
1. Build core for the xilinx13_4 RCC Platform and the e3xx HDL Platform, but omit assemblies
2. Build assets for the xilinx13_4 RCC Platform and the e3xx HDL Platform, but omit assemblies
3. Build the bsp_e310 project for these same platforms
4. Build the testbias assembly from the assets project. This will be used later in this guide.
Once the HDL Platform is built in the BSP project, assemblies can be built for that HDL platform
$
$
$
$
$
cd /home//ocpi_projects/ && \
ocpidev build -d core --rcc-platform xilinx13_4 --hdl-platform e3xx --no-assemblies && \
ocpidev build -d assets --rcc-platform xilinx13_4 --hdl-platform e3xx --no-assemblies && \
ocpidev build -d bsp_e310 --rcc-platform xilinx13_4 --hdl-platform e3xx && \
ocpidev build -d assets hdl assembly testbias --hdl-platform e3xx;
Note: replace “” with your username in the commands above.
Each of these build commands can also be performed via the ANGRYVIPER IDE as follows:
To perform this operation within the IDE:
1. Open the ANGRYVIPER Perspective
2. Select the asset from OpenCPI Project View
3. Import to AV Operations Panel using “>” button
4. Select the RCC and/or HDL platforms for the build (use
Ctrl
for multiple selection)
5. Click “Build”
See the ANGRYVIPER Team’s Getting Started Guide for additional information concerning the use of ocpidev
and the ANGRYVIPER IDE to build OpenCPI assets.
3.4
Hardware Setup
• Ettus USRP E3XX
It is expected that this SDR package includes a power supply, micro-USB to USB cable and standard SD card
(4GB or larger).
OpenCPI has been tested on the Ettus USRP E310.
The micro-USB serial port located on the back E310 labeled CONSOLE (Figure 2) can be used to access the
serial connection with the processor.
6
Ettus E3XX Getting Started Guide
ANGRYVIPER Team
Figure 2: Back Panel
• Ethernet cable: An Ethernet port is available on the E310 (Figure 2) and is required when the Network
mode (discussed later) environment is used. The OpenCPI BSP for the E310 is configured for DHCP.
Figure 3: Front Panel
• Access to a network which supports DHCP. (Network Mode)
• SD card: As mentioned earlier, a 4GB or larger SD card should come with the SDR. The bootable SD card
slot is located on the front of the unit (Figure 3) and ejects by gently pushing it in and releasing.
• SD card reader
• Further information on front panel: Also found on the front panel of the SDR are six labeled SMB (50
Ohm) connectors: TRX-A, RX2-A, RX2-B, TRX-B, GPS, and SYNC (Figure 3). The upper connections are
7
Ettus E3XX Getting Started Guide
ANGRYVIPER Team
split into two individual channels referred to as “Front End A” and “Front End B.” Specific details can be
found in the vendor manuals.
4
SD Card Setup
4.1
Make a backup image of factory SD card (assumes Linux host)
This section provides the steps for creating an SD card backup image. The subsequent subsections assume the SD
card is empty.
• Determine the device file name for the SD card by executing dmesg command below. It will likely be something
like /dev/sdb or /dev/mmcblk0.
$ dmesg | tail -n 15
• Run the following dd command to make a backup image, where DEVICENAME was determined above. This
step should take ∼ 15 minutes depending on the card size.
$ dd if=DEVICENAME of=backup.image
To restore the card back to the original contents, run the command “dd of=DEVICENAME if=backup.image” (Do
not do this step unless you want the original contents back on the SD card.)
4.2
Format the SD card
• Format the SD card with a single FAT32 partition.
4.3
Copy OpenCPI files to SD card
This section provides the simplest instructions for copying files over to the SD card. Appendix B contains more
involved instructions for copying only the necessary files to the SD card for each mode.
WARNING: The user must ensure that the contents of the SD, match the version of the OpenCPI release that the
artifacts were built against.
When using the factory SD card, all files can be ignored or deleted. Any files/directories copied to SD card will
appear at /mnt/card on the E310.
Copy the following directory onto the SD card:
$ cp -r /opt/opencpi/cdk/e3xx/sdcard-xilinx13_4/* /run/media///
4.3.1
Copy Standalone Mode specific files to SD card
Copy the testbias bitstream into the artifacts directory:
$ cp /home/ocpi_projects/assets/hdl/assemblies/testbias/container-testbias_e3xx/\
target-zynq/testbias_e3xx_base.bit.gz /run/media///opencpi/xilinx13_4/artifacts
4.3.2
Copy Network Mode specific files to SD card
No additional files required for Network Mode.
4.3.3
SD Card Source
The final SD Card artifacts are distributed in /opt/opencpi/cdk/e3xx/ via RPM as noted previously. The end user
is not required nor expected to generate the files, but the process is documented below in Appendix A.
8
Ettus E3XX Getting Started Guide
5
ANGRYVIPER Team
Script Setup
There are two type of setups or modes for running applications on any embedded radio: Network and Standalone.
In Network mode, a development system hosts the OpenCPI tree as an NFS server to the E310 which is an NFS
client. This configuration provides quick and dynamic access to all of OpenCPI, and presumably any applications,
components and bitstreams. In Standalone mode, all the artifacts are located on the SDR’s local storage (e.g. SD
card) and no network connection is required. This may be more suited for deployment scenarios in which network
connection is not possible or practical. Network mode is generally preferred during the development process.
For both Network and Standalone mode, the following step is necessary:
1) Enter the mounted SD card’s opencpi directory
$ cd /run/media///opencpi/
5.1
Setting up the Network and Standalone Mode scripts
For each mode, a startup script is used to configure the environment of the embedded system. The OpenCPI
framework provides a default script for each mode. The default scripts are to be copied, modified per the user’s
requirements.
5.1.1
Network Mode
1) Make a copy of the default script for editing
$ cp /run/media///opencpi/default_mynetsetup.sh \
/run/media///opencpi/mynetsetup.sh
2) Edit the copy
1. In mynetsetup.sh, uncomment the following lines which are necessary for mounting core, assets, and bsp_
e310 projects:
mkdir
mount
mkdir
mount
mkdir
mount
-p
-t
-p
-t
-p
-t
/mnt/ocpi_core
nfs -o udp,nolock,soft,intr $1:/home//ocpi_projects/core /mnt/ocpi_core
/mnt/ocpi_assets
nfs -o udp,nolock,soft,intr $1:/home//ocpi_projects/assets /mnt/ocpi_assets
/mnt/bsp_e310
nfs -o udp,nolock,soft,intr $1:/home//ocpi_projects/assets /mnt/bsp_e310
2. Edit /home//ocpi_projects/core and /home//ocpi_projects/assets to reflect the paths to
the core, assets, and bsp_e310 projects on the host, for example:
mkdir
mount
mkdir
mount
mkdir
mount
5.1.2
-p
-t
-p
-t
-p
-t
/mnt/ocpi_core
nfs -o udp,nolock,soft,intr $1:/home/johndoe/ocpi_projects/core /mnt/ocpi_core
/mnt/ocpi_assets
nfs -o udp,nolock,soft,intr $1:/home/johndoe/ocpi_projects/assets /mnt/ocpi_assets
/mnt/bsp_e310
nfs -o udp,nolock,soft,intr $1:/home/johndoe/ocpi_projects/assets /mnt/bsp_e310
Standalone Mode
In this mode, all OpenCPI artifacts that are required to run any application on the E310 must be copied onto the
SD card. Building the provided projects to obtain such artifacts is discussed in Section 3.3. Once the artifacts have
been created, they must be copied to the SD card in Section 4. In general, any required .so (RCC workers),
.bit.gz (hdl assemblies), and application XMLs or executables must be copied to the SD card.
1) Make a copy of the default script for editing
9
Ettus E3XX Getting Started Guide
ANGRYVIPER Team
$ cp /run/media///opencpi/default_mysetup.sh \
/run/media///opencpi/mysetup.sh
2) Edit the copy
Unlike Network mode, there is no required modifications to this script.
3) Copy any additional artifacts to SD card’s opencpi/artifacts/ directory
5.2
Setup system time reference
If Linux system time is not required to be accurate, this step may be skipped.
For either Network or Standalone mode, the following settings that are passed by mynetsetup.sh/mysetup.sh to
the zynq_net_setup.sh/zynq_setup.sh scripts may require modification:
• Identify the system that is to be used as a time server, where the default is “time.nist.gov”. A valid time
server must support RFC-868.
• Identify the current timezone description, where the default is “EST5EDT,M3.2.0,M11.1.0”. Change this if
required for the local timezone. See man tzset on the host PC for more information.
• If a time server is not required, or cannot connect to a time server, the user is required to manually set the
time at start up. Use the date command to manually set the Linux system time. See man date on the host
PC for more information.
10
Ettus E3XX Getting Started Guide
6
ANGRYVIPER Team
Development Host Setup - Network Mode ONLY
6.1
Network Mounting Mode
The NFS server needs to be enabled on the host in order to run the SDR in Network Mode. The following sections
are directions on how to do this for both CentOS 6 and CentOS 7 host operating systems.
6.1.1
CentOS 6
From the host, install the necessary tools using yum:
%
%
%
%
sudo
sudo
sudo
sudo
yum install nfs-utils nfs-utils-lib
chkconfig nfs on
service rpcbind start
service nfs start
From the host, add the following lines to the bottom of /etc/exports and change “XX.XX.XX.XX/MM” to a valid
netmask for the DHCP range that the SDR will be set to for your network (e.g. 192.168.0.0/16).
% sudo vi /etc/exports
/opt/opencpi XX.XX.XX.XX/MM(rw,sync,no_root_squash,no_subtree_check)
XX.XX.XX.XX/MM(rw,sync,no_root_squash,no_subtree_check)
XX.XX.XX.XX/MM(rw,sync,no_root_squash,no_subtree_check)
% sudo exportfs -av
From the host, restart the services that have modified for the changes to take effect:
% sudo service nfs start
6.1.2
CentOS 7
From the host, install the necessary tools using yum:
% sudo yum install nfs-utils
1
From the host, allow NFS past SELinux2 :
% sudo setsebool -P nfs_export_all_rw 1
% sudo setsebool -P use_nfs_home_dirs 1
From the host, allow NFS past the firewall:
%
%
%
%
%
sudo
sudo
sudo
sudo
sudo
firewall-cmd
firewall-cmd
firewall-cmd
firewall-cmd
firewall-cmd
--permanent
--permanent
--permanent
--permanent
--reload
--zone=public
--zone=public
--zone=public
--zone=public
--add-service=nfs
--add-port=2049/udp
--add-service=mountd
--add-service=rpc-bind
Define the export by creating a new file that has the extension “exports”. If it does not have that extension, it
will be ignored. Add the following lines to that file and replace “XX.XX.XX.XX/MM” with a valid netmask for the
DHCP range that the SDR will be set to for your network (e.g. 192.168.0.0/16).
% sudo vi /etc/exports.d/user_ocpi.exports
/opt/opencpi XX.XX.XX.XX/MM(rw,sync,no_root_squash,crossmnt)
/home/user/ocpi_projects/core XX.XX.XX.XX/MM(rw,sync,no_root_squash,crossmnt)
/home/user/ocpi_projects/assets XX.XX.XX.XX/MM(rw,sync,no_root_squash,crossmnt)
1 nfs-utils-lib was rolled into nfs-utils starting with CentOS 7.2, if using eariler versions of CentOS 7, nfs-utils-lib will need
to be explicitly installed
2 You can use getsebool to see if these values are already set before attempting to set them. Some security tools may interpret the
change attempt as a system attack.
11
Ettus E3XX Getting Started Guide
ANGRYVIPER Team
If the file system that you are mounting is XFS, then each mount needs to have a unique fsid defined. Instead, use:
% sudo vi /etc/exports.d/user_ocpi.exports
/opt/opencpi XX.XX.XX.XX/MM(rw,sync,no_root_squash,crossmnt,fsid=33)
/home/user/ocpi_projects/core XX.XX.XX.XX/MM(rw,sync,no_root_squash,crossmnt,fsid=34)
/home/user/ocpi_projects/assets XX.XX.XX.XX/MM(rw,sync,no_root_squash,crossmnt,fsid=35)
Restart the services that have modified for the changes to take effect:
%
%
%
%
%
%
%
%
sudo
sudo
sudo
sudo
sudo
sudo
sudo
sudo
systemctl
systemctl
systemctl
systemctl
systemctl
systemctl
systemctl
systemctl
enable rpcbind
enable nfs-server
enable nfs-lock
enable nfs-idmap
restart rpcbind
restart nfs-server
restart nfs-lock
restart nfs-idmap
* Note: Some of the “enable” commands may fail based on your package selection, but should not cause any problems.
NOTE: You will need to add the ocpi.bsp.e310 project to your list of exports (in /etc/exports.d/user_ocpi.
exports).
12
Ettus E3XX Getting Started Guide
7
ANGRYVIPER Team
Configuring the runtime environment on the platform
7.1
Network Mode
1. Plug in an Ethernet cable to a network configured for DHCP
2. Ensure a micro-USB to USB cable is connected between the E310’s serial port and development host
3. Apply power to the E310
4. Use a serial terminal application to establish a serial connection, for example:
$ sudo screen /dev/ttyUSB0 115200
5. After a successful boot to PetaLinux, login to the system, using “root” for user name and password
6. Setup the OpenCPI environment on remote system
Each time the SDR is booted, the OpenCPI environment must be setup. By sourcing the mynetsetup.sh
script, the remote system’s environment is configured for OpenCPI and NFS directories are mounted for
Network mode.3 . The user must provide the network address of the development system to the script as its
only argument:
$ . /mnt/card/opencpi/mynetsetup.sh XX.XX.XX.XX
where XX.XX.XX.XX is the IP address of the NFS host (i.e. that development host, e.g. 192.168.1.10). A
successful run should output the following:
An IP address was detected.
Setting the time from time server: time.nist.gov
My IP address is: XX.XX.XX.XX, and my hostname is: zynq
Running login script. OCPI_CDK_DIR is now /mnt/net/cdk.
Executing /home/root/.profile
No reserved DMA memory found on the linux boot command line.
The mdev config has no OpenCPI rules. We will add them to /etc/mdev.conf
NET: Registered protocol family 12
Driver loaded successfully.
OpenCPI ready for zynq.
Discovering available containers...
Available containers:
# Model Platform
OS
OS-Version Arch
Name
0 hdl
e3xx
PL:0
1 rcc
xilinx13_4
linux x13_4
arm
rcc0
Note: If the output includes “rdate: bad address ‘time.nist.gov’”, comment out the rdate command in
zynq_net_setup.sh, reboot the radio, and start back at step 1 of this section.
3 This
script calls the zynq_net_setup.sh script, which should not be modifiable by the user.
13
Ettus E3XX Getting Started Guide
7.2
ANGRYVIPER Team
Standalone Mode
1. (Not required for OpenCPI in this mode) Plug in an Ethernet cable to a network configured for DHCP
2. Ensure a micro-USB to USB cable is connected between the E310’s serial port and development host
3. Apply power to the E310
4. Use a serial terminal application to establish a serial connection, for example:
$ sudo screen /dev/ttyUSB0 115200
5. After a successful boot to PetaLinux, login to the system, using “root” for user name and password
6. WARNING: Applications (including XML-only ones) fail if there is not an IP address assigned to the platform,
even when in “standalone mode.” When the Ethernet port is not connected to a network configured with
DHCP, a temporary IP address must be set:
$ ifconfig eth0 192.168.244.244
7. Setup the OpenCPI environment on remote system
Each time the SDR is booted, the OpenCPI environment must be setup. By sourcing the mysetup.sh script,
the remote system’s environment is configured for OpenCPI 4 . There are no arguments for this script.
$ . /mnt/card/opencpi/mysetup.sh
A successful run should output the following:
Attempting to set the time from time server: time.nist.gov
Setting the time from time server: time.nist.gov
Running login script. OCPI_CDK_DIR is now /mnt/card/opencpi.
Executing /home/root/.profile
No reserved DMA memory found on the linux boot command line.
The mdev config has no OpenCPI rules. We will add them to /etc/mdev.conf
NET: Registered protocol family 12
Driver loaded successfully.
OpenCPI ready for zynq.
Discovering available containers...
Available containers:
# Model Platform
OS
OS-Version Arch
Name
0 hdl
e3xx
PL:0
1 rcc
xilinx13_4
linux x13_4
arm
rcc0
Note: If the output includes “rdate: bad address ‘time.nist.gov’”, comment out the rdate command in
zynq_setup.sh, reboot the radio, and start back at step 1 of this section.
4 This
script calls the zynq_setup.sh script, which should not be modifiable by the user.
14
Ettus E3XX Getting Started Guide
8
ANGRYVIPER Team
Build an application
The setup of the platform can be verified by running an application that uses both RCC and HDL workers. A
simple application that requires two RCC and one HDL worker is located in assets/applications/bias.xml, but
only the RCC artifacts are provided with the installation of RPMs, and are availble on the SD card (Standard
Mode) or mounted CDK directory (Network Mode). The remaining task is to build an assembly, or bitstream for
loading the FPGA, which contains the HDL worker.
9
9.1
Run an Application
Network Mode
The default setup script sets the OCPI_LIBRARY_PATH variable to include the RCC workers that are required to
execute the application, but it must be updated to include to the assembly bitstream that was built. After running
the mynetsetup.sh script, navigate to /mnt/ocpi_assets/applications, then update the OCPI_LIBRARY_PATH
variable using the following command:
$ export OCPI_LIBRARY_PATH=/mnt/ocpi_assets/artifacts:/mnt/ocpi_core/artifacts
Run the application using the following command:
$ ocpirun -v -t 1 -d -m bias=hdl bias.xml
The output should be similar to:
Available containers are: 0: PL:0 [model: hdl os: platform: e3xx], 1: rcc0 [model: rcc os: linux
֒→ platform: xilinx13_4]
Actual deployment is:
Instance 0 file_read (spec ocpi.core.file_read) on rcc container 1: rcc0, using file_read in /
֒→ mnt/ocpi_core/artifacts/ocpi.core.file_read.rcc.0.xilinx13_4.so dated Fri Sep 28
֒→ 18:18:26 2018
Instance 1 bias (spec ocpi.core.bias) on hdl container 0: PL:0, using bias_vhdl/a/bias_vhdl in
֒→ /mnt/ocpi_assets/artifacts/ocpi.assets.testbias_e3xx_base.hdl.0.e3xx.gz dated Tue Oct
֒→ 2 11:59:53 2018
Instance 2 file_write (spec ocpi.core.file_write) on rcc container 1: rcc0, using file_write
֒→ in /mnt/ocpi_core/artifacts/ocpi.core.file_write.rcc.0.xilinx13_4.so dated Fri Sep 28
֒→ 18:18:31 2018
Application XML parsed and deployments (containers and artifacts) chosen
Application established: containers, workers, connections all created
Communication with the application established
Dump of all initial property values:
Property 0: file_read.fileName = "test.input" (cached)
Property 1: file_read.messagesInFile = "false" (cached)
Property 2: file_read.opcode = "0" (cached)
Property 3: file_read.messageSize = "16"
Property 4: file_read.granularity = "4" (cached)
Property 5: file_read.repeat = ""
Property 6: file_read.bytesRead = "0"
Property 7: file_read.messagesWritten = "0"
Property 8: file_read.suppressEOF = "false"
Property 9: file_read.badMessage = "false"
Property 10: file_read.ocpi_debug = "false" (parameter)
Property 11: file_read.ocpi_endian = "little" (parameter)
Property 12: bias.biasValue = "16909060" (cached)
Property 13: bias.ocpi_debug = "false" (parameter)
Property 14: bias.ocpi_endian = "little" (parameter)
Property 15: bias.test64 = "0"
Property 16: file_write.fileName = "test.output" (cached)
Property 17: file_write.messagesInFile = "false" (cached)
15
Ettus E3XX Getting Started Guide
ANGRYVIPER Team
Property 18: file_write.bytesWritten = "0"
Property 19: file_write.messagesWritten = "0"
Property 20: file_write.stopOnEOF = "true" (cached)
Property 21: file_write.ocpi_debug = "false" (parameter)
Property 22: file_write.ocpi_endian = "little" (parameter)
Application started/running
Waiting up to 1 seconds for application to finish
Application finished
Dump of all final property values:
Property 3: file_read.messageSize = "16"
Property 5: file_read.repeat = ""
Property 6: file_read.bytesRead = "4000"
Property 7: file_read.messagesWritten = "251"
Property 8: file_read.suppressEOF = "false"
Property 9: file_read.badMessage = "false"
Property 15: bias.test64 = "0"
Property 18: file_write.bytesWritten = "4000"
Property 19: file_write.messagesWritten = "250"
Run the following command to view the input:
$ hexdump test.input | less
The output should look like the following:
0000000
0000010
0000020
0000030
0000040
0000050
0000060
0000070
0000080
0000090
00000a0
00000b0
00000c0
00000d0
00000e0
00000f0
0000100
0000110
0000120
0000130
0000140
0000150
0000160
0000
0004
0008
000c
0010
0014
0018
001c
0020
0024
0028
002c
0030
0034
0038
003c
0040
0044
0048
004c
0050
0054
0058
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0001
0005
0009
000d
0011
0015
0019
001d
0021
0025
0029
002d
0031
0035
0039
003d
0041
0045
0049
004d
0051
0055
0059
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0002
0006
000a
000e
0012
0016
001a
001e
0022
0026
002a
002e
0032
0036
003a
003e
0042
0046
004a
004e
0052
0056
005a
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0003
0007
000b
000f
0013
0017
001b
001f
0023
0027
002b
002f
0033
0037
003b
003f
0043
0047
004b
004f
0053
0057
005b
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
Run the following command to view the output:
$ hexdump test.output | less
The output should look like the following:
0000000
0000010
0000020
0000030
0304
0308
030c
0310
0102
0102
0102
0102
0305
0309
030d
0311
0102
0102
0102
0102
0306
030a
030e
0312
0102
0102
0102
0102
0307
030b
030f
0313
0102
0102
0102
0102
16
Ettus E3XX Getting Started Guide
0000040
0000050
0000060
0000070
0000080
0000090
00000a0
00000b0
00000c0
00000d0
00000e0
00000f0
0000100
0000110
0000120
0000130
0000140
0000150
0000160
0314
0318
031c
0320
0324
0328
032c
0330
0334
0338
033c
0340
0344
0348
034c
0350
0354
0358
035c
0102
0102
0102
0102
0102
0102
0102
0102
0102
0102
0102
0102
0102
0102
0102
0102
0102
0102
0102
0315
0319
031d
0321
0325
0329
032d
0331
0335
0339
033d
0341
0345
0349
034d
0351
0355
0359
035d
0102
0102
0102
0102
0102
0102
0102
0102
0102
0102
0102
0102
0102
0102
0102
0102
0102
0102
0102
0316
031a
031e
0322
0326
032a
032e
0332
0336
033a
033e
0342
0346
034a
034e
0352
0356
035a
035e
ANGRYVIPER Team
0102
0102
0102
0102
0102
0102
0102
0102
0102
0102
0102
0102
0102
0102
0102
0102
0102
0102
0102
0317
031b
031f
0323
0327
032b
032f
0333
0337
033b
033f
0343
0347
034b
034f
0353
0357
035b
035f
0102
0102
0102
0102
0102
0102
0102
0102
0102
0102
0102
0102
0102
0102
0102
0102
0102
0102
0102
17
Ettus E3XX Getting Started Guide
9.2
ANGRYVIPER Team
Run an Application in Standalone Mode
The default setup script sets the OCPI_LIBRARY_PATH variable to include the all of the artifacts that are required to
execute the application. Specifically, all three of the artifacts that are located on the SD card are mounted at
/mnt/card/opencpi/xilinx13_4/artifacts. After running mysetup.sh, navigate to /mnt/card/opencpi/xml.
Run the application using the following command:
$ ocpirun -v -t 1 -d -m bias=hdl bias.xml
The output should be similar to the output shown in Section 9.1.
Run the following commands to view the input and output, and reference Section 9.1 for the expected results:
$ hexdump test.input | less
$ hexdump test.output | less
10
Running Reference Applications
Now that you have set up OpenCPI and the E310 radio, you can run one of the reference applications. Navigate to
bsp_e310/applications/FSK or bsp_e310/applications/rx_app and follow the instructions in the corresponding
documents (FSK_App_Getting_Started_Guide_E3XX.pdf and FSK_app_e3xx.pdf, or RX_app_e3xx.pdf ).
18
Ettus E3XX Getting Started Guide
ANGRYVIPER Team
Appendices
A
Generating Boot Artifacts
In normal use cases, the SD card should be createdable and usable via the simple steps in Section 4. This section
outlines the steps required to regenerate the artifacts used in previous sections for solely informational purposes and
is not expected for users to have to complete these steps.
A.1
BOOT.bin and u-boot.img
The original first and second stage bootloader artifacts that come installed on the E310 SD card are not suitable
for the Petalinux build OpenCPI uses for its software platform as those artifacts are expecting a uImage kernel with
a separate filesystem partition, while the Petalinux build uses a separate ramdisk image file. The BOOT.bin and
u-boot.img files were rebuilt in order to support booting into this style of Linux images from Ettus’s and Xilinx’s
repositories. In summary, the repositories were cloned and checked out to the proper branch, according to the release
for the e310 and the bitbake recipe, and subsequently cross-compiled for ARM using the Xilinx toolchain. The steps
are shown below.
$
$
$
$
$
$
$
$
$
$
$
$
$
$
git clone https://github.com/EttusResearch/meta-ettus.git
cd meta-ettus && git checkout e300-daisy && cd ..
git clone https://github.com/Xilinx/u-boot-xlnx.git
cd u-boot-xlnx && git checkout 664820b231b129552e963e1a96b45ac7196ccc81 && cd ..
cp meta-ettus/e300-bsp/recipes-bsp/u-boot/ettus-e300/* u-boot-xlnx/
cd u-boot-xlnx
mv ps7_init.{c,h} board/xilinx/zynq/
git apply 0001-E300-Uses-UART0-for-console.patch
git apply 0002-E300-Disable-QSPI.patch
git apply 0003-Read-mac-address-from-i2c-EEPROM.patch
git apply 0001-e300-Added-memory-test.patch
source {xilinx-install-dir}/Xilinx/SDK/2013.4/settings64.sh
make zynq_zc70x_config CROSS_COMPILE=arm-xilinx-linux-gnueabimake CROSS_COMPILE=arm-xilinx-linux-gnueabi-
A.2
devicetree.dtb
The device tree needed to be modified in order to register the hardware devices with the correct hardware device
driver in the Petalinux kernel. In summary, the device tree provided by Ettus was decompiled to a device tree source
(dts) file using the device tree compiler (dtc), modified the text file by adding the proper "compatible" strings to
the devices, and subsequently compiled back into a device tree blob (dtb). The steps shown below assume dtc is in
your $PATH and the original device tree blob is in the current working directory.
$ dtc -I dtb -O dts -o devicetree.dts uImage-zynq-e31x-3.dtb
$ vim devicetree.dts
$ dtc -I dts -O dtb -o devicetree.dtb devicetree.dts
Note: The full source for the modified devicetree.dts can be found at /hdl/platforms/e3xx/sd_
card_source/devicetree.dts
A.3
uImage and uramdisk.image.gz
The uImage and uramdisk.image.gz image files come directly from the default 13_4 OpenCPI software platform.
The 13_3 software platform could not be used due to the SD card driver in 13_3 not supporting the E310’s SD card
device.
19
Ettus E3XX Getting Started Guide
B
B.1
ANGRYVIPER Team
Copying only required files to SD card
Copy embedded OS and boot files to SD card
Copy the following files/directories onto the SD card:
$ cp /opt/opencpi/cdk/e3xx/sdcard-xilinx13_4/boot.bin /run/media///
$ cp /opt/opencpi/cdk/e3xx/sdcard-xilinx13_4/devicetree.dtb /run/media///
$ cp /opt/opencpi/cdk/e3xx/sdcard-xilinx13_4/u-boot.img /run/media///
$ cp /opt/opencpi/cdk/e3xx/sdcard-xilinx13_4/uImage /run/media///
$ cp /opt/opencpi/cdk/e3xx/sdcard-xilinx13_4/uramdisk.image.gz /run/media///
B.2
Files needed for Standalone Mode
After performing the steps from B.1, copy the entire opencpi directory to the SD card, then copy the relevant
bitstreams, artifacts into the artifacts directory and application XMLs into the applications directory. For this
getting started guide, only one bitstream is required to be copied onto the SD cards, where as the required artifacts
and application XML where copied to the SD along with the entire opencpi directory.
$ cp -r /opt/opencpi/cdk/e3xx/sdcard-xilinx13_4/opencpi /run/media///
$ cp /home//ocpi_projects/assets/hdl/assemblies/testbias/container-testbias_e3xx_base/\
target-zynq/testbias_e3xx_base.bit.gz /run/media///opencpi/xilinx13_4/artifacts
B.3
Files needed for Network Mode
After performing the steps from B.1, create a directory on the partition named "opencpi" and copy the following
files into the this directory:
$ mkdir /run/media///opencpi
$ cp /opt/opencpi/cdk/e3xx/sdcard-xilinx13_4/opencpi/default_mynetsetup.sh \
/run/media///opencpi/
$ cp /opt/opencpi/cdk/e3xx/sdcard-xilinx13_4/opencpi/zynq_net_setup.sh \
/run/media///opencpi/
20
Source Exif Data:
File Type : PDF File Type Extension : pdf MIME Type : application/pdf PDF Version : 1.4 Linearized : No Page Count : 20 XMP Toolkit : XMP toolkit 2.9.1-13, framework 1.6 About : uuid:ebf235be-03ff-11f4-0000-f324c528b5cd Producer : GPL Ghostscript 9.07 Keywords : () Modify Date : 2018:10:09 16:50:05Z Create Date : 2018:10:09 16:50:05Z Creator Tool : ANGRYVIPER Team Document ID : uuid:ebf235be-03ff-11f4-0000-f324c528b5cd Format : application/pdf Title : Ettus E3xx Getting Started Guide Creator : ANGRYVIPER Team Description : () Author : ANGRYVIPER Team Subject :EXIF Metadata provided by EXIF.tools