Gyro not detected on TMOTORF4 when using 10.9.0 configurator

[hectormfl]

Describe the bug

Hi,
During the migration to Betaflight 4.4 of my quads, detected an extrange issue on one of them.
The board is a TMOTORF4.
Using the latest configurator and installing the 4.4 version, when the process finishes and connects to the configurator, the Gyro is not detected.
Tried to reinstall the 4.3.2 version and works fine.

The thing is that if i use the 10.8.0 configurator, I can flash either 4.3.2 or 4.4 and gyro is detected fine. But I have doubts because its supposed that the version 4.4 should only be installed with de 10.9.0 configurator

On the pictures attached can be seen the gyro not detected on 4.4 flashed with 10.9.0 and gyro working after flashing 4.4 with 10.8.0 configurator

To Reproduce

installed 4.4 version with 10.9.0 configurator

Expected behavior

Gyro not detected

Configurator version

10.9.0

Flight controller configuration

# version
# Betaflight / STM32F405 (S405) 4.4.0 Feb  9 2023 / 20:26:02 (4605309d8) MSP API: 1.45

# config: YES

# start the command batch
batch start

board_name TMOTORF4
manufacturer_id TMTR

# master
set osd_canvas_width = 30
set osd_canvas_height = 13

profile 0

rateprofile 0

# end the command batch
batch end

Add any other context about the problem that you think might be relevant here

No response

[haslinghuis]

Fixed in: betaflight/betaflight#12371

You can test this PR in expert mode. Add #12371 in the commit field before flashing.

[hectormfl]

@haslinghuis

Installed the version with the #12371 commit, but same behaviour

Also tried with the betaflight_4.5.0_STM32F405_81c53e2.hex file of the Assets on the PR, same thing.

on the 4.5 pre-release tried with the commit, same result

[klutvott123]

that's strange. are we sure they aren't using other gyros than the mpu6000 on this board? Can you flash 4.3.2 and post the output of status in cli?

[klutvott123]

Looks like there's a regular and a HD version of this flight controller. Regular version uses ICM20602 while the HD version uses MPU6000.
Try adding GYRO_SPI_ICM20602 and ACC_SPI_ICM20602 to custom defines.
I think maybe the HD version should have had it's own config

[hectormfl]

that's strange. are we sure they aren't using other gyros than the mpu6000 on this board? Can you flash 4.3.2 and post the output of status in cli?

MCU F40X Clock=168MHz (PLLP-HSE), Vref=3.31V, Core temp=26degC
Stack size: 2048, Stack address: 0x1000fff0
Configuration: CONFIGURED, size: 4100, max available: 16384
Devices detected: SPI:1, I2C:0
Gyros detected: gyro 1 locked dma
GYRO=ICM20602, ACC=ICM20602
OSD: MAX7456
System Uptime: 29 seconds, Current Time: 2023-02-17T08:05:06.276+00:00
CPU:33%, cycle time: 125, GYRO rate: 8000, RX rate: 15, System rate: 9
Voltage: 1 * 0.01V (0S battery - NOT PRESENT)
I2C Errors: 0
SD card: Not configured
Arming disable flags: RXLOSS CLI MSP MOTOR_PROTO

[hectormfl]

ACC_SPI_ICM20602

Did it this way

It seems it works! now it´s detected.

As you said, yes, should be two different targets... this is the F4 not the F4HD
Hope can try it soon.

Thanks!

[klutvott123]

Thanks! That confirms it. betaflight/unified-targets#903 will fix it

[haslinghuis]

Fixed in betaflight/unified-targets#903