How to fully configure i2c sensor working with NCS bluetooth?

RE: How to fully configure i2c sensor working with NCS bluetooth?

Hakon — Tue, 16 Feb 2021 16:14:07 GMT

[quote user="new"]Arduino reads the same address with length 6 and gets different value from register and it is changing but nrf52840 gets different value and unchanging. (I have used i2c1 in board overlay)[/quote]

Can you use a logic analyzer to check the data that is being sent and received in both cases? Check the SDA and SCL pins.

RE: How to fully configure i2c sensor working with NCS bluetooth?

new — Sat, 13 Feb 2021 06:54:38 GMT

I modified example BME280 with bmp388 configurations and at the end even I forcefully written required pwr, odr and osr values. Attaching the .c and .h files. I am sorry for not maintaining readable script. Very much haphazard.

devzone.nordicsemi.com/.../bme280.c devzone.nordicsemi.com/.../bme280.h

RE: How to fully configure i2c sensor working with NCS bluetooth?

new — Sat, 13 Feb 2021 06:47:53 GMT

I am using NRF52840- zephyr (i2c_burst_read) and BMP388 sensor using I2C. I am successfully able to setup register enabling required feature and able to read the sensor data from I2C. However, the data read from data register doesn't change. The hexadecimal value read from arduino with same sensor board is completely different from that read in nrf52840 over i2c. Please help me know if I am missing ay fundamental understanding reading data value over i2c. I am reading register 0x04 with Length 6. Arduino reads the same address with length 6 and gets different value from register and it is changing but nrf52840 gets different value and unchanging. (I have used i2c1 in board overlay)

RE: How to fully configure i2c sensor working with NCS bluetooth?

Hakon — Tue, 26 Jan 2021 12:49:18 GMT

For a start, you can try changing i2c0 to either i2c1 or i2c2. There are conflicting memory addresses between i2c0 and uart0, so you should use a different i2c peripheral instance.

RE: How to fully configure i2c sensor working with NCS bluetooth?

new — Thu, 24 Dec 2020 06:19:13 GMT

Also, how to configure any GPIO PIN as INPUT or OUTPUT with Zephyr.

device_get_bindig('GPIO_0') is successful, but gpio_pin_configure(dev,20,GPIO_OUTPUT_ACTIVE/GPIO_OUTPUT_LOW/GPIO_OUTPUT) and gpio_pin_set(dev,20,1) is not working.

I am trying to set pin number 20 in NRF52840. But it is not working. I am unable to find any suitable example to fix this issue. Please help out.

RE: How to fully configure i2c sensor working with NCS bluetooth?

new — Thu, 24 Dec 2020 05:04:49 GMT

I tried all possibilities modifying;

DTS->Bindings, Devicetree.h, drivers, overlay, board.dts, but no progress in adding adxl345 sensor to custom 52840 board nor BMI160 to NRF52840 development kit.

