30 min

Bridge the gap between the digital and analog world with DAC80501 and PIC32MZ1024EFK144

Craft your analog path with DAC innovation

DAC 9 Click with UNI-DS v8

Published Aug 21, 2023

Click board™

DAC 9 Click

Dev Board



NECTO Studio



By translating binary codes into voltage levels, this solution amplifies data's voice, enabling systems to interpret, respond to, and leverage digital insights for various applications



Hardware Overview

How does it work?

DAC 9 Click is based on the DAC80501, a single-channel, buffered, 16-bit resolution digital-to-analog converter from Texas Instruments. It includes a 2.5V, 5ppm/˚C internal reference, giving full-scale output voltage ranges of 1.25V, 2.5V, or 5V, and incorporates a Power-On Reset function. This function makes sure that the DAC80501 output powers up at zero scale or midscale and remains at that scale until a valid code is written to the device. High resolution and simple interface features make this Click board™ suitable for applications such as battery testers, communications equipment, factory automation, control, test and measurement, and more. The output channel, which DAC80501 routed to the VOUT terminal, consists of a rail-to-rail ladder

architecture with an output buffer amplifier that generates rail-to-rail voltages, giving a maximum output range of 0V to VDD. The full-scale output range of the DAC output is determined by the reference voltage on the VREFIO pin, the reference divider setting, and the gain configuration for that channel set by the corresponding BUFF-GAIN bit. When the DAC80501 uses an internal reference, this voltage is externally available at the VREF terminal and can source up to 5mA. Besides, the user can bring the external reference voltage on this terminal in the case of the DAC80501 external reference configuration. DAC 9 Click provides the possibility of using both I2C and SPI interfaces. The selection can be performed by positioning SMD jumpers labeled COMM SEL to an appropriate

position. Note that all jumpers must be placed on the same side, or the Click board™ may become unresponsive. In SPI mode, the DAC80501 uses a 3-Wire SPI serial interface that operates at clock rates of up to 50MHz, while in I2C mode, the DAC80501 can operate in Standard Mode (100 kbps), Fast Mode (400 kbps) and Fast-Plus Mode (1.0 Mbps). 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.

DAC 9 Click hardware overview image

Features overview

Development board

UNI-DS v8 is a development board specially designed for the needs of rapid development of embedded applications. It supports a wide range of microcontrollers, such as different STM32, Kinetis, TIVA, CEC, MSP, PIC, dsPIC, PIC32, and AVR MCUs regardless of their number of pins, and a broad set of unique functions, such as the first-ever embedded debugger/programmer over WiFi. The development board is well organized and designed so that the end-user has all the necessary elements, such as switches, buttons, indicators, connectors, and others, in one place. Thanks to innovative manufacturing technology, UNI-DS v8 provides a fluid and immersive working experience, allowing access anywhere and under any

circumstances at any time. Each part of the UNI-DS v8 development board contains the components necessary for the most efficient operation of the same board. An advanced integrated CODEGRIP programmer/debugger module offers many valuable programming/debugging options, including support for JTAG, SWD, and SWO Trace (Single Wire Output)), and seamless integration with the Mikroe software environment. Besides, it also includes a clean and regulated power supply module for the development board. It can use a wide range of external power sources, including a battery, an external 12V power supply, and a power source via the USB Type-C (USB-C) connector. Communication options such as USB-UART, USB

HOST/DEVICE, CAN (on the MCU card, if supported), and Ethernet is also included. In addition, it also has the well-established mikroBUS™ standard, a standardized socket for the MCU card (SiBRAIN standard), and two display options for the TFT board line of products and character-based LCD. UNI-DS v8 is an integral part of the Mikroe ecosystem for rapid development. Natively supported by Mikroe software tools, it covers many aspects of prototyping and development thanks to a considerable number of different Click boards™ (over a thousand boards), the number of which is growing every day.

UNI-DS v8 horizontal image

Microcontroller Overview

MCU Card / MCU



8th Generation



MCU Memory (KB)


Silicon Vendor


Pin count


RAM (Bytes)


Used MCU Pins

mikroBUS™ mapper

SPI Chip Select
SPI Clock
Power Supply
I2C Clock
I2C Data
Power Supply

Take a closer look


DAC 9 Click Schematic schematic

Step by step

Project assembly

Fusion for PIC v8 front image hardware assembly

Start by selecting your development board and Click board™. Begin with the UNI-DS v8 as your development board.

