Skip to content

Latest commit

 

History

History

uts7segr

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 
 
 
 
 

UT-S 7-SEG R Click

UT-S 7-SEG R Click demo application is developed using the NECTO Studio, ensuring compatibility with mikroSDK's open-source libraries and tools. Designed for plug-and-play implementation and testing, the demo is fully compatible with all development, starter, and mikromedia boards featuring a mikroBUS™ socket.


Click Library

  • Author : Jelena Milosavljevic
  • Date : Jun 2021.
  • Type : SPI type

Software Support

Example Description

The demo application shows basic usage of the UT 7 SEG display.

Example Libraries

  • MikroSDK.Board
  • MikroSDK.Log
  • Click.UT-S7-SEGR

Example Key Functions

  • uts7segr_cfg_setup Config Object Initialization function.
void uts7segr_cfg_setup ( uts7segr_cfg_t *cfg );
  • uts7segr_init Initialization function.
err_t uts7segr_init ( uts7segr_t *ctx, uts7segr_cfg_t *cfg );
  • uts7segr_default_cfg Click Default Configuration function.
void uts7segr_default_cfg ( uts7segr_t *ctx );
  • uts7segr_generic_write This function writes a desired number of data bytes starting from the selected register by using SPI serial interface.
err_t uts7segr_generic_write ( uts7segr_t *ctx, uint8_t *data_in );
  • uts7segr_display_state This function display state.
void uts7segr_display_state ( uts7segr_t *ctx, uint8_t state );
  • uts7segr_display_number This function displays number on dispaly matrix.
err_t uts7segr_display_number ( uts7segr_t *ctx, uint8_t number, uint8_t dot_pos );

Application Init

Configuring Clicks and log objects. Settings the Click in the default configuration.

void application_init ( void ) 
{
    log_cfg_t log_cfg;            /**< Logger config object. */
    uts7segr_cfg_t uts7segr_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 );
    Delay_ms ( 100 );
    log_info( &logger, " Application Init " );
    // Click initialization.

    uts7segr_cfg_setup( &uts7segr_cfg );
    UTS7SEGR_MAP_MIKROBUS( uts7segr_cfg, MIKROBUS_1 );
    err_t init_flag  = uts7segr_init( &uts7segr, &uts7segr_cfg );
    if ( init_flag == SPI_MASTER_ERROR ) {
        log_error( &logger, " Application Init Error. " );
        log_info( &logger, " Please, run program again... " );

        for ( ; ; );
    }

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

Application Task

Draws numbers from 0 to 99 on the screen.

void application_task ( void ) 
{ 
    log_info( &logger, "---- Number counter ----" );

    for ( uint8_t cnt = 0; cnt < 100; cnt++ ) {
        uts7segr_display_number( &uts7segr, cnt, UTS7SEGR_DOT_LEFT );
        Delay_ms ( 500 );
    }
}

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.

Additional Notes and Information

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.