DPS310 barometer not detected on GEPRC GEP-M10-DQ with TUNERC Poly F405 using INAV 8.0.0

[kazumayokota]

---

💡 Issue Summary

Using the GEPRC GEP-M10-DQ GPS module (QMC5883 + DPS310) with INAV 8.0.0 on a TUNERC Poly F405 AIO board.
The QMC5883 magnetometer is correctly detected, but the DPS310 barometer is not, even though baro_hardware = DPS310 and USE_BARO_DPS310 is defined in the target.

No I2C errors are present, and the barometer task does not appear in tasks, indicating the sensor was never initialized.

---

📦 My Build

Component	Description
Frame	GEPRC GEP-TC18
FC	TUNERC Poly F405 2S-4S 20A AIO V1.2
RX	BETAFPV ELRS Lite V1.1
Motors	Happymodel EX1102 9000KV (×4)
Props	Gemfan 45mm 3-Blade (×4)
Battery	GNB 550mAh 7.6V 2S 100C HV
VTX	Walksnail Avatar HD Mini 1s Kit
GPS	GEPRC GEP-M10-DQ (QMC5883 + DPS310)
Optical Flow & Range	Micoair MTF-02P
Other	Flywoo 1.3g Universal Prop Guard, BETAFPV Pavo Strap

---

🔍 What I've tried

• baro_hardware = DPS310 confirmed in CLI

• USE_BARO_DPS310 already defined in target.h

• No I2C errors in status

• GPS & MAG (QMC5883) working fine on same I2C bus (PB10 = SCL, PB11 = SDA)

• Power cycling FC and GPS in different orders

• Clean install of INAV 8.0.0 official firmware

• No baro task appears in tasks output

---

📸 Screenshot / Logs

# status
INAV/TUNERCF405 8.0.0 Jan 21 2025 / 16:17:36 (ec2106af) 
GCC-13.2.1 20231009
System Uptime: 20 seconds
Voltage: 7.45V (2S battery - OK)
Sensor status: GYRO=OK, ACC=OK, MAG=OK, BARO=UNAVAILABLE, RANGEFINDER=OK, OPFLOW=OK, GPS=OK
I2C Errors: 0
tasks
Task list         rate/hz  max/us  avg/us maxload avgload     total/ms

...

9 -      COMPASS       9     176     170    0.6%    0.6%        28

(No barometer task running)

# tasks

Task list         rate/hz  max/us  avg/us maxload avgload     total/ms

...

9 -      COMPASS       9     176     170    0.6%    0.6%        28

(No barometer task running)

---

❓ Question

• Could this be an issue with how INAV initializes DPS310 on this specific board?

• Is there a known timing or address detection issue with DPS310?

• Any plan to improve DPS310 detection robustness?

---

Thank you so much for this amazing flight system and for your continued development! 🚀
Happy to test any suggestions you may have.

[kazumayokota]

I'd like to update a previous discussion and let you know that the issue has been resolved on my end.

I received a report from the manufacturer regarding the investigation results, and I’d like to share it here.

The cause of the issue was a mismatch between the INAV settings and the GEPRC GPS module (M10-DQ) concerning the I2C address of the DPS310 barometer.

Specifically:

INAV’s default I2C address for the DPS310 is 0x76

The DPS310 on the GEPRC M10-DQ module uses the default address 0x77

Due to this mismatch, the sensor was not being recognized properly.
To resolve this, it is necessary to recompile the INAV firmware with the DPS310 address changed to 0x77.