Switch signals between their pull-up or pull-down states with DTH-08 and STM32F103RB
Simple yet effective way to manage signal states for electronic projects, enhancing their reliability and performance
Published Oct 08, 2024
Click board™
EasyPull Click
Dev. board
Nucleo 64 with STM32F103RB MCU
Compiler
NECTO Studio
MCU
STM32F103RB
Configure used mikroBUS™ signals within applications to be either in a pull-up or pull-down state
A
A
Hardware Overview
How does it work?
EasyPull Click is a compact add-on board designed to empower users to easily configure used mikroBUS™ signals within their applications to be either in a pull-up or pull-down state. This board is equipped with two 8-position switches that enable the pull-up or pull-down configuration for mikroBUS™ signals such as AN, RST, PWM, and INT, as well as for communication protocols like SPI, UART, and I2C. All resistors on the EasyPull Click are set to 4.7kΩ, ensuring consistent performance across various signal lines. Whether for prototyping or final product development, EasyPull Click provides developers with a practical tool for enhancing their projects with reliable signal management capabilities. Configuring the signal lines to the desired state is straightforward, thanks to the clear directional arrows on each switch's left
side. These arrows indicate the direction to toggle the switch to achieve either a pull-up (upward direction) or pull-down (downward direction) state. This feature allows for quick and easy adjustments, enhancing the board's usability and flexibility in different project setups. Additionally, the EasyPull Click board™ offers an unpopulated header marked as EXT, which extends four signals from the switches - two from each - labeled as EXTx. This header can be used as a conventional GPIO (General Purpose Input/Output) signal according to the user's requirements. The board also includes two sets of unmarked resistors at the top, connected to the EXT signals, maintaining the 4.7kΩ resistance value consistent with the rest of the board. A unique feature of the EasyPull Click is its low-power mode capability, achieved by cutting
the ID CUT traces on the back of the board. The connection to the lower section of the board, which includes the power (PWR) LED and ID chip, is interrupted by cutting these lines. This action results in significant energy savings, making the EasyPull Click an excellent choice for energy-sensitive applications that require efficient power management. This Click board™ can operate with either 3.3V or 5V logic voltage levels selected via the VCC SEL jumper. This way, both 3.3V and 5V capable MCUs can use the communication lines properly. Also, this 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 STM32F103RB 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-M3
MCU Memory (KB)
128
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
20480
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 STM32F103RB MCU as your development board.
Track your results in real time
Application Output
1. Application Output - In Debug mode, the 'Application Output' window enables real-time data monitoring, offering direct insight into execution results. Ensure proper data display by configuring the environment correctly using the provided tutorial.
2. UART Terminal - Use the UART Terminal to monitor data transmission via a USB to UART converter, allowing direct communication between the Click board™ and your development system. Configure the baud rate and other serial settings according to your project's requirements to ensure proper functionality. For step-by-step setup instructions, refer to the provided tutorial.
3. Plot Output - The Plot feature offers a powerful way to visualize real-time sensor data, enabling trend analysis, debugging, and comparison of multiple data points. To set it up correctly, follow the provided tutorial, which includes a step-by-step example of using the Plot feature to display Click board™ readings. To use the Plot feature in your code, use the function: plot(*insert_graph_name*, variable_name);. This is a general format, and it is up to the user to replace 'insert_graph_name' with the actual graph name and 'variable_name' with the parameter to be displayed.
Software Support
Library Description
This library contains API for EasyPull Click driver.
Key functions:
easypull_get_an_pin- This function reads the state of the AN pin of EasyPull click boardeasypull_get_rst_pin- This function reads the state of the RST pin of EasyPull click boardeasypull_get_cs_pin- This function reads the state of the CS pin of EasyPull click board
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 main.c
* @brief EasyPull Click Example.
*
* # Description
* This example demonstrates the use of PIR 2 Click boards.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and USB UART logger.
*
* ## Application Task
* It checks the state of the pins and displays their state on the USB UART.
*
* @author Stefan Ilic
*
*/
#include "board.h"
#include "log.h"
#include "easypull.h"
static easypull_t easypull; /**< EasyPull Click driver object. */
static log_t logger; /**< Logger object. */
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
easypull_cfg_t easypull_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.
easypull_cfg_setup( &easypull_cfg );
EASYPULL_MAP_MIKROBUS( easypull_cfg, MIKROBUS_1 );
if ( DIGITAL_OUT_UNSUPPORTED_PIN == easypull_init( &easypull, &easypull_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
if ( EASYPULL_PIN_STATE_HIGH == easypull_get_an_pin( &easypull ) )
{
log_printf( &logger, " AN pin state: HIGH \n" );
}
else
{
log_printf( &logger, " AN pin state: LOW \n" );
}
if ( EASYPULL_PIN_STATE_HIGH == easypull_get_rst_pin( &easypull ) )
{
log_printf( &logger, " RST pin state: HIGH \n" );
}
else
{
log_printf( &logger, " RST pin state: LOW \n" );
}
if ( EASYPULL_PIN_STATE_HIGH == easypull_get_cs_pin( &easypull ) )
{
log_printf( &logger, " CS pin state: HIGH \n" );
}
else
{
log_printf( &logger, " CS pin state: LOW \n" );
}
if ( EASYPULL_PIN_STATE_HIGH == easypull_get_pwm_pin( &easypull ) )
{
log_printf( &logger, " PWM pin state: HIGH \n" );
}
else
{
log_printf( &logger, " PWM pin state: LOW \n" );
}
if ( EASYPULL_PIN_STATE_HIGH == easypull_get_int_pin( &easypull ) )
{
log_printf( &logger, " INT pin state: HIGH \n" );
}
else
{
log_printf( &logger, " INT pin state: LOW \n" );
}
log_printf( &logger, "- - - - - - - - - - - - - \r\n" );
Delay_ms( 1000 );
}
int main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
return 0;
}
// ------------------------------------------------------------------------ END
