Experience the power of touch with CY8C201A0 and STM32F091RC
Tap into innovation
Published Feb 26, 2024
Click board™
CapSense Click
Dev Board
Nucleo-64 with STM32F091RC MCU
Compiler
NECTO Studio
MCU
STM32F091RC
Experience intuitive interaction like never before by integrating responsive touch controls into your projects for enhanced user experiences and functionality
A
A
Hardware Overview
How does it work?
CapSense Click is based on the CY8C201A0, a multi-channel capacitive touch sensor from Infineon Technologies. The CY8C201A0 takes human body capacitance as an input and directly provides real-time sensor information via a serial interface. The user can also configure registers with parameters needed to adjust the operation and sensitivity of the CapSense touch buttons and slider and permanently store the settings. As mentioned earlier, this board contains a 5-segment capacitive sensing slider that can detect a slide in either the UP or DOWN direction, as well as two touch button pads which are the only elements on the top side of the board. Each of these touch button pads has a
LED indicator representing the activity in that field. If a touch event is detected on one of these onboard pads, the state of the corresponding LED will be changed, indicating an activated channel; more precisely, touch has been detected on that specific field. CapSense Click communicates with MCU using the standard I2C 2-Wire interface to read data and configure settings. The CY8C201A0 contains multiple operating modes: Active, Periodic Sleep, and Deep Sleep Mode, to meet different power consumption requirements. In the case of using some of the existing Sleep modes, the user is provided with the possibility of controlling these states via the GPO pin, routed to the AN pin of the
mikroBUS™ socket, or this pin can be set in software as an interrupt pin indicating when a specific interrupt event occurs (touch detection). Besides, a Reset pin, routed to the RST pin of the mikroBUS™ socket, causes all operations of the CY8C201A0s CPU and blocks to stop and return to a pre-defined state. This Click board™ can operate with either 3.3V or 5V logic voltage levels selected via the PWR SEL jumper. This way, both 3.3V and 5V capable MCUs can use the communication lines properly. However, the Click board™ comes equipped with a library containing easy-to-use functions and an example code that can be used, as a reference, for further development.
Features overview
Development board
Nucleo-64 with STM32F091RC 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)
256
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
Start by selecting your development board and Click board™. Begin with the Nucleo-64 with STM32F091RC 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 CapSense Click driver.
Key functions:
capsense_get_slider_lvl- This function gets slider levelcapsense_read_data- Read one byte from register addresscapsense_write_data- Generic write data 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
* \brief CapSense Click example
*
* # Description
* This demo example shows level of the slider on the terminal.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes device.
*
* ## Application Task
* Waits user to press top and bottom button to turn click's LEDs ON or OFF.
* User can swipe slider to send log to the UART where one can track their changes.
*
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "capsense.h"
// ------------------------------------------------------------------ VARIABLES
static capsense_t capsense;
static log_t logger;
// ------------------------------------------------------- ADDITIONAL FUNCTIONS
void bits_to_str( uint8_t num, uint8_t *s )
{
uint8_t mask = 0x80;
while ( mask )
{
if ( num & mask )
{
*s++ = '1';
}
else
{
*s++ = '0';
}
mask >>= 1;
}
*s = '\0';
}
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
capsense_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.
capsense_cfg_setup( &cfg );
CAPSENSE_MAP_MIKROBUS( cfg, MIKROBUS_1 );
capsense_init( &capsense, &cfg );
if ( CAPSENSE_ERROR == capsense_default_cfg ( &capsense ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
static uint8_t current_led_state = 0;
uint8_t output_lvl[ 10 ] = { 0 };
uint8_t button_select = 0;
uint8_t slider_lvl = 0;
capsense_read_data( &capsense, CAPSENSE_CS_READ_STATUS0, &button_select );
capsense_get_slider_lvl( &capsense, &slider_lvl );
capsense_write_data( &capsense, CAPSENSE_OUTPUT_PORT0, current_led_state );
Delay_ms( 100 );
if ( 8 == button_select )
{
current_led_state ^= 0x01;
log_printf( &logger, "Toggle LED1\r\n");
Delay_ms( 100 );
}
if ( 16 == button_select )
{
current_led_state ^= 0x02;
log_printf( &logger, "Toggle LED2\r\n");
Delay_ms( 100 );
}
if ( 24 == button_select )
{
current_led_state = ~current_led_state;
log_printf( &logger, "Toggle both LEDs\r\n");
Delay_ms( 100 );
}
if ( slider_lvl )
{
bits_to_str( slider_lvl, output_lvl );
log_printf( &logger, "Slider level - channels [5-1]:\t%s \r\n", &output_lvl[ 3 ] );
Delay_ms( 100 );
}
}
int main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
return 0;
}
// ------------------------------------------------------------------------ END