Fusion for PIC v8 front image hardware assembly
GNSS2 Click front image hardware assembly
SiBRAIN for PIC32MZ1024EFK144 front image hardware assembly
GNSS2 Click complete accessories setup image hardware assembly
v8 SiBRAIN Access MB 1 - upright/background hardware assembly
Necto image step 2 hardware assembly
Necto image step 3 hardware assembly
Necto image step 4 hardware assembly
NECTO Compiler Selection Step Image hardware assembly
NECTO Output Selection Step Image hardware assembly
Necto image step 6 hardware assembly
Necto image step 7 hardware assembly
Necto image step 8 hardware assembly
Necto image step 9 hardware assembly
Necto image step 10 hardware assembly
Necto PreFlash Image hardware assembly

Track your results in real time

Application Output

After pressing the "FLASH" button on the left-side panel, it is necessary to open the UART terminal to display the achieved results. By clicking on the Tools icon in the right-hand panel, multiple different functions are displayed, among which is the UART Terminal. Click on the offered "UART Terminal" icon.

UART Application Output Step 1

Once the UART terminal is opened, the window takes on a new form. At the top of the tab are two buttons, one for adjusting the parameters of the UART terminal and the other for connecting the UART terminal. The tab's lower part is reserved for displaying the achieved results. Before connecting, the terminal has a Disconnected status, indicating that the terminal is not yet active. Before connecting, it is necessary to check the set parameters of the UART terminal. Click on the "OPTIONS" button.

UART Application Output Step 2

In the newly opened UART Terminal Options field, we check if the terminal settings are correct, such as the set port and the Baud rate of UART communication. If the data is not displayed properly, it is possible that the Baud rate value is not set correctly and needs to be adjusted to 115200. If all the parameters are set correctly, click on "CONFIGURE".

UART Application Output Step 3

The next step is to click on the "CONNECT" button, after which the terminal status changes from Disconnected to Connected in green, and the data is displayed in the Received data field.

UART Application Output Step 4

Software Support

Library Description

This library contains API for DAC 9 Click driver.

Key functions:

  • dac9_set_config - Set config function

  • dac9_set_gain - Set gain function

  • dac9_set_vout - Set Vout function

Open Source

Code example

This example can be found in NECTO Studio. Feel free to download the code, or you can copy the code below.

 * @file main.c
 * @brief DAC9 Click example
 * # Description
 * This is an example that demonstrates the use of the DAC 9 Click board.
 * The demo application is composed of two sections :
 * ## Application Init
 * Initalizes SPI or I2C driver and applies default settings.
 * ## Application Task
 * Demonstrates use of DAC 9 click board by changing output values every two seconds.
 * @author Stefan Ilic

#include "board.h"
#include "log.h"
#include "dac9.h"

static dac9_t dac9;
static log_t logger;
static uint16_t res = 2500;

void application_init ( void ) {
    log_cfg_t log_cfg;  /**< Logger config object. */
    dac9_cfg_t dac9_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.
    dac9_cfg_setup( &dac9_cfg );
    DAC9_MAP_MIKROBUS( dac9_cfg, MIKROBUS_1 );
    err_t init_flag  = dac9_init( &dac9, &dac9_cfg );
    if ( ( I2C_MASTER_ERROR == init_flag ) || ( SPI_MASTER_ERROR == init_flag ) ) {
        log_error( &logger, " Application Init Error. " );
        log_info( &logger, " Please, run program again... " );

        for ( ; ; );
    log_printf( &logger, "---------------------\r\n" );
    log_printf( &logger, "     Soft reset      \r\n" );
    dac9_soft_reset( &dac9 );
    Delay_ms( 200 );

    log_printf( &logger, "---------------------\r\n" );
    log_printf( &logger, "  Vref divided by 2  \r\n" );
    log_printf( &logger, "  Set DAC gain of 2  \r\n" );
    dac9_set_gain( &dac9, DAC9_GAIN_REF_DIV_2, DAC9_GAIN_BUFF_GAIN_2 );
    Delay_ms( 100 );

    log_printf( &logger, "---------------------\r\n" );
    log_info( &logger, " Application Task " );

void application_task ( void ) {
    uint16_t n_cnt;
    for ( n_cnt = 0; n_cnt <= res; n_cnt += 500 ) {
        log_printf( &logger, "Output Voltage : %d mV\r\n", ( uint16_t ) n_cnt );
        dac9_set_vout( &dac9, n_cnt );
        Delay_ms( 2000 );

void main ( void ) {
    application_init( );

    for ( ; ; ) {
        application_task( );

// ------------------------------------------------------------------------ END

Additional Support