-
-
Notifications
You must be signed in to change notification settings - Fork 113
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
baro BMP280 not detect FURYF4OSD #415
Comments
Hmm might need to add baro drivers |
@Kaiowarez What file I need to modify ? And what I need to add ? Thanks |
Hi guys, So when I add this line "drivers/barometer/barometer_bmp280.c" like this in the FURY4 target folder, I flash my board with the FURYF4 target but I don't have any osd so it's not really good Do you have any lead ? |
you'll need a |
@nerdCopter thanks I can now make my hex file for this target but still nothing on the configurator, I also modify the target.h at line 92 and 93 but don't work. |
@maxgame91 , So you're flashing the local .hex you made and your external Baro 280 is still not seen, correct? |
@nerdCopter You are correct, I have this branch on my computer and make my own .hex and yes my external bmp280 is not seen, even when I add the driver in the "target.mk". It look like the i2c are define in the right pin but I'm clearly not a dev so maybe I'm wrong I'm really open to idea yes |
First you add the drivers on the. Mk file needed \ on it |
If it's on a uart make sure it's on either half or full duplex mode.. |
|
I add the
and you lost me at spi and cs pin sorry |
Yeah that's right
Then i2c_device needs to match which i2c it is
Then defined for baro to use then if baro has a cs pin its using and spi
instance as well needs to be defined
…On Thu, Nov 26, 2020, 12:31 PM maxgame91 ***@***.***> wrote:
I add the
i2c is working I tried on betaflight 4.2 and my bmp280 was detect
For my board scl and sda are define by this pin :
#define I2C1_SCL PB6 // SCL pad
#define I2C1_SDA PB7
and you lost me at spi and cs pin sorry
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#415 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOMD72BBFH6A3RHLGI4UADTSR2GF7ANCNFSM4UBIW7YA>
.
|
Has any official/test updates with this driver been made? Got another pilot on the FB page with same problem:
|
And another
|
i wonder if @JulioCesarMatias would be interested in this issue? |
yes, when i have time i will dedicate myself to it |
is there anyone to test this? |
Do I need to make a separate bug fix request for the |
Hopefully will hear results from one of the guys on FB page. |
@JulioCesarMatias Got a response. Baramoter is still not showing up on FURYF4OSD. See attached images (betaflight image included to show working): |
i cherry-picked code into 0.3.4: please test: |
@BeauBrewski , let me know if it works (has fair values) in the air as well, then i can merge to master. |
|
problem solved, close this. |
Hello,
I tried to use an external barometer, a BMP280 on my mamba f405 mk2 so I ha ve for target the FURYF4OSD, but my baro is not detect by the board.
I tried on betaflight 4.2 (need a custom unified target). So wiring is not the problem here.
In the CLI i have nothing when I type "get baro" I have nothing related to a barometer.
Do i need to modified something in the target or somewhere else ? My goal is to use this branch to have an alti limiter
The text was updated successfully, but these errors were encountered: