Matekf722-wing Dfu loop

[ChunkyzSoup]

Current Behavior

when i have my flywoo bt-nano v2 connected on uart 1 ( haven't tested any other uarts yet) and I power it up via USB and load inav (current version) everything seems to work. I can then disconnect (click disconnect on inav while leaving it plugged in.) I then open speedybee app and bluetooth connects and works fine. I can plug the battery up and it will still work fine. But once I kill power to it all together. And hook only my battery to my fc, it doesn't work, bluetooth doesn't connect to speedybee, inav wont connect to com6 (my fc) and it redirects me (sometimes) to a dfu, other times I have to push the boot button to get to dfu mode. To once again install the firmware and try again, repeatedly. I have a matek sam-m8q gps Mag on uart 3 when I have to disconnect to enter dfu mode (but then it sometimes auto recognized dfu mode after failing to connect to com6) I say that because on the matek website they say if gps or other type of module is connected to uarts then.. well -see attached. But sometimes it did enter dfu mode while attached and powered on. The other attached picture is exactly as I have mine setup, exactly. Well, Minus the airflow sensors and oled screen. I set the bluetooth baut to 115200. Because the screenshoted 56700 value didn't work. And I don't have soft serial enabled with smartport since I'm using fport on tx2 and there's no point in making tx 2 a soft serialport (Right??? Serious question)

All this kept happening.

Flash firmware
Setup everything
Click disconnect button on inav keeping power the to fc.
Bluetooth connect to speedybee perfectly.
Kill power to fc totally and then plug in battery.
Bluetooth doesn't connect to speedybee
Inav doesn't connect to fc. -sometimes- auto identifying after a failed com connect as dfu mode

I got tired of it and snipped the positive and negative to my bluetooth module. Plugged it in. And it recognizes the fc again. Its all confusing. But it has something to do with the bluetooth, perhaps being connected to one of the uarts listed in the screenshot I posted is having some adverse reaction. They say uart 1 and 3 have power when the fc is plugged in it cant enter dfumode. Which is partially true. I have to disconnect my gps if I want to enter dfu mode, but I never had to disconnect the bluetooth module to inter dfu mode. I actually have to disconnect the module to stop me from always entering dfu mode, but ONLY when I plugged my battery in.

Not sure what else I can say..

Steps to Reproduce

1.Flash firmware
2.Setup everything
3.Click disconnect button on inav keeping power the to fc.
4.Bluetooth connect to speedybee perfectly.
5.Kill power to fc totally and then plug in battery.
6.Bluetooth doesn't connect to speedybee
7.Inav doesn't connect to fc. -sometimes- auto identifying after a failed com connect as dfu mode
8. Disconnect flywoo, dfu loop ends.

Expected behavior

Suggested solution(s)

Additional context

---

• FC Board name and vendor:
• INAV version string:# version

INAV/MATEKF722SE 2.5.2 Aug 4 2020 / 10:22:04 (faaedc7)

GCC-9.2.1 20191025 (release) [ARM/arm-9-branch revision 277599]

[issue-label-bot[bot]]

Issue-Label Bot is automatically applying the label BUG to this issue, with a confidence of 0.81. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

[ChunkyzSoup]

#4205 (comment) this seems kind of connected to my problem. If this problem is connected to my problem, what on earth can I connect to uart 1 what won't interfere with the fc booting up? In the matek f722 wing diagram it shows to connect bluetooth to uart 1 🤦‍♂️

[ChunkyzSoup]

I disconnected my vtx from uart 4 and plugged my bluetooth module onto uart 4. Same problem. While powered with USB, bluetooth will connect and enter configurator. Disconnect power, plug up battery. Same problem persists. Bluetooth will connect to phone but times out I suppose, on "initializing" same as always. Any suggestions?