BMP388 changes for BMP390 using DTS and set Chip-id #77624
Unanswered
ruehlchris
asked this question in
General
Replies: 2 comments
-
@ruehlchris are you working on this? I am new to Zephyr but I can help test. I have a BMP390 and very much want to use it in a project. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Hi, @gherlein |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, with the BMP390 drop in replacement for Bosch BMP388 it would be easy to use the existing driver with a minor change to check the chip-id (0x50=bmp388; 0x60=bmp390).
Changes would be:
dts/bindings bosch,bmp388.yaml add the description for chip-id here.
bmp388.c use data->chip_id from new struct member which read the chip_id from dts defines
bmp388.h remove the obsolete define for the 388 only chip-id.
bosch_bmp390: bmp390@77 {
compatible = "bosch,bmp388";
reg = <0x77>;
odr = "12.5";
osr-press = <8>;
osr-temp = <1>;
iir-filter = <3>;
chip-id = <0x60>; /* 0x50 = bmp388; 0x60 = bmp390 */
status="disabled"
};
On the side, in the bmp388 driver are some improvements can do.
I have started some work on it for a project we working on replacing bmp180 with bmp390.
Please let me know what you think.
Cheers.
Chris
Beta Was this translation helpful? Give feedback.
All reactions