Developer Tree Portion Description
OPEN
Fully populated with the source files used by Vaisala to build each RVP release.
Use the OPEN code as a reference for programming examples and ideas.
Note that OPEN code can change significantly with each release. Changes may be
lost when you install the next RDA update.
SITE
Use the SITE directory to add custom features to RVP.
This directory is a collection of empty program stubs whose calling conventions
are very stable. Each stub is a hook that can be used to define a new major mode.
Replace these stubs with custom code to add custom major modes to RVP.
Customizations are typically done in the rvp9main/open, rvpxproc/open, rvp9main/
site, and rvpxproc/site trees.
RVP source code is in the rvpxproc tree.
C.2.2
Building A Customised RDA Tree
During an RDA, you copy the new source tree to your develpment envirnoment and merge
your customizations to the new tree.
For more information, see IRIS and RDA Software Installation Guide
After an upgrade, you must build ind install your customized version of RVP and RCP.
C.3
Debugging and Profiling Your Code
While RVP is a complex multi-thread and multi- process system, it is a user-level application
running under the Linux operating system.
You can debug most of your custom code using tools familiar to Linux/C/GNU programmers.
C.3.1
Monitoring Opcode/Data Activity: -exposeIO
RVP is generally controlled by higher level application such as Ascope, IRIS, and dspx, which
communicate with RVP through the IRIS DSP Driver Library using the opcodes (see 8.1 Host
Computer Command Overview (page 235)). These layered applications provide a clean and
maintainable signal processor interface.
The complete opcode activity, between the application driver and RVP, can be viewed by
including the –exposeIO
flag on RVP startup command line. The following printout shows
the output example when you type an Output Test opcode, followed by a Noise
Sample command and a Get Processor Parameters opcode:
RVP900 User Guide M211322EN-J
374