TOP Contributors

  1. MIKROE (2762 codes)
  2. Alcides Ramos (374 codes)
  3. Shawon Shahryiar (307 codes)
  4. jm_palomino (118 codes)
  5. Bugz Bensce (90 codes)
  6. S P (73 codes)
  7. dany (71 codes)
  8. MikroBUS.NET Team (35 codes)
  9. NART SCHINACKOW (34 codes)
  10. Armstrong Subero (27 codes)

Most Downloaded

  1. Timer Calculator (139250 times)
  2. FAT32 Library (71746 times)
  3. Network Ethernet Library (57120 times)
  4. USB Device Library (47429 times)
  5. Network WiFi Library (43082 times)
  6. FT800 Library (42403 times)
  7. GSM click (29835 times)
  8. mikroSDK (28074 times)
  9. PID Library (26885 times)
  10. microSD click (26198 times)
Libstock prefers package manager

Package Manager

We strongly encourage users to use Package manager for sharing their code on Libstock website, because it boosts your efficiency and leaves the end user with no room for error. [more info]

< Back
mikroSDK Library

USB-C Sink Click

Rating:

0

Author: MIKROE

Last Updated: 2024-10-31

Package Version: 2.1.0.13

mikroSDK Library: 2.0.0.0

Category: USB-C PD

Downloaded: 155 times

Not followed.

License: MIT license  

USB-C Sink Click is a compact add-on board that contains a standalone autonomous USB power delivery controller. This board features the STUSB4500, a USB-C sink-only controller compatible with Power-Delivery (PD) from STMicroelectronics. It supports dead battery mode to allow a system to be powered from an external source directly, establishes a valid source-to-sink connection, and negotiates a USB power delivery (PD) contract with a PD capable source device.

No Abuse Reported

Do you want to subscribe in order to receive notifications regarding "USB-C Sink Click" changes.

Do you want to unsubscribe in order to stop receiving notifications regarding "USB-C Sink Click" changes.

Do you want to report abuse regarding "USB-C Sink Click".

  • mikroSDK Library 1.0.0.0
  • Comments (0)

mikroSDK Library Blog


USB-C Sink Click

USB-C Sink Click is a compact add-on board that contains a standalone autonomous USB power delivery controller. This board features the STUSB4500, a USB-C sink-only controller compatible with Power-Delivery (PD) from STMicroelectronics. It supports dead battery mode to allow a system to be powered from an external source directly, establishes a valid source-to-sink connection, and negotiates a USB power delivery (PD) contract with a PD capable source device.

usbcsink_click.png

Click Product page


Click library

  • Author : Stefan Ilic
  • Date : Aug 2021.
  • Type : I2C type

Software Support

We provide a library for the USBCSink Click as well as a demo application (example), developed using MikroElektronika compilers. The demo can run on all the main MikroElektronika development boards.

Package can be downloaded/installed directly from NECTO Studio Package Manager(recommended way), downloaded from our LibStock™ or found on Mikroe github account.

Library Description

This library contains API for USBCSink Click driver.

Standard key functions :

  • usbcsink_cfg_setup Config Object Initialization function.

    void usbcsink_cfg_setup ( usbcsink_cfg_t *cfg );
  • usbcsink_init Initialization function.

    err_t usbcsink_init ( usbcsink_t *ctx, usbcsink_cfg_t *cfg );

Example key functions :

  • usbcsink_hw_reset HW reset function.

    void usbcsink_hw_reset ( usbcsink_t *ctx );
  • usbcsink_get_pdo2 Get PO2 pin state function.

    uint8_t usbcsink_get_pdo2 ( usbcsink_t *ctx );
  • usbcsink_write_byte Write byte function.

    void usbcsink_write_byte ( usbcsink_t *ctx, uint8_t reg, uint8_t tx_data );

Example Description

This is an example which demonstrates the use of USB-C Sink Click board.

The demo application is composed of two sections :

Application Init

Initialization driver enables - I2C, set hw reset, set PDO2 profile and current value for PDO2 1.5A, upload new data and reset device to write NVM settings to the STUSB450, also write log.


