Unleash the beauty of analog side of a signal with DAC60508 and MK64FN1M0VDC12
Bridging the binary abyss
Published Aug 21, 2023
Click board™
DAC 12 Click
Dev Board
Clicker 2 for Kinetis
Compiler
NECTO Studio
MCU
MK64FN1M0VDC12
Convert discrete digital values into continuous analog voltages, and enable accurate audio or visual signal representation
A
A
Hardware Overview
How does it work?
DAC 12 Click is based on the DAC60508, a low-power voltage-output 8-channel 12-bit digital-to-analog converter (DAC) from Texas Instruments. Each output channel in the DAC60508 consists of an R-2R ladder architecture, followed by an output buffer amplifier. It also includes a 2.5V, 5ppm/°C internal reference, eliminating the need for an external precision reference in most applications, and a user interface-selectable gain configuration that provides full-scale output voltages of 1.25V, 2.5V, or 5V. This Click board™ communicates with MCU through a flexible serial interface compatible
with SPI-type interfaces used on many microcontrollers and DSP controllers, with a maximum frequency of 50 MHz. The input data are written to the individual DAC data registers in straight binary format, where after a Power-On or a reset event, all DAC registers are set to a mid-scale code. Data written to the DAC data registers are initially stored in the DAC buffer registers. Data transfer from the DAC buffer registers to the active DAC registers can be configured immediately using the asynchronous mode or initiated by an LDAC trigger in synchronous mode. Once the DAC
active registers are updated, the DAC outputs change to new values. When the host reads from a DAC data register, the value held in the DAC buffer register is returned (not stored in the DAC active register). 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
This Click board can be interfaced and monitored in two ways:
Application Output- Use the "Application Output" window in Debug mode for real-time data monitoring. Set it up properly by following this tutorial.
UART Terminal- Monitor data via the UART Terminal using a USB to UART converter. For detailed instructions, check out this tutorial.
Software Support
Library Description
This library contains API for DAC 12 Click driver.
Key functions:
dac12_soft_reset- This function executes the software reset commanddac12_set_channel_value- This function sets the raw DAC value to the specific channels outputdac12_set_channel_voltage- This function sets the output voltage of the specific channels
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 DAC12 Click example
*
* # Description
* This example demonstrates the use of DAC 12 click board by changing
* the outputs voltage level every 2 seconds.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and performs the click default configuration.
*
* ## Application Task
* Changes the output voltage of all channels every 2 seconds and logs the voltage value on the USB UART.
* It will go through the entire voltage range taking into account the number of steps which is defined below.
*
* @author Stefan Filipovic
*
*/
#include "board.h"
#include "log.h"
#include "dac12.h"
#define NUMBER_OF_STEPS 20 // The number of steps by which the entire voltage range will be divided.
static dac12_t dac12;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
dac12_cfg_t dac12_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.
dac12_cfg_setup( &dac12_cfg );
DAC12_MAP_MIKROBUS( dac12_cfg, MIKROBUS_1 );
if ( SPI_MASTER_ERROR == dac12_init( &dac12, &dac12_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
DAC12_SET_DATA_SAMPLE_EDGE;
if ( DAC12_ERROR == dac12_default_cfg ( &dac12 ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
float step = DAC12_INTERNAL_VREF / NUMBER_OF_STEPS;
float output_voltage = step;
for ( uint8_t cnt = 0; cnt < NUMBER_OF_STEPS; cnt++ )
{
if ( DAC12_OK == dac12_set_channel_voltage ( &dac12, DAC12_SELECT_CHANNEL_ALL, output_voltage ) )
{
log_printf( &logger, " All channels output voltage set to %.3f V\r\n", output_voltage );
output_voltage += step;
Delay_ms( 2000 );
}
}
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
