mikroe_accel8_mpu6050

MPU6050 - Accel 8 Click (Mikroe)

Summary

This project aims to show the hardware driver that is used to interface with the MPU6050 Sensor using Silicon Labs platform.

The MPU6050 is a very popular motion sensor IC, equipped with a 3-axis gyroscope and 3-axis accelerometer.

Table Of Contents

• Required Hardware
• Hardware Connection
• Setup
  • Create a project based on an example project
  • Start with an empty example project
• How It Works
• Report Bugs & Get Support

Required Hardware

• 1x Silicon Labs BLE Explorer Kit based on the EFR32 SoC, such as:

  • BGM220-EK4314A
  • BG22-EK4108A
  • xG24-EK2703A

  or

  1x Silicon Labs Wi-Fi Development Kit based on SiWG917, such as:

  • SiW917Y-EK2708A

• 1x Accel 8 Click board

Hardware Connection

The Silicon Labs Explorer Kit boards feature a mikroBUS™ socket, allowing the Accel 8 Click board to connect easily via the mikroBUS header. Ensure that the 45-degree corner of the Accel 8 Click board aligns with the 45-degree white line on the Explorer Kit. The hardware connection is illustrated in the image below.

For the Silicon Labs boards that do not have a mikroBUS™ socket, consider using the Wire Jumpers.

Setup

You can either create a project based on an example project or start with an empty example project.

Important

• Make sure that the Third Party Hardware Drivers extension is installed as part of the SiSDK. If not, follow this documentation.
• Third Party Hardware Drivers extension must be enabled for the project to install the required components from this extension.

Tip

To show all components in the Third Party Hardware Drivers extension, the Evaluation quality must be enabled in the Software Component view.

Create a project based on an example project

1. From the Launcher Home, add your board to My Products, click on it, and click on the EXAMPLE PROJECTS & DEMOS tab. Find the example project filtering by "mpu6050".

2. Click Create button on the project: Example project creation dialog pops up -> click Create and Finish and Project should be generated.

3. Build and flash this example to the board.

Start with an empty example project

1. Create an "Empty C Project" for your board using Simplicity Studio v5. Use the default project settings.

2. Copy the file app/example/mikroe_accel8_mpu6050/app.c into the project root folder (overwriting the existing file).

3. Open the .slcp file. Select the SOFTWARE COMPONENTS tab and install the following components:

   • If the BLE Explorer Kit is used:

     • [Services] → [IO Stream] → [IO Stream: EUSART] → default instance name: vcom
     • [Application] → [Utility] → [Log]
     • [Third Party Hardware Drivers] → [Sensors] → [MPU6050 - Accel 8 Click (Mikroe)] → use default configuration

   • If the Wi-Fi Development Kit is used:

     • [WiSeConnect 3 SDK] → [Device] → [Si91x] → [MCU] → [Peripheral] → [I2C] → [i2c2] → [i2c2]
     • [Third Party Hardware Drivers] → [Sensors] → [MPU6050 - Accel 8 Click (Mikroe)] → use default configuration

4. Enable Printf float

   • Open Properties of the project.
   • Select C/C++ Build → Settings → Tool Settings → GNU ARM C Linker → General → Check Printf float.

5. Build and flash this example to the board.

How It Works

The application reads Accel X/Y/Z axis, Gyro X/Y/Z axis and device Temperature. You can launch Console that's integrated into Simplicity Studio or use a third-party terminal tool like Tera Term to receive the data from the USB. A screenshot of the console output is shown in the figure below.

Report Bugs & Get Support

To report bugs in the Application Examples projects, please create a new "Issue" in the "Issues" section of third_party_hw_drivers_extension repo. Please reference the board, project, and source files associated with the bug, and reference line numbers. If you are proposing a fix, also include information on the proposed fix. Since these examples are provided as-is, there is no guarantee that these examples will be updated to fix these issues.

Questions and comments related to these examples should be made by creating a new "Issue" in the "Issues" section of third_party_hw_drivers_extension repo.