nRF9160 with CCS811 and Missing Log in LTE Link Monitor

RE: nRF9160 with CCS811 and Missing Log in LTE Link Monitor

Akash Patel — Thu, 08 Jul 2021 17:01:24 GMT

Hello mschweig,

I actually had posted this question on behalf of a customer and I actually do not own a CCS811 sensor. Given that this DevZone ticket is over a year old, I would recommend opening a new ticket with the problem you are facing and someone from our DevZone support team should be able to help you.

RE: nRF9160 with CCS811 and Missing Log in LTE Link Monitor

mschweig — Thu, 08 Jul 2021 10:31:43 GMT

Hi I am using the one with 5A register, but I am also getting "Failed to get device binding". Have you managed to communicate with the CCS811?

RE: nRF9160 with CCS811 and Missing Log in LTE Link Monitor

Aditya_s — Thu, 16 Jul 2020 22:01:28 GMT

Thank you, I will do that.
Just for the information sake, which CCS811 sensor were you using? The one by Sparkfun or by Adafruit?

RE: nRF9160 with CCS811 and Missing Log in LTE Link Monitor

Akash Patel — Thu, 16 Jul 2020 21:59:05 GMT

Hello Aditya,

I see that you have opened a ticket for the issue here. I would encourage you to work with the team in that ticket. Hopefully you will get a response soon. It will also be helpful if you included in that ticket your SDK version and your source code for the project. You should be edit your original post to include that information.

Regards,

Akash

RE: nRF9160 with CCS811 and Missing Log in LTE Link Monitor

Aditya_s — Thu, 16 Jul 2020 17:37:00 GMT

Hello Akash,

Was this helpful? I had similar issues I followed the steps but I get this error "Failed to get device binding"

RE: nRF9160 with CCS811 and Missing Log in LTE Link Monitor

Jan Tore Guggedal — Fri, 03 Apr 2020 17:05:33 GMT

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