This page gives an overview of using the ARM Mbed platform supported firmware example with Analog Devices AD4696 Evaluation board(s) and SDP-K1 controller board. This example code leverage the ADI developed IIO (Industrial Input Output) ecosystem to evaluate the AD4696 family devices by providing a device debug and data capture support.
The overview of an entire system is shown below:
IIO oscilloscope is used as client application running on windows-OS, which is ADI developed GUI for ADC data visualization and device debug. The interface used for communicating client application with firmware application (IIO device) is UART (Note: SDP-K1 can also support high speed VirtualCOM port @1Mbps or higher speed for faster data transmission). The firmware application communicates with IIO device (AD4696) using ADI No-OS drivers and platform drivers low level software layers. SDP-K1 is used as controller board, on which IIO firmware application runs and using above software libraries, the IIO firmware communicates with AD4696 IIO device. The AD4696B Eval board is used for development and testing of this application.
The AD4696 device is configured in “Serial Software” mode in the firmware. AD4696 uses SPI communication for device register access and data capture.
SDP-K1 is powered through USB connection from the computer. SDP-K1 acts as a Serial device when connected to PC, which creates a COM Port to connect to IIO Oscilloscope GUI running on windows-OS. The COM port assigned to a device can be seen through the device manager for windows based OS.
The SDP-K1 generates PWM signals to manually trigger conversion on the AD4696. The digital pin and the sampling rate for PWM signal can be configured in the app_config_mbed.h file. By default it is generated at 62.5 KSPS on D6 Arduino pin. To achieve this, the CS of the SDP-K1 and CNV pins on the Eval board should be shorted/soldered either by switching JP31 onboard jumper position to A or by using external wires to connect the same. The D6 (CNV) Arduino pin on the MCU should should be left floating, as this pin is used only to trigger interrupt attached to the data capture callback function in the software. The rising edge on the CS pin acts as conversion start signal for the AD4696: whenever a SPI read transaction is performed in the data capture callback function.
The firmware supports both unipolar and pseudo bipolar modes. By default the firmware is configured in unipolar mode. To switch to pseudo bipolar mode, by defining “PSEUDO_BIPOLAR_MODE” macro in app_config.h file. Make sure to change the JP6 jumper to position A on the Eval board to use the PSEUDO_BIPOLAR_MODE. Since the pin pairing option is same for all the channels in standard sequencer mode, hence polarity mode for all the channels is also kept same to avoid stale ADC output codes.
Latest firmware (Use below link):
If you have some familiarity with the Mbed platform, the following is a basic list of steps required to start running the code, see below for more detail:
This library provides an abstracted library interface to communicate IIO device (AD4696) and IIO client application (IIO Oscilloscope) without worrying about the low level hardware details. Download and install below Libiio windows installer in your computer.
Libiio installer for Windows (Use below link):
This is a GUI (Graphical User Interface) based IIO client application for data visualization and device configuration/debugging. The data from IIO devices (ADCs/DACs) is transmitted over Serial/Ethernet/USB link to IIO Oscilloscope client through the abstracted layer of “libiio”. Download and install below IIO Oscilloscope windows installer in your computer.
IIO Oscilloscope installer for Windows (Use below link):
Open the IIO Oscilloscope application from start menu and configure the serial (UART) settings as shown below. Click on refresh button and AD4696 device should pop-up in IIO devices list. Click 'Connect' and select the AD4696 device from the drop down menu list of 'Device Selection'.
The IIO Oscilloscope allows user to access and configure different device parameters, called as 'Device Attributes”. There are 2 types of attributes:
How to read and write attribute:
DMM tab can be used read the instantaneous voltage applied on analog input channels. Simply select the device and channels to read and press start button.
*Note: The voltage is just instantaneous, so it is not possible to get RMS AC voltage or averaged DC voltage. Also, when using DMM tab, it is not encouraged to use Data Capture or Debug tab as this could impact data capturing.
To capture the data from ad4696 IIO device, simply select the device and channels to read/capture data. The data is plotted as “ADC Raw Value” Vs “Number of Samples” and is just used for Visualization. The data is read as is from device without any processing. If user wants to process the data, it must be done externally by capturing data from the Serial link on controller board.
*Note: The DMM or Debug tab should not be accessed when capturing data as this would impact data capturing.
The below block diagram shows the ad4696 IIO firmware layer.
This file can be used to:
This file can be used to:
These files define the user configurations for the AD4696, such as SPI parameters (frequency, mode, etc) and other init parameters used by No-OS drivers to initialize AD4696 device (active device, data format, etc). These are the parameters loaded into device when device is powered-up or power-cycled.
This file implements the data capturing logic for the AD4696 device. The adc_data_capture.c module present in platform drivers acts as an abstracted layer for common IIO application data capturing.
This file defines getter/setter functions for all the device and channel specific attributes (related to AD4696 devices) to read/write the device parameters. The majority of device specific functionality is present in this module.
The no-os drivers provide the high-level abstracted layer for digital interface of AD4696 devices. The complete digital interface (to access memory map and perform data read) is done in integration with platform drivers. The functionality related with no-os drivers is covered in below 2 files: 1. ad469x.c 2. ad469x.h The drivers are can use SPI engine framework or Standard SPI framework to communicate with the board. By default, the drivers use the Standard SPI framework. The SPI engine framework can be enabled defining the “ENABLE_SPI_ENGINE” macro in the ad469x.h file.