How to connect other sensor to nrf9160 (i2c and GPIO)

Liza 7 months ago

Hi,

I want to connect LDC2114 to nRF9160. I write the nrf9160dk_nrf9160_ns.overlay and the astri,ldc2114.yaml. I don't know how to set GPIOs in &i2c1 - ldc2114: ldc2114@2a which are the output pins of LDC2114 and input pins of nRF9160.

Fullscreen 1462.nrf9160dk_nrf9160_ns.overlay.txt Download

/ {
	/* Map the devices to the aliases of the application. */ 
	aliases {	
		ldc-sensor = &ldc2114;
	};
	
};

&i2c1 {
    compatible = "nordic,nrf-twim";
    #address-cells = < 0x1 >;
    #size-cells = < 0x0 >;
    reg = < 0x9000 0x1000 >;
    // clock-frequency = < 0x186a0 >;
    clock-frequency = <I2C_BITRATE_STANDARD>;
    interrupts = < 0x9 0x1 >;
    status = "okay";
    pinctrl-0 = < &i2c1_default >;
    pinctrl-1 = < &i2c1_sleep >;
    pinctrl-names = "default", "sleep";
    ldc2114: ldc2114@2a{
        compatible = "astri,ldc2114";   //binding
        status = "okay";
        reg = < 0x2a >;
        label = "LDC2114";
        gpio-controller;
        #gpio-cells = < 0x2 >;
        intb-gpios = < &gpio0 25 0 >; // LDC2114 INTB pin -> nrf9160 INPUT P0.25
        in0-gpios = < &gpio0 24 0 >;  // LDC2114 OUT0 pin -> nrf9160 INPUT P0.24
        in1-gpios = < &gpio0 23 0 >;  // LDC2114 OUT1 pin -> nrf9160 INPUT P0.23
        in2-gpios = < &gpio0 22 0 >;  // LDC2114 OUT2 pin -> nrf9160 INPUT P0.22
        in3-gpios = < &gpio0 21 0 >;  // LDC2114 OUT3 pin -> nrf9160 INPUT P0.21
    };
};

&i2c2 { 
	status = "disabled";
};

&pinctrl {
	i2c1_default: i2c1_default {
		group1 {
			psels = <NRF_PSEL(TWIM_SDA, 0, 30)>,
				    <NRF_PSEL(TWIM_SCL, 0, 31)>;
		};
	};

	i2c1_sleep: i2c1_sleep {
		group1 {
			psels = <NRF_PSEL(TWIM_SDA, 0, 30)>,
				    <NRF_PSEL(TWIM_SCL, 0, 31)>;
			low-power-enable;
		};
	};
};

Fullscreen 2308.astri,ldc2114.yaml.txt Download

# Copyright (c) 2018, Peter Bigot Consulting, LLC
# SPDX-License-Identifier: Apache-2.0

description: Sensor LDC2114

compatible: "astri,ldc2114"

include: [sensor-device.yaml, i2c-device.yaml, gpio-controller.yaml, base.yaml]

properties:
  reg:
    required: true

  #alert-gpios:

  "#gpio-cells":
    const: 2

  intb-gpios:
    type: phandle-array
    description: |
      LDC2114 INTB pin -> nrf9160 INPUT P0.25

  in0-gpios:
    type: phandle-array
    description: |
      LDC2114 OUT0 pin -> nrf9160 INPUT P0.24

  in1-gpios:
    type: phandle-array
    description: |
      LDC2114 OUT1 pin -> nrf9160 INPUT P0.23

  in2-gpios:
    type: phandle-array
    description: |
      LDC2114 OUT2 pin -> nrf9160 INPUT P0.22

  in3-gpios:
    type: phandle-array
    description: |
      LDC2114 OUT3 pin -> nrf9160 INPUT P0.21

gpio-cells:
  - pin
  - flags

Also, What else should I do in order to connect the devices?

Best regards,

Liza

Parents

0 Vidar Berg 7 months ago

Hi Liza,

It looks like you have configured everything correctly in your Devicetree overlay. Are you getting build errors, or does it fail when you try to run the application?

Best regards,

Vidar
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Liza 7 months ago in reply to Vidar Berg

