How do I extra the gpio phandle form a lis3dh device to the C code?

RE: How do I extra the gpio phandle form a lis3dh device to the C code?

runsiv — Fri, 26 Apr 2024 06:43:34 GMT

I wonder if it might not be the intellisense giving a false positive. I have seen it reported with the same driver before on devzone. I did acutally get the same warning yesterday with the following config.

//prj.conf
CONFIG_I2C=y
CONFIG_SENSOR=y
CONFIG_LIS2DH=y
CONFIG_LIS2DH_TRIGGER_GLOBAL_THREAD=y

//devicetree
&i2c1 {
    compatible = "nordic,nrf-twim";
    status = "okay";
    lis3dh: lis3dh@18 {
        compatible = "st,lis2dh","st,lis2dh12", "st,lis3dh" ;
        status = "okay";
        reg = <0x18>;
        irq-gpios = <&gpio0 2 GPIO_ACTIVE_HIGH>,<&gpio1 15 GPIO_ACTIVE_HIGH>;
        disconnect-sdo-sa0-pull-up;
    };
};
 
/{
    aliases {
        accel0 = &lis3dh;
    };
};

But when I started VScode today it gave me no warning. I would recommend checking if the sensor is included in the generated devicetree with status okay

Regards

Runar

RE: How do I extra the gpio phandle form a lis3dh device to the C code?

J0sh1101 — Thu, 25 Apr 2024 13:57:19 GMT

I do not get any errors, but I get a warning saying that it cannot enabled:

-- Including generated dts.cmake file: C:/nordic_play_workfolder/LIS3DH/build_nrf52840_dk/zephyr/dts.cmake

warning: LIS2DH (defined at drivers/sensor/lis2dh/Kconfig:6) was assigned the value 'y' but got the
value 'n'. Check these unsatisfied dependencies: DT_HAS_ST_LIS2DH_ENABLED (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_LIS2DH and/or look up LIS2DH in the
menuconfig/guiconfig interface. The Application Development Primer, Setting Configuration Values,
and Kconfig - Tips and Best Practices sections of the manual might be helpful too.

RE: How do I extra the gpio phandle form a lis3dh device to the C code?

runsiv — Thu, 25 Apr 2024 13:00:32 GMT

Do you get any error when you try to a pristine build?

I have seen in the past doing a pristine build or deleting the build folder might help.

You can also check if it is included in the generated .dts with status okey.

Regards

Runar

RE: How do I extra the gpio phandle form a lis3dh device to the C code?

J0sh1101 — Thu, 25 Apr 2024 12:09:17 GMT

Hello,

Unfortunately it did not make any difference. I got that it could not set the CONFIG_LIS2DH:

Do you know why is this happening?

RE: How do I extra the gpio phandle form a lis3dh device to the C code?

runsiv — Wed, 24 Apr 2024 11:21:02 GMT

Could you try adding the following Kconfig options

CONFIG_SENSOR=y

CONFIG_LIS2DH=y

CONFIG_LIS3DH is not a thing so you would need to use LIS2DH. It might also be that you need to set compatible to

"st,lis3dh", "st,lis2dh";

Regards

Runar

RE: How do I extra the gpio phandle form a lis3dh device to the C code?

runsiv — Tue, 23 Apr 2024 13:52:38 GMT

Thanks for the new info. I will need to get back to you tomorrow after looking a bit more into it. However from what I can see you have not enabled the sensor in your prj.conf, try adding CONFIG_LIS3DH=y

We have a lesson covering writing custom drivers here which might be helpful

Regards

Runar

RE: How do I extra the gpio phandle form a lis3dh device to the C code?

J0sh1101 — Tue, 23 Apr 2024 13:29:49 GMT

[quote userid="122502" url="~/f/nordic-q-a/110469/how-do-i-extra-the-gpio-phandle-form-a-lis3dh-device-to-the-c-code/480136"]Which version of NCS are you using? [/quote]

I am using the nRF Connect SDK v2.6.

[quote userid="122502" url="~/f/nordic-q-a/110469/how-do-i-extra-the-gpio-phandle-form-a-lis3dh-device-to-the-c-code/480136"]If you remove the line "const struct gpio_dt_spec int1 = DT_GPIO_CTLR_BY_IDX(I2C1_NODE, irq_gpios, 0);" does it build then?[/quote]

Yes, then it builds. I can extract the data and saved to 2c_dt_spec:

[quote userid="122502" url="~/f/nordic-q-a/110469/how-do-i-extra-the-gpio-phandle-form-a-lis3dh-device-to-the-c-code/480136"]Could you post your prj.conf?[/quote]

ofc, here is the prj.conf:

# Logger module
CONFIG_LOG=y
CONFIG_LOG_MODE_MINIMAL=y


CONFIG_NEWLIB_LIBC=y
CONFIG_CBPRINTF_FP_SUPPORT=y
CONFIG_NEWLIB_LIBC_FLOAT_PRINTF=y



# Button and LED library
CONFIG_DK_LIBRARY=y
CONFIG_BOOT_BANNER=n
CONFIG_I2C=y

[quote userid="122502" url="~/f/nordic-q-a/110469/how-do-i-extra-the-gpio-phandle-form-a-lis3dh-device-to-the-c-code/480136"] I presume your case is somewhat the same as this case[/quote]

Maybe a little. I am trying to write my own driver and he is trying to use the existing driver which I have given up. The interface of the driver is far too complex to just write a few registers and is not intuitive.

[quote userid="122502" url="~/f/nordic-q-a/110469/how-do-i-extra-the-gpio-phandle-form-a-lis3dh-device-to-the-c-code/480136"]Have you verfied that your address is correct according to your setup?[/quote]

Which address are we talking about?

I talked to someone who knows more about the device tree than I do and he said that the problem is the macro function "DT_NODELABEL(mysensor)" and not DT_GPIO_CTLR_BY_IDX() as I thought at first. This is strange because the macro function I2C_DT_SPEC_GET() works perfectly with DT_NODELABEL(), but DT_NODELABEL does not work with DT_GPIO_CTLR_BY_IDX. DT_NODE_LABEL uses the concatenation to create a define which can be found in devicetree_generated.h. In my case it is DT_N_S_soc_S_i2c_40003000_S_mysensor_18_P_irq_gpios_IDX_0_PH. The problem seems to be that it cannot find the define of DT_N_S_soc_S_gpio_50000000. (Now, the error message makes more sense.) At this point I do not understand why the DT_N_S_soc_S_gpio_50000000 is not created.

Do you know anything more about this?

(This device tree is really a hell.)

RE: How do I extra the gpio phandle form a lis3dh device to the C code?

runsiv — Tue, 23 Apr 2024 08:38:36 GMT

Which version of NCS are you using? Have you verfied that your address is correct according to your setup?

The pinconfig looks correct to me so the overlay should be good. If you remove the line "const struct gpio_dt_spec int1 = DT_GPIO_CTLR_BY_IDX(I2C1_NODE, irq_gpios, 0);" does it build then? I presume your case is somewhat the same as this case

Could you post your prj.conf?

Regards

Runar