Hello,
Probably not a firmware issue but I thought posting here might save others time and frustration. I am using an Omnibus F4v3 for my latest build and found that my laptop will not recognize the Omnibus in DFU mode with a GPS plugged in and powered up. This also happens with the latest version of Cleanflight for OMNIBUSF4SD target. Removing power from the GPS seems to allow proper DFU mode detection and driver configuration...
K
GPS or the compass ? Sda/SLC lines?
Having compass connected without powering it up is often begging for
problems.
Hello,
Probably not a firmware issue but I thought posting here might save others
time and frustration. I am using an Omnibus F4v3 for my latest build and
found that my laptop will not recognize the Omnibus in DFU mode with a GPS
plugged in and powered up. This also happens with the latest version of
Cleanflight for OMNIBUSF4SD target. Removing power from the GPS seems to
allow proper DFU mode detection and driver configuration...K
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/iNavFlight/inav/issues/1804, or mute the thread
https://github.com/notifications/unsubscribe-auth/AFaHNtqdiD-abK85DUj1nvP2gm5q6BLKks5sFULvgaJpZM4N9hrM
.
@oleost
I guess I should have included this detail.. but for me its the GPS... I am using the NEO m8N's compass but, the problem seems to be the same with the Sda/Slc connected or not...
It's the hardware limitation. Built-in bootloader activates on USB/UART1. If there is activity on UART1 bootloader doesn't enable USB DFU.
Copy that....