ADI maintains a set of tools to interface with ADI RF and microwave devices within MATLAB and Simulink. These are combined into single Toolbox which contains a set of Board Support Packages (BSP). The list of supported boards is provided below.
The current stable Toolbox can be downloaded from the RF Microwave Toolbox GitHub Release Page. Download the latest mltbx file then open that file within MATLAB. Opening the file will automatically install the Toolbox, adding the necessary components to your MATLAB path. The “Analog Devices, Inc. RF Microwave Toolbox” will appear in your Add-Ons Explore within MATLAB.
To interface and stream data with hardware will require installation of libiio and one of two Hardware Support Packages from MathWorks. The libiio library can be obtained on the Github page of the project.
Installation of either:
is required to use the streaming system objects or blocks. These support packages provide the necessary libIIO MATLAB bindings used by ADI's system objects.
The toolbox can only be built under Linux or with Cygwin on a Windows platform. Conveniently, the entire process is automated with a Makefile located in the CI/scripts folder of the repository. The following is required on the system before the build process can be run:
First clone the repo and move into it:
git clone https://github.com/analogdevicesinc/RFMicrowaveToolbox.git cd RFMicrowaveToolbox
To build the toolbox run the following:
make -C CI/scripts build
To create a installable tlbx file run:
make -C CI/scripts gen_tlbx
Device interfaces which provide control and data streaming are implemented with MATLAB System Objects and Simulink Blocks. These System Objects can be access under the “adi” namespace in MATLAB and are followed by their part number or board name and finally Tx or Rx:
adi.<Part or Board Name>.<Tx or Rx>
For example, to instantiate a Stingray object to control the X-Band Development Platform it can be created as follows:
bf = adi.Stingray;
The Stingray Evaluation board contains an ADXUD1AEBZ, ADF4371 and LTC2314. Therefore, it uses the objects corresponding to these devices along with ADAR100x, a genric ADAR1000 superclass under the hood. Similarly, ADALM-PHASER class is also derived from low level objects based on their parts.
For example usage of certain objects, it can be useful to inspect their related test code which exercises initiations in different configurations. The available code is available in the GitHub repo folder here, where object tests have the naming convention <Object>Tests.m.
To get a list of currently available objects with the BSP installed simply run:
To get more information on a given object run:
help adi.<Part or Board Name>
doc adi.<Part or Board Name>
There are some common attributes that need to be set for system objects and parts.
uriContext address of IIO device.
bf.uri = 'ip:192.168.2.1'
If a driver attribute or setting is not available in the standard objects it can be easily extended to cover more IIO attributes. See this guide.
Examples for streaming data and targeting FPGAs are listed within the Toolbox documentation itself. To view run the following with MATLAB: