BME280 Not working on v2.1.1

RE: BME280 Not working on v2.1.1

RodWatt — Mon, 31 Oct 2022 09:09:36 GMT

Thanks Vidar,

I confirmed that the BME680 device is faulty. I connected it to a Raspberry pi and ran some basic python code which failed to read its ID, it worked with my '280 device.

Rod

RE: BME280 Not working on v2.1.1

Vidar Berg — Mon, 31 Oct 2022 09:05:06 GMT

Hi Rod,

Maybe it could have it caused by stales settings, but I think it must have been the pinctrl assignments in that case, as the other configurations shown in your generated zephyr.dts were correct.

A pristine build is required when you add or remove configurations files.

https://nrfconnect.github.io/vscode-nrf-connect/connect/ui.html?h=

Vidar

RE: BME280 Not working on v2.1.1

RodWatt — Sun, 30 Oct 2022 13:32:51 GMT

Hi Vidar,

I have moved back to I2C0 and its all working fine. I still cannot get my BME680 sensor to work but I have got both the BME280 and my CFD display, which are both on the !2C0 bus working so am starting to think the '680 could be damaged. So, I am still at a loss to explain what the initial problem was. I am very methodical now about deleting my build directory after major changes. Maybe previously I was picking up some stale settings?

I am using Visual Studio, I assume I can update the build commands so I can force a pristine build every time.

Rod

RE: BME280 Not working on v2.1.1

RodWatt — Fri, 28 Oct 2022 08:29:55 GMT

Hi Vidar,

I will check the registers later when i get a chance. I do have external pull ups, this is a board that has been working previously. My board is a nrf52840dongle_nrf52840.

Rod

RE: BME280 Not working on v2.1.1

Vidar Berg — Fri, 28 Oct 2022 07:58:53 GMT

Hi Rod,

The ticket is open now, so we can continue here.

Are you able to check the TWIM0/1 registers like shown in my previous comment to see if there are any differences when you change from instance 1 to 0?

It is also worth checking if the GPIO configuration for the SDA and SCL pin matches this : Master mode pin configuration.

Vidar

Edit: In case you don't have external pull-ups on the SDA/SCL lines, please add the 'bias-pull-up' property to your overlay (ref. https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/build/dts/api/bindings/pinctrl/nordic,nrf-pinctrl.html#grandchild-node-properties)

&pinctrl {

	i2c0_default_alt: i2c0_default_alt {
		group2 {
			psels = <NRF_PSEL(TWIM_SDA, 0, 17)>, <NRF_PSEL(TWIM_SCL, 0, 20)>;
			bias-pull-up;
		};
	};

	i2c0_default_sleep: i2c0_default_sleep {
		group3 {
			psels = <NRF_PSEL(TWIM_SDA, 0, 17)>, <NRF_PSEL(TWIM_SCL, 0, 20)>;
			low-power-enable;
		};
	};
};

Also, I don't think I have asked you earlier, but what board do you build for, is it the '52840dk_nrf52840'?

RE: BME280 Not working on v2.1.1

RodWatt — Fri, 28 Oct 2022 07:47:22 GMT

Hi Vidar,

Yes, I am also not 100% convinced that this was the actual fix, it could be a coincidence. Previously, I had used !2C0. I will put it back to I2C0 and see if it still works.

Since posting my "fix", i have tried to get the BME680 sensor to work and the CFB display, both peripherals I have previously had working, also fail with !2C errors. I think there is someone more fundamental going on here.

Can you open this ticket up again?

Rod

RE: BME280 Not working on v2.1.1

Vidar Berg — Fri, 28 Oct 2022 07:30:20 GMT

Hi Rod,

Thank your for the update, I'm glad to hear that it finally works now! Although, it would have been nice to understand why i2c0 did not work.

The build should have triggered an error at compile if another peripheral with a shared ID such as spi0 had been enabled. The peripheral also seems to get initialized correctly when I run it here. I will make sure to update this ticket if I figure out what may have caused this.

Vidar

RE: BME280 Not working on v2.1.1

RodWatt — Thu, 27 Oct 2022 15:11:55 GMT

Hi Vidar,

I got it working! I think the change was to move to using I2c1. I also actively disabled some other peripherals. For completeness, I have shared my overlay file below. I am using the standard code from the samples.

Rod

&pinctrl {
	uart0_default_alt: uart0_default_alt {
		group0 {
			psels = <NRF_PSEL(UART_TX, 0, 24)>, <NRF_PSEL(UART_RX, 0, 22)>;
		};
	};

	uart0_sleep_alt: uart0_sleep_alt {
		group1 {
			psels = <NRF_PSEL(UART_TX, 0, 24)>, <NRF_PSEL(UART_RX, 0, 22)>;
			low-power-enable;
		};
	};


	i2c1_default_alt: i2c1_default_alt {
		group2 {
			psels = <NRF_PSEL(TWIM_SDA, 0, 17)>, <NRF_PSEL(TWIM_SCL, 0, 20)>;
		};
		
	};

	i2c1_sleep_alt: i2c1_sleep_alt {
		group3 {
			psels = <NRF_PSEL(TWIM_SDA, 0, 17)>, <NRF_PSEL(TWIM_SCL, 0, 20)>;
			low-power-enable;
		};
		
	};
};

&uart0 {
	pinctrl-0 = <&uart0_default_alt>;
	pinctrl-1 = <&uart0_sleep_alt>;	
	pinctrl-names = "default", "sleep";
	compatible = "nordic,nrf-uart";
	current-speed = <115200>;
	status = "okay";
};

&i2c1 {
	status = "okay";
	compatible = "nordic,nrf-twim";
	pinctrl-0 = <&i2c1_default_alt>;
	pinctrl-1 = <&i2c1_sleep_alt>;
	pinctrl-names = "default", "sleep";
	clock-frequency = <I2C_BITRATE_STANDARD>;
	bme280@76 {
		compatible = "bosch,bme280";
		reg = <0x76>;
		label = "BME280";
		status = "okay";
	};
};

&i2c0 {
	status = "disabled";
 };

 &spi0 {
	status = "disabled";
 };

&spi1 {
	status = "disabled";
 };

 &gpio0 {
	status = "disabled";
 };

 &gpio1 {
	status = "disabled";
 };

 &usbd {
	status = "disabled";
 };

RE: BME280 Not working on v2.1.1

RodWatt — Wed, 26 Oct 2022 14:38:06 GMT

Hi Vidar,

Sorry, maybe that was a bad example. The '680 is 0x77, the '280 is 0x76.I have tried both. I have also tried both twi and twin.

Rod

RE: BME280 Not working on v2.1.1

Vidar Berg — Wed, 26 Oct 2022 14:00:19 GMT

Hi Rod,

I notice you are setting the i2c address to 0x77 in the overlay you posted here: RE: Errors when using BME680 Sample Code and 0x76 in the one you posted here. Could this be the reason? I guess you could also try to use the TWI instead of the TWIM peripheral by changing "compatible" from "compatible = "nordic,nrf-twim"; to compatible = "nordic,nrf-twi";

Best regards,

Vidar

RE: BME280 Not working on v2.1.1

RodWatt — Wed, 26 Oct 2022 13:21:27 GMT

Hi Vidar,

Sorry, I was mistaken, the "CONFIG_DT_HAS_BOSCH_BME280_ENABLED not defined" is still there.

I cant recall when this stopped working, I know it worked before the changes to the overlay file.

Errors when using BME680 Sample Code

Since then, the board hasn't changed, the pinout hasn't changed,

Rod

RE: BME280 Not working on v2.1.1

Vidar Berg — Tue, 25 Oct 2022 15:28:52 GMT

Hi Rod,

OK, this is a good step in the right direction. I have only been focusing on the "CONFIG_DT_HAS_BOSCH_BME280_ENABLED not defined" warning until now. The 2nd error which you are seeing now is a runtime error and comes from the driver here: https://github.com/nrfconnect/sdk-zephyr/blob/main/drivers/i2c/i2c_nrfx_twim.c#L171, and it occurs during initialisation of the driver on startup.

It sounds like you were able to interface with the sensor before you updated to SDK v2.1.1. What version did you use previously? Also, is there anything else that have changed? Pin assignments, etc?

The best way to troubleshoot this further may be to use a logic analyzer and probe the bus lines, if you have one available.

Vidar

RE: BME280 Not working on v2.1.1

RodWatt — Tue, 25 Oct 2022 13:08:30 GMT

Hi Vidar,

No I dont see that error any more, just this one

