10 min

Improve user experiences and simplify interactions with ADXL362 and STM32F423RH

Tap to transform: The magic of movement-activated solutions

Shake2Wake Click with UNI-DS v8

Published Oct 05, 2023

Click board™

Shake2Wake Click

Development board



NECTO Studio



This solution opens the door to a new era of automation and accessibility, enabling devices and systems to respond seamlessly to human movement



Hardware Overview

How does it work?

Shake2Wake Click is based on the ADXL362, a digital output 3-axis MEMS accelerometer, and the ADP195, a logic-controlled high-side power switch with reverse current blocking, both from Analog Devices. The ultralow-power ADXL362 features an on-chip temperature sensor, a high resolution of 1mg/LSB detection with ranges of ±2 g, ±4 g, and ±8, low noise, and acceleration sample synchronization via an external trigger. The ADXL362 comes with various features for system-level power savings, such as adjustable thresholds for motion activation, autonomous interrupt processing without the need for the host MCU intervention that allows the rest of the system to be turned off completely, deep embedded

FIFO, and more. The ADXL362 also provides a 12-bit output resolution and 8-bit data for more efficient single-byte transfers when a lower resolution is sufficient. This Click board™ has two main operating modes: measuring and wake-up. For use as a regular accelerometer, for continuous sensing, use the measurement mode. The ADP195 on this Click board™ is an onboard power switch that controls an external device connected through a screw terminal. The load switch isolates the power domain and protects against the reverse current flow from output to input. The ADXL362 uses an SPI serial interface to communicate with the host microcontroller. Several of the built-in functions of the ADXL362

can trigger interrupts to alert the host MCU of certain status conditions. The ADXL362 can use INT1 or INT2 selected over the INT SEL jumper to meet the mapped condition expected to be activated, with INT2 chosen by default. The ADXL362's interrupt is also connected to the host MCU over the INT pin, enabling the ADP195 when movement occurs. 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.

Shake2Wake Click hardware overview image

Features overview

Development board

UNI-DS v8 is a development board specially designed for the needs of rapid development of embedded applications. It supports a wide range of microcontrollers, such as different STM32, Kinetis, TIVA, CEC, MSP, PIC, dsPIC, PIC32, and AVR MCUs regardless of their number of pins, and a broad set of unique functions, such as the first-ever embedded debugger/programmer over WiFi. The development board is well organized and designed so that the end-user has all the necessary elements, such as switches, buttons, indicators, connectors, and others, in one place. Thanks to innovative manufacturing technology, UNI-DS v8 provides a fluid and immersive working experience, allowing access anywhere and under any

circumstances at any time. Each part of the UNI-DS v8 development board contains the components necessary for the most efficient operation of the same board. An advanced integrated CODEGRIP programmer/debugger module offers many valuable programming/debugging options, including support for JTAG, SWD, and SWO Trace (Single Wire Output)), and seamless integration with the Mikroe software environment. Besides, it also includes a clean and regulated power supply module for the development board. It can use a wide range of external power sources, including a battery, an external 12V power supply, and a power source via the USB Type-C (USB-C) connector. Communication options such as USB-UART, USB

HOST/DEVICE, CAN (on the MCU card, if supported), and Ethernet is also included. In addition, it also has the well-established mikroBUS™ standard, a standardized socket for the MCU card (SiBRAIN standard), and two display options for the TFT board line of products and character-based LCD. UNI-DS v8 is an integral part of the Mikroe ecosystem for rapid development. Natively supported by Mikroe software tools, it covers many aspects of prototyping and development thanks to a considerable number of different Click boards™ (over a thousand boards), the number of which is growing every day.

UNI-DS v8 horizontal image

Microcontroller Overview

MCU Card / MCU



8th Generation


ARM Cortex-M4

MCU Memory (KB)


Silicon Vendor


Pin count


RAM (Bytes)


Used MCU Pins

mikroBUS™ mapper

SPI Chip Select
SPI Clock
Power Supply
Power Switch Enable

Take a closer look


Shake2Wake Click Schematic schematic

Step by step

Project assembly

Fusion for PIC v8 front image hardware assembly

Start by selecting your development board and Click board™. Begin with the UNI-DS v8 as your development board.

