nRF9160 with CCS811 and Missing Log in LTE Link Monitor

Question

Hello,

I am trying to interface to a CCS811 sensor found here to the nRF9160 DK. I am using NCS v1.2.0.

I followed the instructions from the blog here which covers how to do this with a BME280 example and adapted them to work with the CCS811 sensor. Please verify if there are any missing steps or other places that need changing:

I copied the CCS811 example from ncs\zephyr\samples\sensor\ccs811 to ncs\nrf\samples\nrf9160\ccs811
I created an nrf9160_pca10090ns.overlay file as shown below.
I modified line 115 of main.c to use my device label "CCS811"
I added CONFIG_I2C_2=y to prj.conf
I build the project using west build -b nrf9160_pca10090ns

When I run this example and look at the logs using LTE Link Monitor (latest version v1.1.1) all I see is this (It's stuck on the "*** Booting Zephyr OS build v2.1.99-ncs1 ***" line):

When I run the exact same example looking at the logs with Tera Term, I see one additional line ("Failed to get device binding"):

I am disconnecting from one terminal before opening the other and simply resetting the board (by pressing the reset button) to reboot. I don't have the sensor hooked up to my board so that explains why I am seeing the "Failed to get device binding" message in Tera Term but why am I not seeing that message in LTE Link Monitor?

line 115 of main.c edited

struct device *dev = device_get_binding("CCS811");

added to prj.conf

CONFIG_I2C_2=y

nrf9160_pca10090ns.overlay

&i2c2 {
	status = "ok";
	sda-pin = < 12 >;
	scl-pin = < 11 >;
    clock-frequency = <I2C_BITRATE_STANDARD>;  
	
	/* The I2C address could be one of two, here 0x5A is assumed */
	ccs811@5A {
		compatible = "ams,ccs811";
		reg = <0x5A>;
		label = "CCS811";
	};
};

merged.hex for nrf9160_pca10090ns: /cfs-file/__key/support-attachments/beef5d1b77644c448dabff31668f3a47-d9f2a3f32f4949a8ba7acdd814276ae3/1856.merged.hex

Full Project here: /cfs-file/__key/support-attachments/beef5d1b77644c448dabff31668f3a47-d9f2a3f32f4949a8ba7acdd814276ae3/4454.ccs811.zip

Regards,

Akash Patel

Jan Tore Guggedal · Accepted Answer

Hi Akash,

I think the reason you're not seeing the last line in the Link Monitor, is because there's no newline '\n' character at the end of that print, and it seems Link Monitor outputs on a per-line basis.

Regarding the change on line 115, I think you can leave it as it was originally. The define will be generated using the CCS811 entry in the overlay file.
You can confirm that by looking in "build/zephyr/include/generated/devicetree_unfixed.h" and check that it's correctly defined.

Note that you can also specify interrrupt, reset and wake-up GPIOs in the overlay, and they will then be used by the driver to provide that functionality, like this:

&i2c2 {
	status = "ok";
	sda-pin = < 12 >;
	scl-pin = < 11 >;
    clock-frequency = <I2C_BITRATE_STANDARD>;

	/* The I2C address could be one of two, here 0x5A is assumed */
	ccs811@5A {
		compatible = "ams,ccs811";
		reg = <0x5A>;
		label = "CCS811";
		reset-gpios = <&gpio0 21 0>;
		wake-gpios = <&gpio0 22 0>;
		irq-gpios = <&gpio0 23 0>;
	};
};

Where 21, 22 and 23 are pin numbers, and 0s are GPIO flags.

It's not entirely clear to me from the driver code if these pins are required for the sensor to function properly.

Best regards,

Jan Tore

nRF9160 with CCS811 and Missing Log in LTE Link Monitor

Top Replies