This project shows the implementation of a barometer-sensor driver using Pressure 3 Click (DPS310) from Mikroe integrated with the Silicon Labs platform.
-
BRD4314A-BGM220 BGM220 Bluetooth Module Explorer Kit (BRD4314A-BGM220 Explorer Kit Board)
-
Or SiWx917 Wi-Fi 6 and Bluetooth LE 8 MB Flash SoC Pro Kit (BRD4002 + BRD4338A)
-
If the BGM220P Explorer Kit is used:
The Pressure 3 Click board supports MikroBus, so it can connect easily to the Explorer Kit via MikroBus header. Assure that the 45-degree corner of Click board matches the 45-degree white line of the Explorer Kit.
The hardware connection is shown in the image below:
-
If the SiWx917 Wi-Fi 6 and Bluetooth LE 8 MB Flash SoC Pro Kit is used:
The hardware connection is shown in the table below:
-
If the I2C interface is used:
Description BRD4338A GPIO BRD4002 EXP Header Pressure 3 Click I2C_SDA ULP_GPIO_6 EXP_16 SDA I2C_SCL ULP_GPIO_7 EXP_15 SCL -
If the SPI interface is used:
Description BRD4338A GPIO BRD4002 Breakout Pad Pressure 3 click CS GPIO_46 P24 CS RTE_GSPI_MASTER_CLK_PIN GPIO_25 P25 SCK RTE_GSPI_MASTER_MISO_PIN GPIO_26 P27 SDO RTE_GSPI_MASTER_MOSI_PIN GPIO_27 P29 SDI
-
You can either create a project based on an example project or start with an empty example project.
-
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 'dps310'.
-
Click Create button on the example:
-
Third Party Hardware Drivers - DPS310 - Pressure 3 Click (Mikroe) - I2C if using the I2C interface.
-
Third Party Hardware Drivers - DPS310 - Pressure 3 Click (Mikroe) - SPI if using the SPI interface.
Example project creation dialog pops up -> click Create and Finish and Project should be generated.
-
-
Build and flash this example to the board.
-
Create an "Empty C Project" for your board using Simplicity Studio v5. Use the default project settings.
-
Copy the file
app/example/mikroe_pressure3_dps310/app.c
into the project root folder (overwriting the existing file). -
Install the software components:
-
Open the .slcp file in the project.
-
Select the SOFTWARE COMPONENTS tab.
-
Install the following components:
If the BGM220P Explorer Kit is used:
- [Services] → [Timers] → [Sleep Timer]
- [Services] → [IO Stream] → [IO Stream: EUSART] → default instance name: vcom
- [Application] → [Utility] → [Log]
- If the SPI interface is used:
- [Platform] → [Driver] → [SPI] → [SPIDRV] → [mikroe] → change the configuration for [SPI master chip select (CS) control scheme] to "CS controlled by the application", select the CS pin to None as below:
- [Third Party Hardware Drivers] → [Sensors] → [DPS310 - Pressure 3 Click (Mikroe) - SPI] → select the CS pin to PC03 as below:
- If the I2C interface is used:
- [Third Party Hardware Drivers] → [Sensors] → [DPS310 - Pressure 3 Click (Mikroe) - I2C]
If the SiWx917 Wi-Fi 6 and Bluetooth LE 8 MB Flash SoC Pro Kit is used:
- [WiSeConnect 3 SDK] → [Device] → [Si91x] → [MCU] → [Service] → [Sleep Timer for Si91x]
- If the SPI interface is used:
- [Third Party Hardware Drivers] → [Sensors] → [DPS310 - Pressure 3 Click (Mikroe) - SPI] → use default configuration
- If the I2C interface is used:
- [WiSeConnect 3 SDK] → [Device] → [Si91x] → [MCU] → [Peripheral] → [I2C] → [i2c2]
- [Third Party Hardware Drivers] → [Sensors] → [DPS310 - Pressure 3 Click (Mikroe) - I2C]
-
-
Install printf float
-
Build and flash this example to the board.
Note:
- Make sure that the Third Party Hardware Drivers extension is installed. If not, follow this documentation.
This is an example that demonstrates the use of the Pressure 3 Click board. Measured pressure and temperature data from the DPS310 sensor on the Pressure 3 Click board. Results are being sent to the USART Terminal where you can track their changes. You can launch Console that's integrated into Simplicity Studio or use a third-party terminal tool like TeraTerm to receive the data from the USB. A screenshot of the console output is shown as the figure below.
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.