Error: Device "BME280" is not ready; check the driver initialization logs for errors.
[00:00:00.753,021] <err> i2c_nrfx_twim: Error on I2C line occurred for message 0

Rod

RE: BME280 Not working on v2.1.1

Vidar Berg — Tue, 25 Oct 2022 13:02:26 GMT

Hi Rod,

Thanks for confirming that CONFIG_DT_HAS_BOSCH_BME280_ENABLED is defined in .config. But do you still see this warning in your build log:

CONFIG_BME280 was assigned the value y, but got the value n. Missing dependencies:
DT_HAS_BOSCH_BME280_ENABLED

It says CONFIG_BME280 is set to =n because CONFIG_DT_HAS_BOSCH_BME280_ENABLED is not selected.

Vidar

RE: BME280 Not working on v2.1.1

RodWatt — Tue, 25 Oct 2022 12:56:52 GMT

Hi Vidar,

I can see that CONFIG_DT_HAS_BOSCH_BME280_ENABLED is enabled in .config

However, when I look at my config file, it says its set to n in build

Yes, I have tried the original code, same error.

Rod

RE: BME280 Not working on v2.1.1

Vidar Berg — Tue, 25 Oct 2022 11:22:52 GMT

Hi Rod,

Do you still get the warning that the 'DT_HAS_BOSCH_BME280_ENABLED' dependency is missing? I tried now to build the sample for 'nrf52840dk_nrf52840' with the overlay you posted, but it appears to be working as expected for me.

Generated zephyr.dts from nrf52840dk_nrf52840 build with overlay

CONFIG_DT_HAS_BOSCH_BME280_ENABLED enabled in .config

[quote user="RodWatt"]Weirdly, its picking up arduino_i2c?[/quote]

This comes from the board file. Dev kits following the arduino form factor will typically define interfaces such as arduino_i2c, arduino_spi, etc to let the application know what i2c or SPI interface to select when connecting the board to arduino type shields. It's like a tag/label to help the program select the correct interface.

Have you tried with the original bme280 sample as well?

RE: BME280 Not working on v2.1.1

RodWatt — Tue, 25 Oct 2022 10:31:48 GMT

Hi Vidar,

Mine looks like this,

Weirdly, its picking up arduino_i2c?

Rod

RE: BME280 Not working on v2.1.1

Vidar Berg — Tue, 25 Oct 2022 05:56:40 GMT

Hi Rod,

Could you check the generated zephyr dts in your build folder to see if it match your overlay (<build dir>/zephyr/zephyr.dts)?

For comparison, this is what I get if I build the bme280 sample for the 'bl654_sensor_board':

[quote userid="76221" url="~/f/nordic-q-a/93185/bme280-not-working-on-v2-1-1/392254"]But this is now throwing an error, has this syntax changed?[/quote]

Yes, the peripheral IO properties were replaced with pinctrl. So, they are no longer defined in the board files.

Vidar

RE: BME280 Not working on v2.1.1

RodWatt — Mon, 24 Oct 2022 20:55:34 GMT

Previously, I had to add the following lines to get this to work,

&i2c0{
/delete-property/sda-gpios;
/delete-property/scl-gpios;
};

But this is now throwing an error, has this syntax changed?

Rod

RE: BME280 Not working on v2.1.1

RodWatt — Mon, 24 Oct 2022 20:30:42 GMT

Hi Vidar,

Thanks for the suggestion. I have updated my overlay file as suggested but still seeing the same error.

Rod

RE: BME280 Not working on v2.1.1

Vidar Berg — Mon, 24 Oct 2022 18:59:03 GMT

Hello,

The error indicates that the BM280 is not enabled in your DT. Please add the "status = "okay"; line to your overlay as shown here: https://github.com/nrfconnect/sdk-zephyr/blob/d9f99ed1951a973c691cd5d6bd70aecb597b2030/boards/arm/bl654_sensor_board/bl654_sensor_board.dts#L87

Best regards,

Vidar

RE: BME280 Not working on v2.1.1

RodWatt — Mon, 24 Oct 2022 15:17:37 GMT

Sorry, forgot to post the error message,

Error: Device "BME280" is not ready; check the driver initialization logs for errors.
[00:00:00.753,021] <err> i2c_nrfx_twim: Error on I2C line occurred for message 0

Rod