nRF9160 DK I2C only receives the first byte with BME280

RE: nRF9160 DK I2C only receives the first byte with BME280

Didrik Rokhaug — Wed, 27 Nov 2019 10:14:56 GMT

Could you please open a new ticket?

At the moment, when a ticket has a "verified answer", it does not appear back in our list of open tickets, so it is hard for us to keep track.

Also, in your ticket, please provide your overlay file and configuration file to help us identify your problem.

Best regards,

Didrik

RE: nRF9160 DK I2C only receives the first byte with BME280

Funyc — Tue, 26 Nov 2019 15:47:29 GMT

I have a similar error:

2> In file included from C:/nordicsdk/ncs/zephyr/include/drivers/sensor.h:23:0,
2> from C:/nordicsdk/ncs/zephyr/drivers/sensor/bme280/bme280.c:11:
2> C:/nordicsdk/ncs/zephyr/drivers/sensor/bme280/bme280.c:384:29: error: 'DT_INST_0_BOSCH_BME280_LABEL' undeclared here (not in a function); did you mean 'DT_INST_0_SOC_NV_FLASH_LABEL'?
2> C:/nordicsdk/ncs/zephyr/include/device.h:107:11: note: in definition of macro 'DEVICE_AND_API_INIT'
Build failed

I think that I used the same procedure

RE: nRF9160 DK I2C only receives the first byte with BME280

dvldogg13 — Thu, 25 Jul 2019 06:27:20 GMT

Is there a way to change the power mode of the BME280 if I am using the driver from Zephyr? I want to be able to use Forced mode.

RE: nRF9160 DK I2C only receives the first byte with BME280

dvldogg13 — Wed, 17 Jul 2019 15:51:45 GMT

Thank you. I changed everything to i2c_2 and it worked.

RE: nRF9160 DK I2C only receives the first byte with BME280

Didrik Rokhaug — Wed, 17 Jul 2019 08:13:28 GMT

Hi.

It should say "label" in the overlay file, not "lable". This should fix the undeclared DT_BOSCH_BME280_0_LABEL error.

The sample should run without any modifications, but the sensor must be connected and the details in the overlay and configuration file must be correct. Please make sure that the pins and address in the overlay file is correct (the I2C slave address is listed both after the "@" in the node name and in the "reg" field).

If your application is running in non-secure mode the I2C must be set up to be used in non-secure mode. You can either try to build the application for the nrf9160_pca10090 (not ns) board to run the application in secure mode, or you must make sure that the I2C/TWIM peripheral is configured correctly. From your output it looks like TWIM2 is configured for non-secure use, so you could try to change i2c3 to i2c2 in the overlay file and CONFIG_I2C_3 to CONFIG_I2C_2 in the configuration file.

Best regards,

Didrik

RE: nRF9160 DK I2C only receives the first byte with BME280

dvldogg13 — Tue, 16 Jul 2019 21:29:51 GMT

Thank you for the response. After I add the overlay file and add the line to the prj.conf file, do I still need to configure the nRF9160 board in the main.c file? Or should I be able to run it as is?

When I built, I got an error on line 385 of the bme280.c file stating that DT_BOSCH_BME280_0_LABEL is undeclared and asked if it meant DT_BOSCH_BME280_0, so I changed it to that. After, I was able to build without errors. I attempted to run the program, but the following screenshot shows what happens.

RE: nRF9160 DK I2C only receives the first byte with BME280

Didrik Rokhaug — Tue, 16 Jul 2019 15:23:57 GMT

Hi.

Zephyr has a driver for interfacing with the BME280. Take a look at their sample in the ncs/zephyr/samples/sensors/bme280 folder.

In order to run the sample on the nRF9160DK you have to add your own overlay file (nrf9160_pca10090.overlay):

&i2c3 {
    status = "ok";
    sda-pin = <12>;
    scl-pin = <11>;
    
    bme280@76 {
        compatible = "bosch,bme280";
        reg = <0x76>;
        label = "BME280";
    };
};

You must also add the following lines in the prj.conf file in order to enable I2C:

CONFIG_I2C_3=y

Best reagrds,

Didrik