void application_init ( void ) {
    log_cfg_t log_cfg;  /**< Logger config object. */
    usbcsink_cfg_t usbcsink_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.
    usbcsink_cfg_setup( &usbcsink_cfg );
    USBCSINK_MAP_MIKROBUS( usbcsink_cfg, MIKROBUS_1 );
    err_t init_flag = usbcsink_init( &usbcsink, &usbcsink_cfg );
    if ( I2C_MASTER_ERROR == init_flag ) {
        log_error( &logger, " Application Init Error. " );
        log_info( &logger, " Please, run program again... " );

        for ( ; ; );
    }

    usbcsink_hw_reset( &usbcsink );
    Delay_ms ( 1000 );

    usbcsink_set_pdo_num( USBCSINK_SET_PDO_2 );
    usbcsink_set_current( USBCSINK_SET_PDO_2, 1.5 );

    sel_profile = usbcsink_get_pdo_num( );
    log_printf( &logger , "- - - - - - - - - - - - \r\n" );
    log_printf( &logger , "   Setting PDO ~ PDO%d \r\n", ( uint16_t ) sel_profile );
    log_printf( &logger , "- - - - - - - - - - - - \r\n" );

    usbcsink_upload_new_data( &usbcsink, USBCSINK_UPLOAD_NEW_DATA_VAL );
    Delay_ms ( 1000 );

    usbcsink_hw_reset( &usbcsink );
    Delay_ms ( 1000 );

    log_info( &logger, " Application Task " );
}

Application Task

USB-C Sink Click board can be used to read the Power Data Objects (PDO) highest priority profile: PDO1 : 5V, PDO2 : 12V, PDO3 : 20V. All data logs write on USB uart changes for every 5 sec.


void application_task ( void ) {
    usbcsink_load_data( &usbcsink );

    log_printf( &logger , "     New Parameters     \r\n" );
    log_printf( &logger , "------------------------\r\n" );

    sel_profile = usbcsink_get_pdo_num( );

    log_printf( &logger , "    PDO Number ~ PDO%d\r\n", ( uint16_t ) sel_profile );
    log_printf( &logger , "- - - - - - - - - - - - \r\n" );

    demo_data = usbcsink_get_voltage( sel_profile );
    log_printf( &logger , " Voltage : %.2f V\r\n", demo_data );

    demo_data = usbcsink_get_current( sel_profile );
    log_printf( &logger , " Current :  %.2f A\r\n", demo_data );

    log_printf( &logger , "------------------------\r\n" );
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );
}

The full application code, and ready to use projects can be installed directly from NECTO Studio Package Manager(recommended way), downloaded from our LibStock™ or found on Mikroe github account.

Other Mikroe Libraries used in the example:

  • MikroSDK.Board
  • MikroSDK.Log
  • Click.USBCSink

Additional notes and informations

Depending on the development board you are using, you may need USB UART Click, USB UART 2 Click or RS232 Click to connect to your PC, for development systems with no UART to USB interface available on the board. UART terminal is available in all MikroElektronika compilers.


ALSO FROM THIS AUTHOR

TempHum 3 Click

0

Temp&Hum 3 Click is a smart environmental temperature and humidity sensor Click board™, packed with features which allow easy and simple integration into any design that requires accurate and reliable humidity and temperature measurements

[Learn More]

AudioAmp 2 click

5

Audio Amp 2 click is a highly efficient class D audio amplifier, using the TDA7491, a dual BTL class-D audio amplifier IC, capable of delivering up to 20W to 8Ω load.

[Learn More]

Accel 21 Click

0

Accel 21 Click is a compact add-on board that contains an acceleration sensor. This board features the MIS2DH, a high-performance three-axis accelerometer from STMicroelectronics. The MIS2DH allows selectable full-scale acceleration measurements in ranges of ±2g, ±4g, ±8g, or ±16g in three axes with a configurable host interface that supports both SPI and I2C serial communication. It also supports high-resolution and low-power operating modes, allowing maximum flexibility to meet various use case needs.

[Learn More]