This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
resources:eval:user-guides:ad4130:mbed_iio_app [20 Jul 2022 14:54] – Mahesh Phalke | resources:eval:user-guides:ad4130:mbed_iio_app [31 May 2023 07:54] (current) – Mahesh Phalke | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ===== AD4130 | + | ===== AD4130 IIO Application===== |
- | This page gives an overview of using the ARM Mbed platform | + | |
+ | ===== Introduction ===== | ||
+ | |||
+ | This page gives an overview of using the ARM platforms | ||
Devices AD4130 Evaluation board and SDP-K1 controller board. This example code leverages | Devices AD4130 Evaluation board and SDP-K1 controller board. This example code leverages | ||
the ADI developed IIO (Industrial Input Output) ecosystem to evaluate the AD4130 device by providing a | the ADI developed IIO (Industrial Input Output) ecosystem to evaluate the AD4130 device by providing a | ||
device debug and data capture support. | device debug and data capture support. | ||
- | The overview of an entire system is shown below: | ||
- | |||
- | {{ : | ||
- | IIO oscilloscope is used as a client application running on windows-os, which is ADI developed GUI for ADC data visualization and device debug. The physical interface used for communicating client application with firmware application (IIO device) is UART/VirtualCOM (*For now only SDP-K1 supports high speed VirtualCOM port @1Mbps or higher speed for faster data transmission). The firmware application communicates with IIO device (AD4130) using ADI No-OS drivers and platform drivers middle-ware | + | {{section> |
---- | ---- | ||
===Useful links=== | ===Useful links=== | ||
+ | {{section> | ||
* [[adi> | * [[adi> | ||
* [[adi> | * [[adi> | ||
- | * [[https:// | ||
- | * [[https:// | ||
---- | ---- | ||
Line 29: | Line 28: | ||
< | < | ||
- | AD4130 uses SPI communication for device register access and data capture. For data transmission to IIO client, VirtualCOM Or UART serial communication is used. SDP-K1 by default uses the VCOM serial interface for higher speed data transmission. | + | AD4130 uses SPI communication for device register access and data capture. |
- | SDP-K1 is powered through USB connections 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. | + | |
- | {{ :resources:eval:user-guides: | + | {{section>resources/tools-software/ |
- | + | ||
- | SDP-K1 can support | + | |
- | + | ||
- | {{ : | + | |
---- | ---- | ||
Line 42: | Line 36: | ||
===== Software Downloads ===== | ===== Software Downloads ===== | ||
- | <WRAP round download> | + | {{section>resources/tools-software/product-support-software/iio_support_software_downloads# |
- | Latest firmware (Use below link): | + | |
- | * [[https:// | + | |
- | </ | + | |
- | + | ||
- | === Quick Start to Use Mbed IIO Firmware === | + | |
- | If you have some familiarity with the Mbed platform, the following is a basic list of steps required to start running the code: | + | |
- | + | ||
- | * Connect the AD4130 EVAL-board to the SDP-K1 controller board as specified in hardware connections section. | + | |
- | * Connect the SDP-K1 controller board to your computer over USB provided along with SDP-K1 board. | + | |
- | * mport the code into Keil Studio from above firmware download link by using “File→Import Project…” option. Specify the web link of code in URL and check 'Make this the active project’ option. | + | |
- | {{ : | + | |
- | + | ||
- | * Make sure all dependent libraries are obtained correctly by IDE. | + | |
- | {{ : | + | |
- | + | ||
- | * Compile the code as shown below. After a successful compile a binary will be downloaded to your computer - store this into your computer. Drag and drop (or copy) this binary file to the SDP-K1 USB drive mounted in your computer file system (similar to C/D drives) to flash firmware into MCU. | + | |
- | {{ : | + | |
- | + | ||
- | ==== Libiio: IIO Library ==== | + | |
- | This library provides an abstracted library interface to communicate IIO device and IIO client application (e.g. IIO Oscilloscope) without worrying about the low level hardware details. Download and install below [[wiki/ | + | |
- | <WRAP round download> | + | |
- | Libiio installer for Windows (Use below link): | + | |
- | * [[repo> | + | |
- | </ | + | |
- | + | ||
- | ==== IIO Oscilloscope (Client) ==== | + | |
- | This is a GUI (Graphical User Interface) based IIO client application for data visualization and device configuration/ | + | |
- | <WRAP round download> | + | |
- | Download and install below IIO Oscilloscope windows installer in your computer. | + | |
- | IIO Oscilloscope installer for Windows (Use below link): | + | |
- | * [[repo> | + | |
- | </ | + | |
---- | ---- | ||
==== Evaluating AD4130 Using IIO Ecosystem ==== | ==== Evaluating AD4130 Using IIO Ecosystem ==== | ||
- | <note>Ensure that hardware connection has been made properly in between Controller Board (SDP-K1) and AD4130 Eval board. Also ensure all software's (IIO firmware, Libiio windows installer and IIO Oscilloscope windows installer) are downloaded and installed in your computer before trying to communicate with AD4130 device..< | + | |
+ | {{section>resources/ | ||
==== Running IIO Oscilloscope (Client) ==== | ==== Running IIO Oscilloscope (Client) ==== | ||
Line 133: | Line 96: | ||
{{ : | {{ : | ||
+ | |||
+ | ---- | ||
+ | |||
+ | ==== Python Environment and Scripts ==== | ||
+ | |||
+ | Data capture, sensor measurement, | ||
+ | |||
+ | {{section> | ||
---- | ---- | ||
Line 172: | Line 143: | ||
=== Sensor Channels Calibration === | === Sensor Channels Calibration === | ||
It is possible to calibrate the device channels which are connected to external sensors. The sensors calibration (gain and offset) is done by executing the python script “ad4130_calibration.py”. | It is possible to calibrate the device channels which are connected to external sensors. The sensors calibration (gain and offset) is done by executing the python script “ad4130_calibration.py”. | ||
- | |||
- | ---- | ||
- | |||
- | ==== Python Environment and Scripts ==== | ||
- | Data capture, sensor measurement, | ||
- | |||
- | === Setting-up Python Environment === | ||
- | * Install python (64-bit windows) into your local machine. The python scripts are developed and executed using python 3.10.5 version, so recommend using version 3.10.5 or beyond. [[https:// | ||
- | * Once python is installed, make sure the environment path (on windows machine) is set properly. You can verify if python is installed properly by typing “python --version” command on command line tool such as gitbash, command prompt, power shell, etc. | ||
- | {{ : | ||
- | |||
- | * Install all required support packages by running requirements.txt file using command “python -m pip install -r requirements.txt” from the '/ | ||
- | {{ : | ||
- | |||
- | === Modifying/ | ||
- | * All python scripts specific to ad4130 IIO firmware are stored into “scripts” folder present in the project directory. So, any script must be executed from this folder. | ||
- | |||
- | * Update the ‘uri’ interface in script according to COM port assigned to your device (sdp-k1). | ||
- | |||
- | {{ : | ||
- | |||
- | * Executing the python script by using command “python script_name.py” | ||
---- | ---- |