device_get_binding(DT_LABEL(DT_INST(0,adi_adxl345) is always NULL and DT_NODE_HAS_STATUS(ADXL345,okay) is always NULL.

Driver->adxl345->cmake

devzone.nordicsemi.com/.../2555.CMakeLists.txt

Driver -> adxl_345.c

devzone.nordicsemi.com/.../adxl345.c

Drivers->adxl345->Kconfig

# ADXL345, 3-Axis, +/-16g Digital Accelerometer

# Copyright (c) 2020 Antmicro <www.antmicro.com>
# SPDX-License-Identifier: Apache-2.0
config ADXL345
	bool "ADXL345 Three Axis I2C accelerometer"
	depends on I2C
	help
	  Enable driver for ADXL345 Three-Axis Digital Accelerometer.

2. ncs->nrf->samples->bluetooth->mesh->adxl345->

nrf52840dk_nrf52840.overlay overlay file:

/*
 * Copyright (c) 2020, Nordic Semiconductor ASA
 *
 * SPDX-License-Identifier: Apache-2.0
 */

&i2c0 {
	compatible = "nordic,nrf-twim";
	status = "okay";
	sda-pin = <17>;
	scl-pin = <13>;
	clock-frequency = <I2C_BITRATE_FAST>;
	adxl345@53 {
		compatible = "adi,adxl345";
		label = "ADXL345";
		reg = <0x53>;
		status = "okay";
	};
};

devzone.nordicsemi.com/.../2555.CMakeLists.txt

sample.yaml

sample:
  name: adxl345 sample
  description: ADXL345 accelerometer sample application
tests:
  sample.sensor.adxl345:
    harness: sensor
    tags: sensors
    depends_on: i2c
    platform_allow: nrf52840dk_nrf52840

Proj.conf

CONFIG_STDOUT_CONSOLE=y
CONFIG_I2C=y
CONFIG_SENSOR=y
CONFIG_ADXL345=y

CONFIG_USE_SEGGER_RTT=y
CONFIG_RTT_CONSOLE=y
CONFIG_LOG_BACKEND_UART=y
CONFIG_SERIAL=y
CONFIG_UART_CONSOLE=n
CONFIG_PRINTK=y
CONFIG_CONSOLE=y

main.c

/*
 * Copyright (c) 2019 Brett Witherspoon
 *
 * SPDX-License-Identifier: Apache-2.0
 */

#include <zephyr.h>
#include <stdio.h>
#include <device.h>
#include <drivers/sensor.h>
#include <drivers/gpio.h>
#include <drivers/i2c.h>
K_SEM_DEFINE(sem, 0, 1);
#define adxl_sdo 20
#define adxl_cs  15
static void trigger_handler(const struct device *dev,
			    struct sensor_trigger *trig)
{
	switch (trig->type) {
	case SENSOR_TRIG_DATA_READY:
		if (sensor_sample_fetch(dev) < 0) {
			printf("Sample fetch error\n");
			return;
		}
		k_sem_give(&sem);
		break;
	case SENSOR_TRIG_THRESHOLD:
		printf("Threshold trigger\n");
		break;
	default:
		printf("Unknown trigger\n");
	}
}
const struct device *gpio_dev;
void i2c_init(){
  gpio_pin_configure(gpio_dev,adxl_sdo,GPIO_PULL_DOWN);
  gpio_pin_configure(gpio_dev,adxl_cs,GPIO_PULL_DOWN);
  gpio_pin_set(gpio_dev,adxl_sdo,0);
  gpio_pin_set(gpio_dev,adxl_cs,1);

}
void main(void)
{
	struct sensor_value accel[3];
        if(DT_NODE_HAS_STATUS(ADXL345,okay)){
        printf("Device found\n");
        }
	const struct device *dev = device_get_binding(DT_LABEL(DT_INST(0, adi_adxl345)));
	if (dev == NULL) {
		printf("Device get binding device\n");
		return;
	}

	while (true) {

			if (sensor_sample_fetch(dev) < 0) {
				printf("Sample fetch error\n");
				return;
			}


		if (sensor_channel_get(dev, SENSOR_CHAN_ACCEL_X, &accel[0]) < 0) {
			printf("Channel get error\n");
			return;
		}

		if (sensor_channel_get(dev, SENSOR_CHAN_ACCEL_Y, &accel[1]) < 0) {
			printf("Channel get error\n");
			return;
		}

		if (sensor_channel_get(dev, SENSOR_CHAN_ACCEL_Z, &accel[2]) < 0) {
			printf("Channel get error\n");
			return;
		}

		printf("x: %.1f, y: %.1f, z: %.1f (m/s^2)\n",
		       sensor_value_to_double(&accel[0]),
		       sensor_value_to_double(&accel[1]),
		       sensor_value_to_double(&accel[2]));
	}
}

Above is my project configuration files.

I am trying to read ADXL345 accelerometer value from NRF52840 custom board. The device is not getting detected. Similar configuration I have used for BMI160 with NRF52840 development kit but there also device binding is NULL.

Please help me find the missing modifications for getting the sensor working.

RE: How to fully configure i2c sensor working with NCS bluetooth?

new — Tue, 22 Dec 2020 06:08:06 GMT

I tried using BME680 to build BMI160 sensor support for NRF5340. Whatever overlay name such as NRF5340PDK/DK_NRF5340_CPUAPP/NS I try the BOSCH_BMI160 not declared error repeats.

I have modified files for BMI160 said following :

1. https://devzone.nordicsemi.com/f/nordic-q-a/65900/change-sda-and-scl-pin-for-i2c1-on-nrf5340

2. https://devzone.nordicsemi.com/f/nordic-q-a/66230/how-to-add-new-i2c-based-sensor-device-to-ncs-v1-3-0-zephyr-drivers-sensor

But it throws error : DT_N_INST_)_BOSCH_BMI160_P_LABEL undeclared in expansion of macro 'UTIL_CAT'

How to bypass I2C SCK with custom generated clock frequency (greater than 1 MHz) from GPIO to read sensor values?

RE: How to fully configure i2c sensor working with NCS bluetooth?

Hakon — Fri, 18 Dec 2020 11:27:50 GMT

Hello,

the most useful guide is probably the Zephyr devicetree guide. It would also be helpful if you could post the overlay file and tell what you are doing, to identify the issue.