Get in motion with MPU-6000 and MK64FN1M0VDC12
Detect, track, and conquer movement with precision
Published Jun 19, 2023
Click board™
MPU IMU Click
Dev. board
Clicker 2 for Kinetis
Compiler
NECTO Studio
MCU
MK64FN1M0VDC12
Achieve detection and measurement of both rotational movements and linear acceleration in three dimensions
A
A
Hardware Overview
How does it work?
MPU IMU Click is based on the MPU-6000, an integrated 6-axis motion device that combines a 3-axis gyroscope and accelerometer and a DMP (digital motion processor) from TDK InvenSense. The onboard gyroscope has a high sensitivity with a user-programmable full-scale range of ±250, ±500, ±1000, and ±2000dps, while the accelerometer has a full-scale programmable range of ±2g, ±4g, ±8g, and ±16g. This integrated circuit has high vibration tolerance, where its digital output of 6 or 9-axis MotionFusion data consists of a rotation matrix, quaternion, Euler angle, or row data format. The DMP engine offloads complex MotionFusion, sensor timing synchronization, and gesture detection. The MPU-6000 has an integrated digital output temperature sensor and
embedded algorithms for run-time bias and compass calibration, with no user intervention required. An on-chip 1024 Byte FIFO buffer allows the system to read data in burst and enter a low-power mode, lowering system power consumption. MPU IMU Click allows using both I2C and SPI interfaces with a maximum frequency of 400kHz for I2C and 1MHz for SPI communication (20MHz for reading sensor and interrupt registers). The selection can be made by positioning SMD jumpers marked as SPI/I2C to an appropriate position. Note that all the jumpers' positions must be on the same side, or the Click board™ may become unresponsive. While the I2C interface is selected, the MPU-6000 allows choosing its I2C slave address using the I2C ADD SMD jumper to an
appropriate position marked as 0 and 1. This Click board™ also supports electronic video stabilization and GPS synchronization over a digital FSY pin. Programmable interrupt over an INT pin supports gesture recognition, panning, zooming, scrolling, free fall interrupt, high-G interrupt, zero-motion detection, and more. A pedometer functionality is also implemented, allowing the target board's MCU to sleep while DMP maintains the step count. This Click board™ can only be operated with a 3.3V logic voltage level. The board must perform appropriate logic voltage level conversion before using MCUs with different logic levels. However, the Click board™ 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
Start by selecting your development board and Click board™. Begin with the Clicker 2 for Kinetis 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 MPU IMU Click driver.
Key functions:
mpuimu_read_accel- This function read Accel X-axis, Y-axis and Z-axismpuimu_read_gyro- This function read Gyro X-axis, Y-axis and Z-axismpuimu_read_temperature- This function reads temperature data
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 MpuImu Click example
*
* # Description
* MPU IMU Click carries the integrated 6-axis motion tracking device
* that combines 3-axis gyroscope and accelerometer.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Application Init performs Logger and Click initialization.
*
* ## Application Task
* Measured Accel and Gyro coordinates (X,Y,Z) and Temperature in degrees C
* are being sent to the UART where you can track their changes.
* All data logs on USB UART for every 1 sec.
*
* \author Mihajlo Djordjevic
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "mpuimu.h"
float temperature;
// ------------------------------------------------------------------ VARIABLES
static mpuimu_t mpuimu;
static log_t logger;
mpuimu_accel_data_t accel_data;
mpuimu_gyro_data_t gyro_data;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
mpuimu_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 ----" );
Delay_ms ( 100 );
// Click initialization.
mpuimu_cfg_setup( &cfg );
MPUIMU_MAP_MIKROBUS( cfg, MIKROBUS_1 );
mpuimu_init( &mpuimu, &cfg );
log_printf( &logger, "--------------------------\r\n" );
log_printf( &logger, " ---- MPU IMU Click ----\r\n" );
log_printf( &logger, "--------------------------\r\n" );
Delay_ms ( 1000 );
mpuimu_default_cfg ( &mpuimu );
Delay_ms ( 1000 );
log_printf( &logger, " ---- Initialization ---\r\n" );
log_printf( &logger, "--------------------------\r\n" );
Delay_ms ( 1000 );
}
void application_task ( void )
{
mpuimu_read_accel( &mpuimu, &accel_data );
Delay_ms ( 100 );
mpuimu_read_gyro( &mpuimu, &gyro_data );
Delay_ms ( 100 );
temperature = mpuimu_read_temperature( &mpuimu );
Delay_ms ( 100 );
log_printf( &logger, " Accel | Gyro \r\n" );
log_printf( &logger, "--------------------------\r\n" );
log_printf( &logger, " X = %d | X = %d \r\n", accel_data.accel_x, gyro_data.gyro_x );
log_printf( &logger, " Y = %d | Y = %d \r\n", accel_data.accel_y, gyro_data.gyro_y );
log_printf( &logger, " Z = %d | Z = %d \r\n", accel_data.accel_z, gyro_data.gyro_z );
log_printf( &logger, "--------------------------\r\n" );
log_printf( &logger, " TEMP = %0.2f C\r\n", temperature );
log_printf( &logger, "--------------------------\r\n" );
software_reset ( &mpuimu );
Delay_ms ( 1000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
