10 min

Experience the future of seamless charging and data synchronization with AP33772 and STM32F765ZI

Versatile power delivery for a truly connected lifestyle

USB-C Sink 2 Click with UNI-DS v8

Published Nov 13, 2023

Click board™

USB-C Sink 2 Click

Development board



NECTO Studio



Transform the way you connect and charge with our cutting-edge USB-C sink solution, delivering reliability and performance beyond expectations



Hardware Overview

How does it work?

USB-C Sink 2 Click is based on the AP33772, a high-performance USB PD sink controller from Diodes Incorporated. The host MCU can control the PPS with 20mV/step voltage and 50mA/step current. The PD controller supports overtemperature protection (OTP), OVP with auto-restart, OCP with auto-restart, one-time programming (OTP), power-saving mode, and a system monitor and control status register. For OTP, this Click board™ comes with an NTC temperature sensor, with selectable temperature points (25°C, 50°C, 75°C, 100°C) as a temperature threshold. The onboard FAULT LED serves as a visual presentation of the negotiation mismatch. The Multi-time programming (MTP) is reserved for future configuration. This USB Type-C power delivery sink controller requires power from a

standard USB source adapter, in our case from the USB connector labeled USB-C PD-IN, and then delivers power to connected devices on the VSINK connector. A pair of MOSFETs stands between the USB and VSINK terminal, according to the AP33772 driver for N-MOS VBUS power switch support. The PD controller can control the external NMOS switch ON or OFF (all control is done via the I2C interface). The USB C connector acts as a PD-IN discharge path terminal with a USB Type-C configuration channels 1 and 2. The presence of the power supply on the USB C is indicated over the VBUS LED. The AP33772 is equipped with several GPIOs. The user-configurable GPIO1 and GPIO2 are available on the side header labeled GP1 and GP2, with additional GND. Also, this Click board™ has several test pads for testing

purposes. The 5V and 3.3V LDO voltage output can be measured over the V5V and V3V pads and voltage feedback over the VFB pad. USB-C Sink 2 Click uses a standard 2-Wire I2C interface to communicate with the host MCU. The interrupts from AP33772 can be monitored over the INT pin. One of the additional features of the USB-C Sink 2 Click is the ability to track the VBUS voltage over the AN pin of the mikroBUS™ socket. 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.

USB-C Sink 2 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


ARM Cortex-M7

MCU Memory (KB)


Silicon Vendor


Pin count


RAM (Bytes)


Used MCU Pins

mikroBUS™ mapper

Analog Output
Power Supply
I2C Clock
I2C Data
Power Supply

Take a closer look


USB-C Sink 2 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 USB-C Sink 2 Click driver.

Key functions:

  • usbcsink2_write_rdo - USB-C Sink 2 write the RDO function.

  • usbcsink2_get_pdo_voltage - USB-C Sink 2 get the voltage function.

  • usbcsink2_get_pdo_current - USB-C Sink 2 get the current 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 USB-C Sink 2 Click Example.
 * # Description
 * This example demonstrates the use of the USB-C Sink 2 Click board™ 
 * by setting DC power requests and control for Type-C connector-equipped devices (TCD).
 * The demo application is composed of two sections :
 * ## Application Init
 * Initializes I2C and ADC modules and log UART.
 * After driver initialization the app set default settings.
 * ## Application Task
 * In this example, the app configures Power Data Objects (PDO) 
 * highest priority profile and requests power from a standard USB PD source adapter.
 * After connecting the PD source and USB-C Sink 2 Click with the Type-C cable,
 * the app gets the total number of valid PDO's 
 * and switches all PDO configurations every 10 seconds.
 * When the PD source accepts the request, the app displays information about 
 * VOUT Voltage [mV] and Current [mA] and the temperature [degree Celsius] of the USB-C connector.
 * @note
 * FAULT LED flickering notified of the system status:
 *  - Charging: Breathing light (2 sec dimming), 1 cycle is 4 sec.
 *  - Fully charged: Continuously lit Charging current < 500mA.
 *  - Mismatch: 1s flicker Voltage or power mismatch. Non-PD power source, 1 cycle is 2sec.
 *  - Fault: 300ms flicker OVP, 1 cycle is 600ms.
 * @author Nenad Filipovic

#include "board.h"
#include "log.h"
#include "usbcsink2.h"

static usbcsink2_t usbcsink2;   /**< USB-C Sink 2 Click driver object. */
static log_t logger;    /**< Logger object. */

void application_init ( void )
    log_cfg_t log_cfg;  /**< Logger config object. */
    usbcsink2_cfg_t usbcsink2_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.
    usbcsink2_cfg_setup( &usbcsink2_cfg );
    USBCSINK2_MAP_MIKROBUS( usbcsink2_cfg, MIKROBUS_1 );
    err_t init_flag = usbcsink2_init( &usbcsink2, &usbcsink2_cfg );
    if ( ( ADC_ERROR == init_flag ) || ( I2C_MASTER_ERROR == init_flag ) )
        log_error( &logger, " Communication init." );
        for ( ; ; );
    if ( USBCSINK2_ERROR == usbcsink2_default_cfg ( &usbcsink2 ) )
        log_error( &logger, " Default configuration." );
        for ( ; ; );
    log_info( &logger, " Application Task " );
    log_printf( &logger, "---------------------------\r\n" );
    Delay_ms( 100 );

void application_task ( void ) 
    static float voltage_mv = 0, current_ma = 0;
    static uint8_t temperature = 0;
    for ( uint8_t pdo_num = 0; pdo_num < usbcsink2.number_of_valid_pdo; pdo_num++ )
        usbcsink2.pdo_data[ pdo_num * 4 + 3 ] = ( pdo_num + 1 ) << 4;
        if ( USBCSINK2_OK == usbcsink2_write_rdo( &usbcsink2, &usbcsink2.pdo_data[ pdo_num * 4 ] ) )
            log_printf( &logger, " --- PDO[ %d ] ---\r\n", ( uint16_t ) pdo_num );
        if ( USBCSINK2_OK == usbcsink2_wait_rdo_req_success( &usbcsink2 ) )
            if ( USBCSINK2_OK == usbcsink2_get_pdo_voltage( &usbcsink2, &voltage_mv ) )
                log_printf( &logger, " Voltage : %.2f mV\r\n", voltage_mv );
            if ( USBCSINK2_OK == usbcsink2_get_pdo_current( &usbcsink2, &current_ma ) )
                log_printf( &logger, " Current : %.2f mA\r\n", current_ma );
            if ( USBCSINK2_OK == usbcsink2_get_temperature( &usbcsink2, &temperature ) )
                log_printf( &logger, " Temperature : %d C\r\n", ( uint16_t ) temperature );
            log_printf( &logger, "---------------------------\r\n" );
            Delay_ms( 10000 );

void main ( void ) 
    application_init( );

    for ( ; ; ) 
        application_task( );

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

Additional Support