Hello all. I would like to ask for a help. I have 5 inch Iflight Chimera quad, it worked with no issues on BF4.4. After flashing BF4.5 (FC detected, GPS included, full erase done, then manual setup of parameters in the Configurator) the quad cannot arm showing in OSD "RESCUE OFF" error message. 
Below are my observations:
1) Cannot arm with or without GPS fix (FC is allowed to arm without fix).
2) Cannot arm if Failsafe is in Rescue or Drop mode.

Rolling back to BBF4.4 quad is working as usual, but I wanted to have improvements of BF4.5, and just interesting to determine what is wrong.

What can I check to debug this issue? Thank you in advance.

What arming prevention flags are you getting in BFC or CLI? If you match it to the table below it provides the reason and action to resolve it.

https://betaflight.com/docs/wiki/guides/...And-Safety

(26-Jun-2024, 05:47 PM)mstc Wrote: What arming prevention flags are you getting in BFC or CLI? If you match it to the table below it provides the reason and action to resolve it.

https://betaflight.com/docs/wiki/guides/...And-Safety

Thank you, will check. Silly question. To see prevention flag in CLI I need to connect FC to computer. It prevents arming. Will status still indicate prevention flag which was in force when FC is disconnected from USB?

The prevention flag for uab connection, is "msp".
Msp can be ignored, it will display other arming flags too

You might need to flash 4.5 again to find the issue

Yes you will see MSP or CLI and will not be able to arm, but there should also be other warnings that would indicate why your drone is not arming when not connected to BF.

(26-Jun-2024, 11:16 PM)mstc Wrote: Yes you will see MSP or CLI and will not be able to arm, but there should also be other warnings that would indicate why your drone is not arming when not connected to BF.

Here is 'status' output with Arm switch off and on. I see there is I2C errors = 5.
Beeper does not indicate any arming prevention flags, after arming just 3 fast beeps.
Probably it is not arming prevention as in OSD it is showing ARMED, and then RESCUE OFF. It means that arm is tried w/o GPS fix.
So maybe something with motor controls which does not happen in BF4.4 with the same parameters.
I tried to engage motors from MOTORS tab but they do not spin. Tough case...

ARM SWITCH OFF:

# status
MCU F722 Clock=216MHz, Vref=3.27V, Core temp=51degC
Stack size: 2048, Stack address: 0x20010000
Configuration: CONFIGURED, size: 3826, max available: 16384
Devices detected: SPI:1, I2C:0
Gyros detected: gyro 1 locked dma
GYRO=MPU6000, ACC=MPU6000
OSD: MSP (30 x 13)
BUILD KEY: 429d1c68de46aa8b8bbf172f3e03439b (4.5.0)
System Uptime: 24 seconds, Current Time: 2024-06-26T23:37:23.516+00:00
CPU:36%, cycle time: 125, GYRO rate: 8000, RX rate: 150, System rate: 9
Voltage: 1516 * 0.01V (4S battery - OK)
I2C Errors: 5
FLASH: JEDEC ID=0x00ef4018 16M
GPS: connected, UART4 57600 (set to 57600), configured, version =  M8
Arming disable flags: CLI MSP

ARM SWITCH ON:

# status
MCU F722 Clock=216MHz, Vref=3.27V, Core temp=52degC
Stack size: 2048, Stack address: 0x20010000
Configuration: CONFIGURED, size: 3826, max available: 16384
Devices detected: SPI:1, I2C:0
Gyros detected: gyro 1 locked dma
GYRO=MPU6000, ACC=MPU6000
OSD: MSP (30 x 13)
BUILD KEY: 429d1c68de46aa8b8bbf172f3e03439b (4.5.0)
System Uptime: 33 seconds, Current Time: 2024-06-26T23:37:33.282+00:00
CPU:35%, cycle time: 125, GYRO rate: 8000, RX rate: 149, System rate: 9
Voltage: 1517 * 0.01V (4S battery - OK)
I2C Errors: 5
FLASH: JEDEC ID=0x00ef4018 16M
GPS: connected, UART4 57600 (set to 57600), configured, version =  M8
Arming disable flags: CLI MSP ARMSWITCH

#

(26-Jun-2024, 11:12 PM)hugnosed_bat Wrote: The prevention flag for uab connection, is "msp".
Msp can be ignored, it will display other arming flags too

You might need to flash 4.5 again to find the issue

Thank you. Flashed twice already with rollback to 4.4 in between...All the same

Was looking for motors issues in BF4.5 and found the solution at https://github.com/betaflight/betaflight/issues/13598  
Need to use set dshot_bitbang = OFF with dshot_bidir disabled (my case).
Now motors are spinning but not sure what I am losing with dshot bit bang = OFF.

Does anyone know why BF4.5 requires to do so for F7 CPU? And can drone fly with this setting?

It sounds like you "fixed" a board design or target issue. Shouldnt be like that.
Is it maybe a speedybee v3?

(27-Jun-2024, 02:05 PM)hugnosed_bat Wrote: It sounds like you "fixed" a board design or target issue. Shouldnt be like that.
Is it maybe a speedybee v3?

It is Iflight SucceX-E mini F7 Stack