TOP Contributors

  1. MIKROE (2784 codes)
  2. Alcides Ramos (405 codes)
  3. Shawon Shahryiar (307 codes)
  4. jm_palomino (133 codes)
  5. Bugz Bensce (97 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 (142015 times)
  2. FAT32 Library (75248 times)
  3. Network Ethernet Library (59470 times)
  4. USB Device Library (49488 times)
  5. Network WiFi Library (45266 times)
  6. FT800 Library (44873 times)
  7. GSM click (31414 times)
  8. mikroSDK (30400 times)
  9. microSD click (27776 times)
  10. PID Library (27613 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

2x2 key Click

Rating:

0

Author: MIKROE

Last Updated: 2024-10-31

Package Version: 2.1.0.20

mikroSDK Library: 2.0.0.0

Category: Pushbutton/Switches

Downloaded: 595 times

Not followed.

License: MIT license  

2x2 Key Click has a 4 button keypad and allows multiple key presses.

No Abuse Reported

Do you want to subscribe in order to receive notifications regarding "2x2 key Click" changes.

Do you want to unsubscribe in order to stop receiving notifications regarding "2x2 key Click" changes.

Do you want to report abuse regarding "2x2 key Click".

  • mikroSDK Library 1.0.0.0
  • Comments (0)

mikroSDK Library Blog


2x2 key Click

2x2 Key Click has a 4 button keypad and allows multiple key presses.

2x2key_click.png

Click Product page


Click library

  • Author : Mihajlo Djordjevic
  • Date : Dec 2019.
  • Type : GPIO type

Software Support

We provide a library for the 2x2key 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 form compilers IDE(recommended way), or downloaded from our LibStock, or found on mikroE github account.

Library Description

This library contains API for 2x2key Click driver.

Standard key functions :

  • Config Object Initialization function.

    void c2x2key_cfg_setup ( c2x2key_cfg_t *cfg );

  • Initialization function.

    C2X2KEY_RETVAL c2x2key_init ( c2x2key_t ctx, c2x2key_cfg_t cfg );

  • Click Default Configuration function.

    void c2x2key_default_cfg ( c2x2key_t *ctx );

Example key functions :

  • This function gets state of AN pin on 2X2_Key Click board.

    uint8_t c2x2key_t1_state ( c2x2key_t *ctx );

  • This function gets state of RST pin on 2X2_Key Click board.

    uint8_t c2x2key_t2_state ( c2x2key_t *ctx );

  • This function gets state of CS pin on 2X2_Key Click board.

    uint8_t c2x2key_t3_state ( c2x2key_t *ctx );

  • This function gets state of PWM pin on 2X2_Key Click board.

    uint8_t c2x2key_t4_state ( c2x2key_t *ctx );

Examples Description

This example code demonstrates the usage of 2X2 Key Click board.

The demo application is composed of two sections :

Application Init

Application Init performs Logger and Click initialization.


void application_init ( void )
{
    log_cfg_t log_cfg;
    c2x2key_cfg_t cfg;

    /** 
     * 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_printf( &logger, "-- Application  Init --\r\n" );
    Delay_ms ( 1000 );

    //  Click initialization.

    c2x2key_cfg_setup( &cfg );
    C2X2KEY_MAP_MIKROBUS( cfg, MIKROBUS_1 );
    c2x2key_init( &c2x2key, &cfg );

    log_printf( &logger, "-----------------------\r\n" );
    log_printf( &logger, "     2X2 key Click     \r\n" );
    log_printf( &logger, "-----------------------\r\n" );
    Delay_ms ( 1000 );

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

Application Task

Application Task detects whether any of the keys is pressed, and results are being sent to the UART Terminal where you can track changes.


void application_task ( void )
{
   t1_state = c2x2key_t1_state( &c2x2key );

   if ( t1_state == 1 && t1_state_old == 0 )
    {
        log_printf( &logger, "-----------------------\r\n" );
        log_printf( &logger, "     Key 1 pressed     \r\n" );
        log_printf( &logger, "-----------------------\r\n" );
        t1_state_old = 1;
    }

    if ( t1_state == 0 && t1_state_old == 1 )
    {
        t1_state_old = 0;
    }

    t2_state = c2x2key_t2_state( &c2x2key );

   if ( t2_state == 1 && t2_state_old == 0 )
    {
        log_printf( &logger, "-----------------------\r\n" );
        log_printf( &logger, "     Key 2 pressed     \r\n" );
        log_printf( &logger, "-----------------------\r\n" );
        t2_state_old = 1;
    }

    if ( t2_state == 0 && t2_state_old == 1 )
    {
        t2_state_old = 0;
    }

    t3_state = c2x2key_t3_state( &c2x2key );

   if ( t3_state == 1 && t3_state_old == 0 )
    {
        log_printf( &logger, "-----------------------\r\n" );
        log_printf( &logger, "     Key 3 pressed     \r\n" );
        log_printf( &logger, "-----------------------\r\n" );
        t3_state_old = 1;
    }

    if ( t3_state == 0 && t3_state_old == 1 )
    {
        t3_state_old = 0;
    }

    t4_state = c2x2key_t4_state( &c2x2key );

   if ( t4_state == 1 && t4_state_old == 0 )
    {
        log_printf( &logger, "-----------------------\r\n" );
        log_printf( &logger, "     Key 4 pressed     \r\n" );
        log_printf( &logger, "-----------------------\r\n" );
        t4_state_old = 1;
    }

    if ( t4_state == 0 && t4_state_old == 1 )
    {
        t4_state_old = 0;
    }
} 

The full application code, and ready to use projects can be installed directly form compilers IDE(recommneded) or found on LibStock page or mikroE GitHub accaunt.

Other mikroE Libraries used in the example:

  • MikroSDK.Board
  • MikroSDK.Log
  • Click.2x2key

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. The terminal available in all Mikroelektronika compilers, or any other terminal application of your choice, can be used to read the message.


ALSO FROM THIS AUTHOR

eINK 2.90 inch display

0

eINK click is an adapter Click boardâ„¢, used to interface a compatible eINK display with the host MCU.

[Learn More]

UART to I2C Click

0

UART to I2C Click is a compact add-on board allowing connections to UART controllers and I2C targets for protocol conversion. This board features the SC18IM704, a bridge between the standard UART host interface and a serial I2C bus from NXP Semiconductors. The SC18IM704 provides a high-speed UART interface with a baud rate of up to 460.8 kbit/s and 256-byte FIFO for the transfer/receive data process, alongside several user-configurable GPIO pins. The host MCU communicates with the SC18IM704 with ASCII messages protocol, allowing it to control all the specific I2C-bus sequences, protocol, arbitration, and timing.

[Learn More]

FreeRTOS V9.0.0 MikroC Examples

15

These examples demonstrate the usage of FreeRTOS V9.0.0 in MikroC PRO for ARM, MikroC PRO for dsPIC and MikroC PRO for PIC32.

[Learn More]