FC: Mamba F722 MK3 
GPS/Compass:Iflight M8Q/QMC5883L 
Firmware: 7.0.0 MAMBA 722 I2C 
I2C errors:60
Hello FPV community, my magnetometer is red. The GPS is connected to the flight controller through a VIFLY GPS MATE to UART4 and everything is perfect. The problem is the magnetrometer that I can't make it turn blue, the connections (soldering) are not the best but enough to do the job, I already checked it with a multimeter and there is no contact between the SLC and SDA pins, also check that there is complete continuity from the GPS connector on the SLC and SDA pins (jst 6 male) to the respective pins on the flight controller and that is fine. Then the manufacturer recommends using these commands for Betaflight for the magnetometer set mag_i2c_device=1, set mag_bustype=i2c The first command assigns device 1 (I2C) for the magnetometer and the second command uses the I2C bus type, I already checked the target.h of this board in INAV and all that is already done, that is, there would be no need to use the commands. The curious thing is that the barometers included in most FCs share the same "1" I2C device with the magnetometer and of course this FC too. Check the target.h INAV of some MATEK and IFLIGHT boards and they also share the same I2C device . I don't understand why they don't use device "2". In this context device "1" is I2C1_SCL PB8 and I2C1_SDA PB9 The story of this FC and many MAMBA FCs is that they have software problems with INAV for the baro and magnotetometer. There is a discussion on github INAV from 2021 about this same problem on this same board and a guy from reddit from December 2023 baro and magnetrometers not detected same FC.
After finishing flash firmware (no lipo, only usb FC) the barometer is not detected but when you turn on the VIFLY (power supply only for the GPS) and choose the corresponding baro and magnometomer; The baro is detected, I suppose it is because they share the same pins with the magnometer since the vifly supplies power, why these MAMBA boards need a LIPO supply to power the baro, I will never buy another MAMBA board again if I ever fly to build a drone xd I haven't tried swapping the SDA and SLC pins yet since I read elsewhere that the Diatone manufacturer sometimes makes mistakes in their pinout.

# status
INAV/MAMBAF722_I2C 7.0.0 Dec  5 2023 / 10:21:16 (895a4f31)
GCC-10.3.1 20210824 (release)
System Uptime: 59 seconds
Current Time: 2041-06-28T01:04:00.000+00:00
Voltage: 0.00V (0S battery - NOT PRESENT)
CPU Clock=216MHz, GYRO=MPU6000, ACC=MPU6000, BARO=BMP280
STM32 system clocks:
  SYSCLK = 216 MHz
  HCLK   = 216 MHz
  PCLK1  = 54 MHz
  PCLK2  = 108 MHz
Sensor status: GYRO=OK, ACC=OK, MAG=UNAVAILABLE, BARO=OK, RANGEFINDER=NONE, OPFLOW=NONE, GPS=OK
ESC Temperature(s): Motor Count = 4
ESC 0: 0°C, ESC 1: 0°C, ESC 2: 0°C, ESC 3: 0°C,
Stack size: 6144, Stack address: 0x20010000, Heap available: 1820
I2C Errors: 60, config size: 9273, max available config: 16384
ADC channel usage:
   BATTERY : configured = ADC 1, used = none
      RSSI : configured = ADC 2, used = none
   CURRENT : configured = ADC 3, used = none
  AIRSPEED : configured = none, used = none
System load: 19, cycle time: 521, PID rate: 1919, RX rate: 9, System rate: 9
Arming disabled flags: HWFAIL RX CLI DSHOTBEEPER
OSD: MAX7456 [30 x 16]
VTX: not detected
GPS: HW Version: UBLOX8 Proto: 18.00 Baud: 115200
  GNSS Capabilities:
    GNSS Provider active/default
    GPS 1/1
    Galileo 0/0
    BeiDou 0/0
    Glonass 0/1
    Max concurrent: 3