Achieve rapid conversion of analog signals into digital form with AD7490 and MK64FN1M0VDC12
12-bit high speed, low power, 16-channel, successive approximation ADC
Published Mar 21, 2024
Click board™
ADC 24 Click
Dev Board
Clicker 2 for Kinetis
Compiler
NECTO Studio
MCU
MK64FN1M0VDC12
Invaluable tool for developers needing precise monitoring and data analysis solutions
A
A
Hardware Overview
How does it work?
ADC 24 Click is based on the AD7490, a 12-bit, high-speed, low-power, 16-channel successive approximation ADC from Analog Devices. This ADC minimizes power consumption while maintaining high throughput rates, drawing just 2.5mA from a 5V supply at full capacity. It achieves up to 1MSPS throughput rates and incorporates a low noise, wide bandwidth track-and-hold amplifier that adeptly handles input frequencies beyond 1MHz. This Click board™ is particularly suited for applications requiring extensive system monitoring, such as multichannel system monitoring, power line monitoring, data acquisition, instrumentation, and process control. The AD7490 is equipped with 16 single-ended analog inputs, enhanced by a channel sequencer that enables the programmed and
sequential conversion of channels. The analog input range is configurable, offering a 0V to REFIN or a broader 0V to 2×REFIN range, achieved by the MCP1525 voltage reference from Microchip, with fixed 2.5V output. This flexibility allows users to tailor the ADC to various measurement requirements. For accurate utilization of the 0V to 2×REFIN measurement range, powering the IC with 5V is mandatory, which is achieved with 5V from the mikroBUS™ power rail. Moreover, the AD7490 supports multiple operational modes, such as Normal, Full Shutdown, Auto Shutdown, and Auto Standby, all of which are register-configurable. These modes provide users with various power management options to optimize the balance between power dissipation and throughput rate
based on specific application needs. The conversion process and data acquisition are made using CS and the serial clock signal, ensuring straightforward interfacing with microprocessors or DSPs (SPI/QSPI™/MICROWIRE™/ DSP compatible). The input signal is sampled at the falling edge of CS, initiating conversion at this juncture without any pipeline delays. This Click board™ can operate with either 3.3V or 5V logic voltage levels selected via the VCC SEL jumper. This way, both 3.3V and 5V capable MCUs can use the communication lines properly. Also, this Click board™ comes equipped with a library containing easy-to-use functions and an example code that can be used as a reference for further development.
Features overview
Development board
Clicker 2 for Kinetis is a compact starter development board that brings the flexibility of add-on Click boards™ to your favorite microcontroller, making it a perfect starter kit for implementing your ideas. It comes with an onboard 32-bit ARM Cortex-M4F microcontroller, the MK64FN1M0VDC12 from NXP Semiconductors, two mikroBUS™ sockets for Click board™ connectivity, a USB connector, LED indicators, buttons, a JTAG programmer connector, and two 26-pin headers for interfacing with external electronics. Its compact design with clear and easily recognizable silkscreen markings allows you to build gadgets with unique functionalities and
features quickly. Each part of the Clicker 2 for Kinetis development kit contains the components necessary for the most efficient operation of the same board. In addition to the possibility of choosing the Clicker 2 for Kinetis programming method, using a USB HID mikroBootloader or an external mikroProg connector for Kinetis programmer, the Clicker 2 board also includes a clean and regulated power supply module for the development kit. It provides two ways of board-powering; through the USB Micro-B cable, where onboard voltage regulators provide the appropriate voltage levels to each component on the board, or
using a Li-Polymer battery via an onboard battery connector. All communication methods that mikroBUS™ itself supports are on this board, including the well-established mikroBUS™ socket, reset button, and several user-configurable buttons and LED indicators. Clicker 2 for Kinetis is an integral part of the Mikroe ecosystem, allowing you to create a new application in minutes. Natively supported by Mikroe software tools, it covers many aspects of prototyping thanks to a considerable number of different Click boards™ (over a thousand boards), the number of which is growing every day.
Microcontroller Overview
MCU Card / MCU
Architecture
ARM Cortex-M4
MCU Memory (KB)
1024
Silicon Vendor
NXP
Pin count
121
RAM (Bytes)
262144
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Click board™ Schematic
Step by step
Project assembly
Start by selecting your development board and Click board™. Begin with the Clicker 2 for Kinetis as your development board.
Track your results in real time
Application Output
1. Application Output - In Debug mode, the 'Application Output' window enables real-time data monitoring, offering direct insight into execution results. Ensure proper data display by configuring the environment correctly using the provided tutorial.
2. UART Terminal - Use the UART Terminal to monitor data transmission via a USB to UART converter, allowing direct communication between the Click board™ and your development system. Configure the baud rate and other serial settings according to your project's requirements to ensure proper functionality. For step-by-step setup instructions, refer to the provided tutorial.
3. Plot Output - The Plot feature offers a powerful way to visualize real-time sensor data, enabling trend analysis, debugging, and comparison of multiple data points. To set it up correctly, follow the provided tutorial, which includes a step-by-step example of using the Plot feature to display Click board™ readings. To use the Plot feature in your code, use the function: plot(*insert_graph_name*, variable_name);. This is a general format, and it is up to the user to replace 'insert_graph_name' with the actual graph name and 'variable_name' with the parameter to be displayed.
Software Support
Library Description
This library contains API for ADC 24 Click driver.
Key functions:
adc24_get_voltage- This function reads the results of 12-bit ADC raw data and converts them to proportional voltage levels by using the SPI serial interfaceadc24_get_adc_data- This function reads a conversion result and selected channel by using the SPI serial interface
Open Source
Code example
The complete application code and a ready-to-use project are available through the NECTO Studio Package Manager for direct installation in the NECTO Studio. The application code can also be found on the MIKROE GitHub account.
/*!
* @file main.c
* @brief ADC 24 Click example
*
* # Description
* This example demonstrates the use of the ADC 24 Click board
* by reading and writing data by using the SPI serial interface
* and reading results of AD conversion.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initialization of SPI module and log UART.
*
* ## Application Task
* The demo application reads the voltage levels
* from all 15 analog input channels and displays the results.
* Results are being sent to the UART Terminal, where you can track their changes.
*
* @author Nenad Filipovic
*
*/
#include "board.h"
#include "log.h"
#include "adc24.h"
static adc24_t adc24;
static log_t logger;
static adc24_ctrl_t ctrl;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
adc24_cfg_t adc24_cfg; /**< Click config object. */
/**
* Logger initialization.
* Default baud rate: 115200
* Default log level: LOG_LEVEL_DEBUG
* @note If USB_UART_RX and USB_UART_TX
* are defined as HAL_PIN_NC, you will
* need to define them manually for log to work.
* See @b LOG_MAP_USB_UART macro definition for detailed explanation.
*/
LOG_MAP_USB_UART( log_cfg );
log_init( &logger, &log_cfg );
log_info( &logger, " Application Init " );
// Click initialization.
adc24_cfg_setup( &adc24_cfg );
ADC24_MAP_MIKROBUS( adc24_cfg, MIKROBUS_1 );
if ( SPI_MASTER_ERROR == adc24_init( &adc24, &adc24_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
ctrl.ch_sel = ADC24_CH_SEL_IN_0;
ctrl.pm = ADC24_PM_NORMAL;
ctrl.seq_shadow = ADC24_SEQ_SHADOW_AN_INPUT;
ctrl.weak = ADC24_WEAK_DOUT_THREE_STATE;
ctrl.range = ADC24_RANGE_VREF_5V;
ctrl.coding = ADC24_CODING_BIN;
log_info( &logger, " Application Task " );
log_printf( &logger, "_____________\r\n" );
}
void application_task ( void )
{
uint8_t ch_pos = 0;
float voltage = 0;
for ( uint8_t n_cnt = ADC24_CH_SEL_IN_0; n_cnt <= ADC24_CH_SEL_IN_15; n_cnt++ )
{
ctrl.ch_sel = n_cnt;
if ( ADC24_OK == adc24_get_voltage( &adc24, ctrl, &ch_pos, &voltage ) )
{
log_printf( &logger, " IN%u : %.3f V\r\n", ( uint16_t ) ch_pos, voltage );
}
Delay_ms( 100 );
}
log_printf( &logger, "_____________\r\n" );
Delay_ms( 1000 );
}
int main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
return 0;
}
// ------------------------------------------------------------------------ END
