Matchstiq-Z1 Getting Started Guide
ANGRYVIPER Team
2
Overview
This document provides steps for configuring a factory provided Epiq Solutions Matchstiq-Z1 SDR with the OpenCPI
run-time environment for executing applications, configuring a development system to build OpenCPI bitstreams
targeting the
matchstiq_z1
platform, and examples of executing applications on the OpenCPI configured Matchstiq-
Z1.
Note: Only the Z1 version of the Epiq Solutions Matchstiq product line is supported by OpenCPI.
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 en-
sures 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 por-
tion of the Component Development Kit (CDK)
and the source for the ocpi.core and ocpi.assets
Projects containing framework essential compo-
nents, 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_3-*.noarch.rpm
Additional files necessary to build the framework
targeting specific RCC/software platforms, inde-
pendent of the final deployed hardware.
opencpi-hw-platform-matchstiq_z1-xilinx13_3-*.noarch.rpm
Additional files necessary to build the frame-
work 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.
3.1
Installation of provided OpenCPI projects:
core
and
assets
This guide assumes the user has executed
ocpi-copy-projects
, accepting the default settings, to copy and register the
core
and
assets
projects from the /opt/opencpi/projects for building bitstreams for the Matchstiq-Z1. Reference
the Getting Started Guide for details on
ocpi-copy-projects
. While registering of the projects is performed during
the execution of 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 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
|
5
