Our touchkey solution revolutionizes user interaction by providing a sensitive and elegant touch interface that responds effortlessly to the gentlest tap of your finger
A
A
Hardware Overview
How does it work?
TocuhKey 2 Click is based on the ATtiny817, an integrated touch QTouch® controller from Microchip. This Click is designed to run on a 3.3V power supply. The four LEDs onboard the click indicate when the Key (Pad) is pressed. TouchKey 2 click communicates with the target microcontroller over the UART interface. You can use TouchKey 2 Click in all conditions without fearing something will happen due to moisture and water droplets falling on it. The plastic overlay on the TouchKey 2 click protects the board from moisture. Thanks to this feature, the electronic components are safe. The ATtiny817 has a driven shield for improved moisture and noise-handling performance. Microchip's ATtiny817 is a
microcontroller that uses an 8-bit AVR® processor with hardware multiplier, running at up to 20MHz and with up to 8KB Flash, 512 bytes of SRAM, and 128 bytes of EEPROM. The ATtiny817 uses the latest technologies from Microchip with a flexible and low-power architecture, including Event System and SleepWalking, accurate analog features, and advanced peripherals. Capacitive touch interfaces with proximity sensing and a driven shield are supported with the integrated QTouch® peripheral touch controller. The module supports wake-up on touch from power-save sleep mode. Capacitive buttons can be toggled even when placed under a layer of glass or paper. There are four LEDs for four touch keys. If key A is pressed,
LED_A is ON, and such. In addition, there is UART communication between ATtiny817 and the main MCU. The header onboard the TouchKey 2 click can be used for device programming. Current firmware sends data packets via UART (based on the demo example in our library). SPI communication is possible with firmware modifications. 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 STM32F410RB 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-M4
MCU Memory (KB)
128
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
32768
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
Track your results in real time
Application Output via Debug Mode
1. Once the code example is loaded, pressing the "DEBUG" button initiates the build process, programs it on the created setup, and enters Debug mode.
2. After the programming is completed, a header with buttons for various actions within the IDE becomes visible. Clicking the green "PLAY" button starts reading the results achieved with the Click board™. The achieved results are displayed in the Application Output tab.
Software Support
Library Description
This library contains API for TouchKey 2 Click driver.
Key functions:
touchkey2_set_reset_pin
- Set reset pin functiontouchkey2_clear_reset_pin
- Clear reset pin functiontouchkey2_target_reset
- Reset 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
* \brief Touchkey2 Click example
*
* # Description
* This application is touch controller.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initalizes device and makes an initial log.
*
* ## Application Task
* Checks if new data byte have received in rx buffer (ready for reading),
and if ready than reads one byte from rx buffer, that show if and what key is pressed.
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "touchkey2.h"
// ------------------------------------------------------------------ VARIABLES
static touchkey2_t touchkey2;
static log_t logger;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
touchkey2_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_info( &logger, "---- Application Init ----" );
// Click initialization.
touchkey2_cfg_setup( &cfg );
TOUCHKEY2_MAP_MIKROBUS( cfg, MIKROBUS_1 );
touchkey2_init( &touchkey2, &cfg );
}
void application_task ( void )
{
char tmp;
tmp = touchkey2_generic_single_read( &touchkey2 );
if( tmp == 0x00 )
{
log_printf( &logger, " Key released\r\n" );
log_printf( &logger, "------------------- \r\n" );
}
else if( tmp == 0x01 )
{
log_printf( &logger, " Key A pressed\r\n" );
log_printf( &logger, "------------------- \r\n" );
}
else if( tmp == 0x02 )
{
log_printf( &logger, " Key B pressed\r\n" );
log_printf( &logger, "------------------- \r\n" );
}
else if( tmp == 0x04 )
{
log_printf( &logger, " Key C pressed\r\n" );
log_printf( &logger, "------------------- \r\n" );
}
else if( tmp == 0x08 )
{
log_printf( &logger, " Key D pressed \r\n" );
log_printf( &logger, "------------------- \r\n" );
}
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END