I2C Barometer Conflict on Mamba F722 with GEPRC M1025-DQ GPS Module

[SergeiLovjagin]

Current Behavior

I am using a Mamba F722 flight controller with the GEPRC M1025-DQ GPS module. The GPS and magnetometer work fine, but there is an issue with barometer detection.

• When the GPS module is disconnected, the FC detects the onboard BPM280 barometer correctly.

• When the GPS module is connected, the FC does not detect the DPS310 barometer inside the M1025-DQ module. Additionally, it no longer detects the BPM280 either.

Expected behavior

• The FC should detect either the DPS310 in the GPS module or at least continue detecting the BPM280.

Suggested solution(s)

• Could this be an I2C address conflict?

• Is there a way to manually select which barometer to use?

• Any known workarounds?

Additional context

• FC Board name and vendor: Mamba F722
• INAV version string: 8.0.0
• GPS Module: GEPRC M1025-DQ
• Barometers: BPM280 (FC), DPS310 (GPS module)

[mmosca]

The solution is to disable the baro on the gps unit, or use a gps unit with no baro, or a baro that does not conflict with your FC baro.

What you are witnessing is a bus conflict on the I2C bus, where you have 2 devices on the same address and talking over each other.

Both the BMP280 and DPS310 share the same I2C address (0x76)

[mmosca]

Here is a suggestion on how to solve the conflict:
#9783 (comment)