nrf_drv_twi_rx error 3

Hi Willem

Since this is a public post, I would just like to remind future other readers of this forum that our nRF Connect SDK has a sample for the LIS2DH: Motion Sensor Monitor, which is compatible with the LIS3DH.

However, you told me last time that you cannot switch to the nRF Connect SDK, so let us continue to work with the nRF5 SDK here.

Where do is the function "lis3dh_device_id_get" defined?

Is your LIS3DH sensor an external sensor?
If so, how is it connected? Are the SCL and SDA lines pulled up?

Regards,
Sigurd Hellesvik

Hi Sigurd!

lis3dh_device_id_get is defined in the driver template: https://github.com/STMicroelectronics/lis3dh/blob/6a82fc90cfb688686d0b344c82184c33ee844697/lis3dh_reg.c#:~:text=int32_t%20lis3dh_device_id_get(stmdev_ctx_t%20*ctx%2C%20uint8_t%20*buff)

It eventually uses the "platform_read" function which I had to write myself. In this function, I just call "nrf_drv_twi_rx". That one returns the 3 error. 

The LIS3DH sensor is internal on the Thingy:52. I assume this means I don't have to worry about pulling up the SCL and SDA since I'm using the twi functions from the SDK? 

I saw your suggestion of using the LIS2DH driver which exists for the nRF5 SDK. I will definitely take a look at this, but regardless, I'd like to know what I'm doing wrong here so I can learn from my mistakes. 

Greetings

Willem

Hi

In our documentation, it looks like the Thingy:52 use a LIS2DH12:

Here, you also see that SA0 is connected to VREG (High).
I see that you use ADD_L, which would be if SA0 is connected to Ground (Low).

The address of the sensor is also in the documentation I linked, so make sure this is matches what you use in your driver.

Does this help you fix the issue?

Regards,
Sigurd Hellesvik

Hi

That could be the problem... 

I probably jumped on the LIS3DH because this is what is used in the Thingy52 SDK: https://github.com/NordicSemiconductor/Nordic-Thingy52-FW/blob/126120108879d5bf5d202c9d5cab65e4e9041f58/source/drivers/drv_acc_lis3dh.c

I tried replacing my STMicroelectronics driver with their LIS2DH12 one, but this didn't change anything about the error. I will try out the Nordic driver for the LIS2DH12 later. 

Happy holidays btw! :)

Willem