Hi Vidar Berg,

I cannot call gpios from ldc2114 Devicetree. Since the gpios are input pins, so I call them from node gpio0 "dev_gpio = device_get_binding(DEVICE_DT_NAME(DT_NODELABEL(gpio0)));" and it works.

Do you know how to call gpios from node ldc2114?

Best regards,

Liza
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

0 Liza 6 months ago in reply to Vidar Berg

Hi Vidar,

You are right! The RESET register is supposed to be 0 after reset. I read the status register and get what I want.

But it seems that i2c_burst_write() and i2c_burst_read() have byte limit?

I try to write 27 bytes buff to LDC_REG_CHAN_EN(0x0c) and the writing error occurs. Then I reduce the buff to 15 bytes, and write & read success.

Fullscreen i2c_burst_write.txt Download

------------------------write 27 bytes to LDC_REG_CHAN_EN (0x0c):--------------------------------------------------

uint8_t configbuf[]={                            0xFF, 0x03, 0x3F, 0x00, //0x0C ~0x0F
                0x3F, 0x01, 0x3F, 0x07, 0x3F, 0x07, 0x00, 0x02, //0x10 ~0x17
                0x03, 0x00, 0xff, 0x00, 0xFF, 0x00, 0x00, 0x00, //0x18 ~0x1F
                0xA7, 0x00, 0xA7, 0x00, 0xA7, 0x00, 0xA7};      //0x20
uint8_t cfgcomp[32];

        k_sleep(K_MSEC(2));
        error = i2c_burst_write(dev_i2c,i2c_dt_ldc2114.addr,LDC_REG_CHAN_EN,configbuf, 27);
        if(error!=0){
            printk("\n--ERROR: LDC_REG_CHAN_EN: Failed to write data at address 0x0%x.-- \n\r", LDC_REG_CHAN_EN);
            return;
        } 
        k_sleep(K_MSEC(2));
        error = i2c_burst_read(dev_i2c,i2c_dt_ldc2114.addr,LDC_REG_CHAN_EN,cfgcomp, 27);
        if(error!=0){
            printk("\n--ERROR: LDC_REG_CHAN_EN: Failed to read data at address 0x0%x.-- \n\r", LDC_REG_CHAN_EN);
            return;
        } 
        for(i=0;i<27;i++){
            printk("configbuf[%d] = %x   ", i, configbuf[i]);
            printk("cfgcomp[%d] = %x\n", i, cfgcomp[i]);
            if(cfgcomp[i] != configbuf[i]){
                printk("\n--ERROR: LDC_REG_CHAN_EN--\n");
                //return;
            }
        }


------------------------output：-------------------------------------------
--ERROR: LDC_REG_CHAN_EN: Failed to write data at address 0x0c.--




--------------------------After reducing the buff to 15 bytes:------------------------------

uint8_t configbuf[]={                            0xFF, 0x03, 0x3F, 0x00, //0x0C ~0x0F
                0x3F, 0x01, 0x3F, 0x07, 0x3F, 0x07, 0x00, 0x02, //0x10 ~0x17
                0x03, 0x00, 0xff, 0x00, 0xFF, 0x00, 0x00, 0x00, //0x18 ~0x1F
                0xA7, 0x00, 0xA7, 0x00, 0xA7, 0x00, 0xA7};      //0x20
uint8_t cfgcomp[32];

        k_sleep(K_MSEC(2));
        error = i2c_burst_write(dev_i2c,i2c_dt_ldc2114.addr,LDC_REG_CHAN_EN,configbuf, 15);
        if(error!=0){
            printk("\n--ERROR: LDC_REG_CHAN_EN: Failed to write data at address 0x0%x.-- \n\r", LDC_REG_CHAN_EN);
            return;
        } 
        k_sleep(K_MSEC(2));
        error = i2c_burst_read(dev_i2c,i2c_dt_ldc2114.addr,LDC_REG_CHAN_EN,cfgcomp, 15);
        if(error!=0){
            printk("\n--ERROR: LDC_REG_CHAN_EN: Failed to read data at address 0x0%x.-- \n\r", LDC_REG_CHAN_EN);
            return;
        } 
        for(i=0;i<15;i++){
            printk("configbuf[%d] = %x   ", i, configbuf[i]);
            printk("cfgcomp[%d] = %x\n", i, cfgcomp[i]);
            if(cfgcomp[i] != configbuf[i]){
                printk("\n--ERROR: LDC_REG_CHAN_EN--\n");
                //return;
            }
        }


