Posts: 155 Threads: 29 Likes Received: 36 in 28 posts Likes Given: 68 Joined: Apr 2017 Reputation: 0 Guys,
I got a banggood Omnibus F4 with OSD and I´m having an issue here.
- If I connect it on Betaflight it works fine, I can configure, reset everything goes well. But if I try to flash firmware (with or without NO BOOT SEQUENCE) option it hangs and buzzer start to do a constant noise.
- If I test the NO BOOT SEQUENCE I´mm pressing the boot button as expected, so this is not the problem.
The same problem happens If I connect the SBUS receiver on the board.
Have you seen this before ?
Any ideas ? ![[-]](https://intofpv.com/images/collapse.png) • Posts: 2,286 Threads: 38 Likes Received: 1,527 in 995 posts Likes Given: 1,881 Joined: Apr 2016 Reputation: 72 A few things:
You don't need to use the boot button unless you have flashed the wrong firmware to the board. This is true of all flight controllers.
There are many things that call themselves "Omnibus F4" on Banggood, you need to post a link to what you bought.
One of the Omnibus clones that Banggood are selling is complete rubbish and tends to blow up for no reason at all.
Don't select the "Full Chip Erase" option when flashing. The F4 based flight controllers don't like it. Posts: 155 Threads: 29 Likes Received: 36 in 28 posts Likes Given: 68 Joined: Apr 2017 Reputation: 0 30-Aug-2017, 12:00 AM (This post was last modified: 30-Aug-2017, 12:00 AM by flabombarda.) Hi Unseen, Here is the link: https://www.aliexpress.com/item/Betaflig...0.0.4hpLXr When I connect on betaflight and run the status command I get this: # version
# BetaFlight/OMNIBUSF4 3.0.1 Oct 18 2016 / 10:22:03 (48b7b4f) Even if I do not try to flash it with the boot buttom and with the erase option the same crap behavior happens: buzzer issues a constant noise, USB is no longer available and the board hangs...[/color][/font][/size] • Posts: 2,286 Threads: 38 Likes Received: 1,527 in 995 posts Likes Given: 1,881 Joined: Apr 2016 Reputation: 72 Hmmm...
I don't know how they managed to flash that firmware onto the board to start with.
The board is a clone of the Airbot Omnibus F4 Pro V2. The correct target to flash for this hardware is OMNIBUSF4SD • Posts: 97 Threads: 16 Likes Received: 51 in 28 posts Likes Given: 27 Joined: Jun 2017 Reputation: 0 30-Aug-2017, 09:00 AM (This post was last modified: 30-Aug-2017, 09:01 AM by Darozas.) (30-Aug-2017, 12:00 AM)flabombarda Wrote: Hi Unseen,
Here is the link:
https://www.aliexpress.com/item/Betaflig...0.0.4hpLXr
When I connect on betaflight and run the status command I get this:
# version
# BetaFlight/OMNIBUSF4 3.0.1 Oct 18 2016 / 10:22:03 (48b7b4f)
Even if I do not try to flash it with the boot buttom and with the erase option the same crap behavior happens: buzzer issues a constant noise, USB is no longer available and the board hangs...[/color][/font][/size] Use Driver Fixer for this board (If you had F3 board before) it could cause driver issues and makes board to don't work properly Download this https://impulserc.com/pages/downloads And try again Had same issue with my one took me while to get it to work properly on PC Regards • Posts: 2,286 Threads: 38 Likes Received: 1,527 in 995 posts Likes Given: 1,881 Joined: Apr 2016 Reputation: 72 Like I said, if he's trying to flash the OMNIBUSF4 target onto this board, it's the wrong target and that explains why the buzzer goes on permanently. If the wrong target is used, the pin assignments for the processor will be incorrect.
This is nothing to do with the wrong drivers, the problem is flashing the wrong target. • Posts: 155 Threads: 29 Likes Received: 36 in 28 posts Likes Given: 68 Joined: Apr 2017 Reputation: 0 (30-Aug-2017, 09:34 AM)unseen Wrote: Like I said, if he's trying to flash the OMNIBUSF4 target onto this board, it's the wrong target and that explains why the buzzer goes on permanently. If the wrong target is used, the pin assignments for the processor will be incorrect.
This is nothing to do with the wrong drivers, the problem is flashing the wrong target. Hi Unseen, OMNIBUSF4SD is exactly what I'm trying to use, but anyway, the firmware is not the issue, because even if I try any other version the same problem happens. the hang+buzzer doesn't start AFTER flashing new firmware, just by clicking on the FLASH button the problem happens. I tried to do the normal flash and the flash with no boot sequence, both cause the same problem • Posts: 97 Threads: 16 Likes Received: 51 in 28 posts Likes Given: 27 Joined: Jun 2017 Reputation: 0 (30-Aug-2017, 03:16 PM)flabombarda Wrote: Hi Unseen,
OMNIBUSF4SD is exactly what I'm trying to use, but anyway, the firmware is not the issue, because even if I try any other version the same problem happens.
the hang+buzzer doesn't start AFTER flashing new firmware, just by clicking on the FLASH button the problem happens.
I tried to do the normal flash and the flash with no boot sequence, both cause the same problem Make sure "FULL CHIP ERACE" IS unchecked its really important one Regards • Posts: 2,286 Threads: 38 Likes Received: 1,527 in 995 posts Likes Given: 1,881 Joined: Apr 2016 Reputation: 72 (30-Aug-2017, 03:16 PM)flabombarda Wrote: Hi Unseen,
OMNIBUSF4SD is exactly what I'm trying to use, but anyway, the firmware is not the issue, because even if I try any other version the same problem happens.
the hang+buzzer doesn't start AFTER flashing new firmware, just by clicking on the FLASH button the problem happens.
I tried to do the normal flash and the flash with no boot sequence, both cause the same problem That's bad news. It sounds like you have a bad clone. The problem with these clones seems to be in the 3.3V regulators that they use. Maybe trying to flash the firmware makes the CPU draw more current and that causes the regulator to drop out and crashes the bootloader. I can't imagine how anything you are doing could cause these problems, so I'd say you have a bad board. • Posts: 155 Threads: 29 Likes Received: 36 in 28 posts Likes Given: 68 Joined: Apr 2017 Reputation: 0 31-Aug-2017, 01:25 PM (This post was last modified: 31-Aug-2017, 01:27 PM by flabombarda.) (30-Aug-2017, 03:48 PM)Darozas Wrote: Make sure "FULL CHIP ERACE" IS unchecked its really important one
Regards I tried that too Darozas thanks !
(30-Aug-2017, 06:19 PM)unseen Wrote: That's bad news. It sounds like you have a bad clone. The problem with these clones seems to be in the 3.3V regulators that they use. Maybe trying to flash the firmware makes the CPU draw more current and that causes the regulator to drop out and crashes the bootloader.
I can't imagine how anything you are doing could cause these problems, so I'd say you have a bad board. I'm afraid so, this is the 2nd board that doesn't work I get from banggood.. these clones seem to be very unreliable.. • Posts: 97 Threads: 16 Likes Received: 51 in 28 posts Likes Given: 27 Joined: Jun 2017 Reputation: 0 31-Aug-2017, 02:02 PM (This post was last modified: 31-Aug-2017, 03:10 PM by Darozas.) What LED status you get on board??? GREEN Only ????
Try this
Make sure only "Manual Baud" is checked and select 115200. (If don't works try to change to different one)
Regards • Posts: 155 Threads: 29 Likes Received: 36 in 28 posts Likes Given: 68 Joined: Apr 2017 Reputation: 0 VERY STRANGE ...
I got the board again to see if I was able to flash it and it simply work.
NO erase option, and NO boot sequence option also.
something was different but I don´t know what.
Now board is working, the only issue is that when I try to connect on the USB it fails to connect on betaflight, I need to insist and click on connect few times before I get the connection working.
All I can think is: bad clone.
I flew 3 batteries now with no issues, so I cannot explain what was wrong, or why I have this odd USB behavior ... • |
