Skip to content

Latest commit

 

History

History

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 

README.md

RGB Driver Click (Mikroe)

Type badge Type badge Type badge Type badge Type badge

Summary

This project shows the driver implementation of a RGB Driver with the Silicon Labs Platform.

RGB Driver click is an RGB LED driver, capable of driving RGB LED stripes, LED fixtures and other RGB LED applications that demand an increased amount of current and voltage.

Table Of Contents

Required Hardware

Hardware Connection

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

board

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

The tables below provide an overview of the pin connections.

Silicon Labs BLE Development Kit:

Description BRD4314A BRD4108A BRD2703A BRD2710A RGB Driver Click
I2C_SDA PD3 PD3 PB5 PD3 SDA
I2C_SCL PD2 PD2 PB4 PD2 SCL

Silicon Labs Wi-Fi Development Kit:

Description BRD4338A + BRD4002A BRD2605A BRD2708A RGB Driver Click
I2C_SDA ULP_GPIO_6 [EXP_16] ULP_GPIO_6 [P16] GPIO_6 SDA
I2C_SCL ULP_GPIO_7 [EXP_15] ULP_GPIO_7 [P15] GPIO_7 SCL

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 with filtering by rgb.

  2. Click Create button on the Third Party Hardware Drivers - RGB Driver Click (Mikroe) example. Example project creation dialog pops up -> click Create and Finish and Project should be generated. Create_example

  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_rgb_driver/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 EFR32xG24 Explorer Kit is used:

      • [Application] → [Utility] → [Log]
      • [Services] → [Timers] → [Sleep Timer]
      • [Services] → [IO Stream] → [IO Stream: USART] → default instance name: vcom
      • [Platform] → [Driver] → [I2C] → [I2CSPM] → instance name: mikroe
      • [Third Party Hardware Drivers] → [Miscellaneous] → [RGB Click (Mikroe)]
    • If the Wi-Fi Development Kit is used:

      • [WiSeConnect 3 SDK] → [Device] → [Si91x] → [MCU] → [Service] → [Sleep Timer for Si91x]
      • [WiSeConnect 3 SDK] → [Device] → [Si91x] → [MCU] → [Peripheral] → [I2C] → [i2c2] → Select the corresponding pins according to the table provided in Hardware Connection
      • [Third Party Hardware Drivers] → [Miscellaneous] → [RGB Click (Mikroe)]
  4. Build and flash this example to the board.

How It Works

After you flashed the code to your board and powered the connected boards, the application starts running automatically. The application changes the color of RGB LED tape connected to the click board every 2 seconds.

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.