Set, track, and achieve your wellness milestones easily with STP201M and STM32F103RB
Step by step to success: Pedometer magic in your hand
Published Oct 08, 2024
Click board™
Pedometer Click
Dev. board
Nucleo 64 with STM32F103RB MCU
Compiler
NECTO Studio
MCU
STM32F103RB
Our pedometer is your reliable companion for tracking daily steps, empowering you to achieve your fitness goals with precision
A
A
Hardware Overview
How does it work?
Pedometer Click is based on the STP201M, a 3D pedometer module with an IC chipset from NiceRF. The module itself is designed for wrist pedometer products, like the pedometer bracelet or watch for example. The end user doesn’t have to worry about doing any calculations on their own, or worry about what the algorithm for step detection is doing, since the INT pins output is already a measurement of the steps that were taken. Specifically, a MEMS sensor. Micro-electro-mechanical system sensors, abbreviated to MEMS, are made out of very small components, with their size usually ranging from 1 to 100 micrometers. These account for the sensor being very small and therefore it having low energy consumption and
also not requiring a lot of space. This particular sensor is a 3D one. The three axes it utilizes, allow for precise measurements of any movement and the direction its taking. The three axes system, along with the MCUs meticulous algorithm, make it significantly less likely to make any false-positive counts (ex. tying up shoes). The MCU has two distinguished modes. The first one of them is the operational mode. The MCU is designed to go into the operational mode whenever it senses some activity. However, if there is no discernible movement over the course of 20 seconds, it goes into the sleep mode. This mode is characterized by the very low energy consumption of only 5 μA max. The STP201M modules communication is
somewhat different from the standard I2C protocol. Since our libraries do not support it, the user has the capability of changing the code of the main MCU in order to fit the protocol of the module and thus change any preprogramed settings. Since the modules maximum operatin voltage is 3.6V, the Pedometer click uses the 3.3V rail for power supply. The other pins it utilizes are the, before mentioned, Interrupt pin, and the I2C Clock and Data pins. This click also has a Power LED indicator. This Click Board™ is designed to be operated only with 3.3V logic level. A proper logic voltage level conversion should be performed before the Click board™ is used with MCUs with logic levels of 5V.
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 Pedometer Click driver.
Key functions:
pedometer_get_interrupt_state- Functions for get Interrupt state on the INT pinpedometer_get_step_counter- Functions for get step counterpedometer_generic_read- Generic read 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 Pedometer Click example
*
* # Description
* This application detected steps.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes driver init and sets step counter on 0.
*
* ## Application Task
* It checks if a new step is detected, if detected new step -
* reads the current number of steps made and logs data to the USBUART.
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "pedometer.h"
// ------------------------------------------------------------------ VARIABLES
static pedometer_t pedometer;
static log_t logger;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
pedometer_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.
pedometer_cfg_setup( &cfg );
PEDOMETER_MAP_MIKROBUS( cfg, MIKROBUS_1 );
pedometer_init( &pedometer, &cfg );
}
void application_task ( void )
{
// Task implementation.
uint8_t new_step;
uint32_t s_counter;
char demoText[ 50 ];
new_step = pedometer_process( &pedometer );
if ( new_step == PEDOMETER_NEW_STEP_DETECTED )
{
s_counter = pedometer_get_step_counter( &pedometer );
log_printf( &logger, " Step Counter : %d \r\n ", s_counter );
Delay_ms( 50 );
}
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