------------------output：----------------
configbuf[0] = ff   cfgcomp[0] = ff
configbuf[1] = 3   cfgcomp[1] = 3
configbuf[2] = 3f   cfgcomp[2] = 3f
configbuf[3] = 0   cfgcomp[3] = 0
configbuf[4] = 3f   cfgcomp[4] = 3f
configbuf[5] = 1   cfgcomp[5] = 1
configbuf[6] = 3f   cfgcomp[6] = 3f
configbuf[7] = 7   cfgcomp[7] = 7
configbuf[8] = 3f   cfgcomp[8] = 3f
configbuf[9] = 7   cfgcomp[9] = 7
configbuf[10] = 0   cfgcomp[10] = 0
configbuf[11] = 2   cfgcomp[11] = 2
configbuf[12] = 3   cfgcomp[12] = 3
configbuf[13] = 0   cfgcomp[13] = 0
configbuf[14] = ff   cfgcomp[14] = ff

So I split the 27 bytes to 12 bytes and 15 bytes, then write and read successfully.

Thanks,

Liza

0 Vidar Berg 6 months ago in reply to Liza

Hi Liza,

You may get more information about why the write failed by enabling CONFIG_LOG to get the logs from the nrfx I2C driver. The TWIM hardware supports sending up to 4096 bytes, but the data may be NACKed by the slave, which will cause the write transaction to be aborted. From the datasheet it seems that the LDC_REG_CHAN_EN register is only 1 byte.

Best regards,

Vidar
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Liza 6 months ago in reply to Vidar Berg

Hi Vidar,

Thanks for your information. I will try CONFIG_LOG.

I made a typo. I write 27 bytes from LDC_REG_CHAN_EN(0x0c) to LDC_REG_SENSOR3_CONFIG(0x26).

Thanks,

Liza
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Vidar Berg 6 months ago in reply to Liza

Hi Liza,

But why 27 bytes? Isn't the register only 1 byte, or am I missing something?

Best regards,

Vidar
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Liza 6 months ago in reply to Vidar Berg

Hi Vidar,

It is 1 byte write to 0x0c, 1 byte write to 0x0d, 1 byte write to 0x0e and so on. Totally 27 bytes write to 27 addresses (0x0c to 0x26).

uint8_t configbuf[]={ 0xFF, 0x03, 0x3F, 0x00, //0x0C ~0x0F
0x3F, 0x01, 0x3F, 0x07, 0x3F, 0x07, 0x00, 0x02, //0x10 ~0x17
0x03, 0x00, 0xff, 0x00, 0xFF, 0x00, 0x00, 0x00, //0x18 ~0x1F
0xA7, 0x00, 0xA7, 0x00, 0xA7, 0x00, 0xA7}; //0x20 ~0x26

Thanks,

Liza
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Liza 6 months ago in reply to Vidar Berg

Hi Vidar,

It is 1 byte write to 0x0c, 1 byte write to 0x0d, 1 byte write to 0x0e and so on. Totally 27 bytes write to 27 addresses (0x0c to 0x26).

uint8_t configbuf[]={ 0xFF, 0x03, 0x3F, 0x00, //0x0C ~0x0F
0x3F, 0x01, 0x3F, 0x07, 0x3F, 0x07, 0x00, 0x02, //0x10 ~0x17
0x03, 0x00, 0xff, 0x00, 0xFF, 0x00, 0x00, 0x00, //0x18 ~0x1F
0xA7, 0x00, 0xA7, 0x00, 0xA7, 0x00, 0xA7}; //0x20 ~0x26

Thanks,

Liza
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

0 Vidar Berg 6 months ago in reply to Liza

Hi Liza,

I see. Thanks for the clarification. Let me know if you get any error messages from the nrfx driver.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel