Transform your projects into hubs of efficiency with AP33771 and STM32F070RB
USB-C sink – Uniting speed, power, and style!
Published Feb 26, 2024
Click board™
USB-C Sink 3 Click
Dev Board
Nucleo-64 with STM32F070RB MCU
Compiler
NECTO Studio
MCU
STM32F070RB
Revolutionize your project experience with our USB-C sink solution, paving the way for faster data transfers and smarter power management.
A
A
Hardware Overview
How does it work?
USB-C Sink 3 Click is based on the AP33771, a high-performance USB PD sink controller from Diodes Incorporated. It supports up to eight voltage selections alongside ten different power range selections. In addition to selected voltages, both fixed PDO and PPS APDO in the PD source adapter are supported in the AP33771 search algorithm. The PD controller supports OVP with auto-restart, one-time programming (OTP) ROM for main firmware, and power capability selection. The onboard FAULT LED serves as a visual presentation of the negotiation mismatch. USB-C Sink 3 Click is equipped with a VSINK, an external power supply terminal that comes with a pair of MOSFETs, according to the AP33771’s driver for N-MOS VBUS power switch support. The PD controller can control the external NMOS switch ON or OFF. 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 USB-C Sink 3 Click comes with a VSEL three 2-position jumpers labeled 0, 1, and 2 to select the desired target voltage. I/O and FIX(ed) sides allow you to choose between hardware and software target voltage selection in eight positions and a target voltage range from 5V up to 17.2V. The VSEL is set to I/O by default, where you can set logic states to the three IO pins over the TCA9536, a remote 4-bit I2C, and SMBus I/O expander with configuration registers from Texas Instruments. The table of the combination of the positions and the resulting target voltages is printed at the bottom of the Click board™. You can use fixed jumper positions by setting the jumpers as you like, where I/O acts as a 0 and 3V3 as a 1 position. The 5V and 3.3V LDO voltage output can be measured over the V5V and V3V pads and voltage feedback over the VFB pad. To select the desired power, there is the MCP41100T, a digital potentiometer with an SPI interface from Microchip. Selecting the corresponding resistance
value on the digital potentiometer allows you to choose one of the current capabilities ranging from 12W to 100W. The table with the expected resistance and the resulting current is printed at the bottom of the Click board™. In addition, you can solder a standard resistor by soldering it on RES resistor pads. For that purpose, you should set the PSEL jumper to a RES position, as it is set to a POT position by default. USB-C Sink 3 Click uses a standard 2-Wire I2C interface of the MCP41100T to communicate with the host MCU. One of the main features of the USB-C Sink 3 Click is the ability to track the VBUS voltage over the AN pin of the mikroBUS™ socket. This Click board™ can be operated only with a 3.3V logic voltage level. The board must perform appropriate logic voltage level conversion before using MCUs with different logic levels. Also, it comes equipped with a library containing functions and an example code that can be used as a reference for further development.
Features overview
Development board
Nucleo-64 with STM32F070RB MCU offers a cost-effective and adaptable platform for developers to explore new ideas and prototype their designs. This board harnesses the versatility of the STM32 microcontroller, enabling users to select the optimal balance of performance and power consumption for their projects. It accommodates the STM32 microcontroller in the LQFP64 package and includes essential components such as a user LED, which doubles as an ARDUINO® signal, alongside user and reset push-buttons, and a 32.768kHz crystal oscillator for precise timing operations. Designed with expansion and flexibility in mind, the Nucleo-64 board features an ARDUINO® Uno V3 expansion connector and ST morpho extension pin
headers, granting complete access to the STM32's I/Os for comprehensive project integration. Power supply options are adaptable, supporting ST-LINK USB VBUS or external power sources, ensuring adaptability in various development environments. The board also has an on-board ST-LINK debugger/programmer with USB re-enumeration capability, simplifying the programming and debugging process. Moreover, the board is designed to simplify advanced development with its external SMPS for efficient Vcore logic supply, support for USB Device full speed or USB SNK/UFP full speed, and built-in cryptographic features, enhancing both the power efficiency and security of projects. Additional connectivity is
provided through dedicated connectors for external SMPS experimentation, a USB connector for the ST-LINK, and a MIPI® debug connector, expanding the possibilities for hardware interfacing and experimentation. Developers will find extensive support through comprehensive free software libraries and examples, courtesy of the STM32Cube MCU Package. This, combined with compatibility with a wide array of Integrated Development Environments (IDEs), including IAR Embedded Workbench®, MDK-ARM, and STM32CubeIDE, ensures a smooth and efficient development experience, allowing users to fully leverage the capabilities of the Nucleo-64 board in their projects.
Microcontroller Overview
MCU Card / MCU
Architecture
ARM Cortex-M0
MCU Memory (KB)
128
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
16384
You complete me!
Accessories
Click Shield for Nucleo-64 comes equipped with two proprietary mikroBUS™ sockets, allowing all the Click board™ devices to be interfaced with the STM32 Nucleo-64 board with no effort. This way, Mikroe allows its users to add any functionality from our ever-growing range of Click boards™, such as WiFi, GSM, GPS, Bluetooth, ZigBee, environmental sensors, LEDs, speech recognition, motor control, movement sensors, and many more. More than 1537 Click boards™, which can be stacked and integrated, are at your disposal. The STM32 Nucleo-64 boards are based on the microcontrollers in 64-pin packages, a 32-bit MCU with an ARM Cortex M4 processor operating at 84MHz, 512Kb Flash, and 96KB SRAM, divided into two regions where the top section represents the ST-Link/V2 debugger and programmer while the bottom section of the board is an actual development board. These boards are controlled and powered conveniently through a USB connection to program and efficiently debug the Nucleo-64 board out of the box, with an additional USB cable connected to the USB mini port on the board. Most of the STM32 microcontroller pins are brought to the IO pins on the left and right edge of the board, which are then connected to two existing mikroBUS™ sockets. This Click Shield also has several switches that perform functions such as selecting the logic levels of analog signals on mikroBUS™ sockets and selecting logic voltage levels of the mikroBUS™ sockets themselves. Besides, the user is offered the possibility of using any Click board™ with the help of existing bidirectional level-shifting voltage translators, regardless of whether the Click board™ operates at a 3.3V or 5V logic voltage level. Once you connect the STM32 Nucleo-64 board with our Click Shield for Nucleo-64, you can access hundreds of Click boards™, working with 3.3V or 5V logic voltage levels.
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 Nucleo-64 with STM32F070RB MCU 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 USB-C Sink 3 Click driver.
Key functions:
usbcsink3_set_voltage- USB-C Sink 3 set the voltage function.usbcsink3_set_power- USB-C Sink 3 set the power function.usbcsink3_get_vbus- USB-C Sink 3 get VBUS function.
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 USB-C Sink 3 Click example
*
* # Description
* This example demonstrates the use of USB-C Sink 3 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 SPI, I2C and ADC modules and log UART.
* After driver initialization the app set default settings:
* Voltage Selection: 5 [V] and Power: 15.0 [W].
*
* ## 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.
* It interprets power input requirements (voltage/current and maximum power) from the TCD.
* The example uses two configurations:
* - Voltage 5 [V] and Power 15.0 [W]
* - Voltage 9 [V] and Power 18.0 [W]
* Results are being sent to the Usart Terminal where you can track their changes.
*
* @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 "usbcsink3.h"
static usbcsink3_t usbcsink3;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
usbcsink3_cfg_t usbcsink3_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.
usbcsink3_cfg_setup( &usbcsink3_cfg );
USBCSINK3_MAP_MIKROBUS( usbcsink3_cfg, MIKROBUS_1 );
err_t init_flag = usbcsink3_init( &usbcsink3, &usbcsink3_cfg );
if ( ( I2C_MASTER_ERROR == init_flag ) || ( SPI_MASTER_ERROR == init_flag ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
Delay_ms( 100 );
if ( USBCSINK3_ERROR == usbcsink3_default_cfg ( &usbcsink3 ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
Delay_ms( 100 );
log_info( &logger, " Application Task " );
log_printf( &logger, " ------------------------\r\n" );
Delay_ms( 1000 );
}
void application_task ( void )
{
static float voltage = 0.0;
if ( ( USBCSINK3_OK == usbcsink3_set_voltage( &usbcsink3, USBCSINK3_VTG_SEL_5V ) ) &&
( USBCSINK3_OK == usbcsink3_set_power( &usbcsink3, USBCSINK3_PWR_SEL_15W ) ) )
{
log_printf( &logger, " Output:\r\nVoltage: 5.0 [V]\r\nPower: 15.0 [W]\r\n" );
log_printf( &logger, " - - - - - - - - - - - -\r\n" );
Delay_ms( 1000 );
usbcsink3_get_vbus ( &usbcsink3, &voltage );
log_printf( &logger, " VBUS : %.1f [V]\r\n", voltage );
log_printf( &logger, " ------------------------\r\n" );
Delay_ms( 5000 );
}
if ( ( USBCSINK3_OK == usbcsink3_set_voltage( &usbcsink3, USBCSINK3_VTG_SEL_9V ) ) &&
( USBCSINK3_OK == usbcsink3_set_power( &usbcsink3, USBCSINK3_PWR_SEL_18W ) ) )
{
log_printf( &logger, " Output:\r\nVoltage: 9.0 [V]\r\nPower: 18.0 [W]\r\n" );
log_printf( &logger, " - - - - - - - - - - - -\r\n" );
Delay_ms( 1000 );
usbcsink3_get_vbus ( &usbcsink3, &voltage );
log_printf( &logger, " VBUS : %.1f [V]\r\n", voltage );
log_printf( &logger, " ------------------------\r\n" );
Delay_ms( 5000 );
}
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
