Interfacing IMU Sensor (LSM6DSL) with SPI

RE: Interfacing IMU Sensor (LSM6DSL) with SPI

rania amara — Wed, 01 May 2024 12:06:30 GMT

hi i'm trying to do the same thing "interfacing imu sensor(lsm6dso) with i2c and i dont know how to set the right overlay file ,can you help me ?

RE: Interfacing IMU Sensor (LSM6DSL) with SPI

Mindtech — Wed, 31 May 2023 12:17:51 GMT

Yes, i got the following answer

"<err> spi_nrfx_spim: Timeout waiting for transfer complete"

I will try to see the signals with a logic analyzer

RE: Interfacing IMU Sensor (LSM6DSL) with SPI

stc114533 — Tue, 30 May 2023 20:03:19 GMT

Have you tried printing the log messages? What did you get?

RE: Interfacing IMU Sensor (LSM6DSL) with SPI

Mindtech — Mon, 29 May 2023 14:59:41 GMT

Thanks, it's very similar to my device tree... I believe I'm missing some other detail.

RE: Interfacing IMU Sensor (LSM6DSL) with SPI

stc114533 — Mon, 29 May 2023 12:48:57 GMT

Sorry for the late reply.

This is everything I have for spi3, hope that helps.

&pinctrl {
    spi3_default: spi3_default {
        group1 {
            psels = <NRF_PSEL(SPIM_SCK, 0, 3)>,
                    <NRF_PSEL(SPIM_MISO, 0, 5)>,
                    <NRF_PSEL(SPIM_MOSI, 0, 4)>;
        };
    };
    spi3_sleep: spi3_sleep {
        group1 {
            psels = <NRF_PSEL(SPIM_SCK, 0, 3)>,
                    <NRF_PSEL(SPIM_MISO, 0, 5)>,
                    <NRF_PSEL(SPIM_MOSI, 0, 4)>;
        };
    };
};


st_lsm6dsl: &spi3 {
    compatible = "nordic,nrf-spim";
    status = "okay";
    pinctrl-0 = <&spi3_default>;
    pinctrl-1 = <&spi3_sleep>;
    pinctrl-names = "default", "sleep";
    cs-gpios = <&gpio0 8 GPIO_ACTIVE_LOW>;
    lsm6dsl: lsm6dsl@0 {
        compatible = "st,lsm6dsl";
        status = "okay";
        spi-max-frequency = <10000000>;
        reg = <0>;
        irq-gpios = <&gpio0 9 0>;
    };
};

RE: Interfacing IMU Sensor (LSM6DSL) with SPI

Mindtech — Fri, 26 May 2023 17:22:22 GMT

I have the same problem you described, but with the nRF9160, could you share your complete device tree overlay?

RE: Interfacing IMU Sensor (LSM6DSL) with SPI

stc114533 — Tue, 09 May 2023 17:03:56 GMT

So I printed out the log messages, found that it's because I didn't set the irq-gpios in overlay. Now everything works as expected.

st_lsm6dsl: &spi3 {

compatible = "nordic,nrf-spim";

status = "okay";

pinctrl-0 = <&spi3_default>;

pinctrl-1 = <&spi3_sleep>;

pinctrl-names = "default", "sleep";

cs-gpios = <&gpio0 8 GPIO_ACTIVE_LOW>;

lsm6dsl: lsm6dsl@0 {

compatible = "st,lsm6dsl";

status = "okay";

spi-max-frequency = <10000000>;

reg = <0>;

irq-gpios = <&gpio0 9 0>;

};

RE: Interfacing IMU Sensor (LSM6DSL) with SPI

stc114533 — Fri, 05 May 2023 20:31:09 GMT

Have you solved it? I also did the same thing as you did and I encountered the same problem, it'd be great if you can guide me to make it work. I'm also using the sample code, so it's probably my overlay that causes this issue.

RE: Interfacing IMU Sensor (LSM6DSL) with SPI

nordicator_prim3 — Thu, 16 Mar 2023 16:33:36 GMT

OK,

The only other thing I can think of is changing the frequency. The data sheet says the minimum spi clock time is 100ns (10MHz). In your overlay, it is set to only 100KHz. Try changing it to "spi-max-frequency =<10000000>;".

RE: Interfacing IMU Sensor (LSM6DSL) with SPI

Thanuha — Thu, 16 Mar 2023 16:03:03 GMT

that is already there in the example code i am not changing in the example code i am just adding the overlay file which I shared above

RE: Interfacing IMU Sensor (LSM6DSL) with SPI

nordicator_prim3 — Thu, 16 Mar 2023 15:33:55 GMT

There are only a few things that would cause this. Either the initialization function in the driver for LSM6DSL is failing (it would print an error) or the device information can not be found in the device tree.

Looking at the driver in "..\ncs\v2.0.0\zephyr\drivers\sensor\lsm6dsl\lsm6dsl.c", if the initialization fails you will see one of two possible errors:

1. LOG_ERR("Failed to initialize sensor bus");

2. LOG_ERR("Failed to initialize chip");

So if you have logging enabled and odn't see either of these errors then the driver can't find the device information from the device tree. How are you getting the variable "lsm6dsl_dev"?