Ettus E3XX Getting Started Guide ANGRYVIPER Team
2 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 Description
All prerequisite RPMs 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 loca-
tion of /opt/opencpi/prerequisites.
angryviper-ide-*.x86 64.rpm 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.
opencpi-*.x86_64.rpm 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 essen-
tial components, workers, platforms, etc.
opencpi-devel-*.x86_64.rpm Additional header files and scripts for developing new assets as
HDL and/or RCC.
opencpi-sw-platform-xilinx13_4-*.noarch.rpm Additional files necessary to build the framework targeting spe-
cific RCC/software platforms, independent of the final deployed
hardware.
opencpi-hw-platform-e3xx-*.noarch.rpm Additional files necessary to build the framework targeting spe-
cific 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.
3.1 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/<user>/ocpi_projects/core | True |
| ocpi.assets | /home/<user>/ocpi_projects/assets | True |
| ocpi.bsp.e310 | /home/<user>/ocpi_projects/bsp_e310 | True |
----------------------------------------------------------------------------------------
5
To Next Page
Loading...
Need help?
General