Upgrade your project capabilities with precise air pressure measurements across various environments, perfect for applications like weather monitoring, portable devices, and immersive virtual experiences
A
A
Hardware Overview
How does it work?
Barometer 13 Click is based on the BMP585, a barometric pressure sensor from Bosch Sensortec. It consists of a pressure-sensitive MEMS sensor element and an integrated circuit that drives and reads out the sensor element. The on-chip FIFO buffer can hold up to 32 pressure samples with an absolute pressure accuracy of ±30Pa. The sensor itself can work in normal, forced, and continuous modes, while in standby mode, no measurements are performed, and power consumption is at a minimum. There is also a deep standby mode with
further reduced power consumption. The BMP585 has a built-in dedicated IIR filter that can reduce noise caused by ambient disturbances, such as an open window, door, and more. Barometer 13 Click can use a standard 2-wire I2C interface to communicate with the host MCU, with a clock frequency of up to 1MHz. The I2C address can be selected over the ADDR SEL jumper. You can also use a standard 4-wire SPI interface for the same purpose, with a clock frequency of up to 12MHz. The selection can be made over the COMM SEL
jumpers. The BMP585 provides an interrupt functionality, which allows it to signal certain events to the host processor over the INT pin. 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
Clicker 2 for Kinetis is a compact starter development board that brings the flexibility of add-on Click boards™ to your favorite microcontroller, making it a perfect starter kit for implementing your ideas. It comes with an onboard 32-bit ARM Cortex-M4F microcontroller, the MK64FN1M0VDC12 from NXP Semiconductors, two mikroBUS™ sockets for Click board™ connectivity, a USB connector, LED indicators, buttons, a JTAG programmer connector, and two 26-pin headers for interfacing with external electronics. Its compact design with clear and easily recognizable silkscreen markings allows you to build gadgets with unique functionalities and
features quickly. Each part of the Clicker 2 for Kinetis development kit contains the components necessary for the most efficient operation of the same board. In addition to the possibility of choosing the Clicker 2 for Kinetis programming method, using a USB HID mikroBootloader or an external mikroProg connector for Kinetis programmer, the Clicker 2 board also includes a clean and regulated power supply module for the development kit. It provides two ways of board-powering; through the USB Micro-B cable, where onboard voltage regulators provide the appropriate voltage levels to each component on the board, or
using a Li-Polymer battery via an onboard battery connector. All communication methods that mikroBUS™ itself supports are on this board, including the well-established mikroBUS™ socket, reset button, and several user-configurable buttons and LED indicators. Clicker 2 for Kinetis is an integral part of the Mikroe ecosystem, allowing you to create a new application in minutes. Natively supported by Mikroe software tools, it covers many aspects of prototyping thanks to a considerable number of different Click boards™ (over a thousand boards), the number of which is growing every day.
Microcontroller Overview
MCU Card / MCU

Architecture
ARM Cortex-M4
MCU Memory (KB)
1024
Silicon Vendor
NXP
Pin count
121
RAM (Bytes)
262144
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
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 Barometer 13 Click driver.
Key functions:
barometer13_get_measurement_data
- Barometer 13 get the measurement data functionbarometer13_set_odr
- Barometer 13 set the output data rate functionbarometer13_set_int_cfg
- Barometer 13 set the interrupt config 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 main.c
* @brief Barometer 13 Click example
*
* # Description
* This example demonstrates the use of Barometer 13 Click board™
* by reading and displaying the pressure and temperature measurements.
*
* The demo application is composed of two sections :
*
* ## Application Init
* The initialization of I2C or SPI module and log UART.
* After driver initialization, the app sets the default configuration.
*
* ## Application Task
* The demo application reads and displays the Pressure [mBar] and Temperature [degree Celsius] data.
* Results are being sent to the UART Terminal, where you can track their changes.
*
* @author Nenad Filipovic
*
*/
#include "board.h"
#include "log.h"
#include "barometer13.h"
static barometer13_t barometer13;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
barometer13_cfg_t barometer13_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.
barometer13_cfg_setup( &barometer13_cfg );
BAROMETER13_MAP_MIKROBUS( barometer13_cfg, MIKROBUS_1 );
err_t init_flag = barometer13_init( &barometer13, &barometer13_cfg );
if ( ( I2C_MASTER_ERROR == init_flag ) || ( SPI_MASTER_ERROR == init_flag ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
if ( BAROMETER13_ERROR == barometer13_default_cfg ( &barometer13 ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
log_printf( &logger, " ______________________ \r\n" );
}
void application_task ( void )
{
float pressure = 0, temperature = 0;
if ( ( BAROMETER13_OK == barometer13_get_measurement( &barometer13, &pressure, &temperature ) ) &&
barometer13_get_interrupt( &barometer13 ) )
{
log_printf( &logger, " Pressure : %.2f mBar \r\n", pressure );
log_printf( &logger, " Temperature : %.2f degC \r\n", temperature );
log_printf( &logger, " ______________________ \r\n" );
Delay_ms( 1000 );
}
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END