Fusion for PIC v8 front image hardware assembly
Buck 22 Click front image hardware assembly
SiBRAIN for PIC32MZ1024EFK144 front image hardware assembly
v8 SiBRAIN MB 1 - upright/background hardware assembly
Necto image step 2 hardware assembly
Necto image step 3 hardware assembly
Necto image step 4 hardware assembly
NECTO Compiler Selection Step Image hardware assembly
NECTO Output Selection Step Image hardware assembly
Necto image step 6 hardware assembly
Necto image step 7 hardware assembly
Necto image step 8 hardware assembly
Necto image step 9 hardware assembly
Necto image step 10 hardware assembly
Necto PreFlash Image hardware assembly

Track your results in real time

Application Output

After pressing the "FLASH" button on the left-side panel, it is necessary to open the UART terminal to display the achieved results. By clicking on the Tools icon in the right-hand panel, multiple different functions are displayed, among which is the UART Terminal. Click on the offered "UART Terminal" icon.

UART Application Output Step 1

Once the UART terminal is opened, the window takes on a new form. At the top of the tab are two buttons, one for adjusting the parameters of the UART terminal and the other for connecting the UART terminal. The tab's lower part is reserved for displaying the achieved results. Before connecting, the terminal has a Disconnected status, indicating that the terminal is not yet active. Before connecting, it is necessary to check the set parameters of the UART terminal. Click on the "OPTIONS" button.

UART Application Output Step 2

In the newly opened UART Terminal Options field, we check if the terminal settings are correct, such as the set port and the Baud rate of UART communication. If the data is not displayed properly, it is possible that the Baud rate value is not set correctly and needs to be adjusted to 115200. If all the parameters are set correctly, click on "CONFIGURE".

UART Application Output Step 3

The next step is to click on the "CONNECT" button, after which the terminal status changes from Disconnected to Connected in green, and the data is displayed in the Received data field.

UART Application Output Step 4

Software Support

Library Description

This library contains API for Shake2Wake Click driver.

Key functions:

  • shake2wake_get_lo_res_raw_data - This function is used to read 8-bit acceleration data per axis

  • shake2wake_get_raw_data - This function is used to read the 3-axis raw data from the accelerometer

  • shake2wake_read_temperature - This function is used to read temperature from an internal sensor

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 Shake2Wake Click example
 * # Description
 * This app shows the capabilities of the Shake2Wake click by
 * reading values of an accelerometer.
 * The demo application is composed of two sections :
 * ## Application Init 
 * Initalizes device and applies default settings.
 * ## Application Task  
 * This is an example that shows the capabilities of the Shake2Wake click by
 * reading values of an accelerometer and logging them on USART terminal and, in case of an interrupt, it
 * raises voltage on the connector.
 * \author MikroE Team
// ------------------------------------------------------------------- INCLUDES

#include "board.h"
#include "log.h"
#include "shake2wake.h"

// ------------------------------------------------------------------ VARIABLES

static shake2wake_t shake2wake;
static log_t logger;

// ------------------------------------------------------ APPLICATION FUNCTIONS

void application_init ( void )
    log_cfg_t log_cfg;
    shake2wake_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.

    shake2wake_cfg_setup( &cfg );
    shake2wake_init( &shake2wake, &cfg );

    Delay_ms( 100 );
    log_printf( &logger, "--------------------------\r\n" );
    log_printf( &logger, "    Shake2Wake  Click     \r\n" );
    log_printf( &logger, "--------------------------\r\n" );

    shake2wake_default_cfg( &shake2wake );

void application_task ( void )
    float temperature;
    int16_t x_val;
    int16_t y_val;
    int16_t z_val;

    shake2wake_get_raw_data( &shake2wake, &x_val, &y_val, &z_val );
    temperature = shake2wake_read_temperature( &shake2wake );

    log_printf( &logger, "X axis: %d\r\n", x_val );
    log_printf( &logger, "Y axis: %d\r\n", y_val );
    log_printf( &logger, "Z axis: %d\r\n", z_val );
    log_printf( &logger, "Temperature: %f \r\n", temperature );
    log_printf( &logger, "--------------------------\r\n" );
    Delay_ms( 1000 );

void main ( void )
    application_init( );

    for ( ; ; )
        application_task( );

// ------------------------------------------------------------------------ END

Additional Support