New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
clracingf4 goes into DFU mode when setting set_displayport_msp_serial #11496
Comments
Question: did you check this strange behavior without connecting HDZero vTX, ESC, ExpressLRS? If not, to avoid any circumstances around an issue with vTX, or ExpressLRS or ESC please remove this external devices.
I know - lot of work - but such kind of problems are hard to identify and a good approach is to start step by step. Possible for you? If you have results from above tests, please inform us. Thanks |
I have a similar issue. Only goes into DFU when you hook up via USB? If you power via battery first it boots fine and USB communication works as expected? Different board but same VTX. If so I'm going to dig into it some tomorrow and glad I'm not the only one. |
Any updates? Please check RC6 |
Sorry, been too busy building, flying and running races now that GQ season is underway. When I get a chance I'll try RC6 |
Please try |
My Mamba mk4 H743 doesn't forget config, but goes to DFU by itself repeatedly. - BF 4.2.11 |
Closing as duplicate of #11516 as that issue seems more active. |
Hmm,Not sure when I could get to this. Camping all weekend and I hope to get some flying in next week. I also see someone else has the problem, maybe they can make more progress. I'll let you know if I do get to it.Kevc
On Thursday, March 31, 2022, 07:08:34 AM EDT, Bernd Klein ***@***.***> wrote:
Question: did you check this strange behavior without connecting HDZero vTX, ESC, ExpressLRS?
If not, to avoid any circumstances around an issue with vTX, or ExpressLRS or ESC please remove this external devices.
- Start with a naked FC, if this will work, than reconnect ESC - test again -
- connect ExpressLRS - check - if it works as design, configure ExpressLRS -> check again (reboot, ....) than 3
- connect HDZero - check -
I know - lot of work - but such kind of problems are hard to identify and a good approach is to start step by step. Possible for you?
Thanks
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Damn I have this same problem! As soon as I changed Displayport to MSP it keeps going into DFU Mode! So annoying! I Have a BetaFPV F411 1S ELRS SX1280 board with an HDZero Whoop Lite VTX! |
I have the exact same issue. If it set "Set osd_displayport_device = AUTO" then i dont have the issue but the MSP doesn't work on the walksnail. It has something to do with the displayport device set to MSP. I also dont have the issue when the battery is plugged in from what i can tell. |
Describe the bug
For BF 4.3 RC 3, BF constantly goes into DFU mode.
Target is clracingf4. I have an HDZero TX5S.1 VTX and wired to tx4/rx4 on the FC.
To Reproduce
In ports tab turned I turn on MSP for UART 4. I
n CLI and set osd_displayport_device = MSP, save and all is ok.
Go back into CLI and set displayport_msp_serial = 3. Save.
After doing this, whenever I connect to betaflight is goes into DFU mode. If I disable DFU mode it goes to com3 temporarily then immediately goes back into DFU mode. Only way I can get around this is to re-flash firmware. I back leveled to 4.2.11 and all works just fine.
Expected behavior
Able to connect normally without going into DFU mode constantly.
Flight controller configuration
Flight controller
clracingf4
Other components
happymodel EP2 elrs receiver
HDzero tx5s.1
How are the different components wired up
receiver connected to uart 6 (tx to rx, rx to tx)
vtx connected to uart 4. tx to rx, rx to tx. power connected to vtx+,vtx- pads. Jumper is set for 7.2v.
Add any other context about the problem that you think might be relevant here
think I covered it all.
If you really need me to reflash to 4.3 RC3 and do commands without setting displayport_msp_serial = 3 but it may be a day or two before I have time. Send email to kevincyr01@gmail.com if you need this. I'm just re[porting this to try and help you to make firmware better.
The text was updated successfully, but these errors were encountered: