Using LIS3dh with Thingy52

RE: Using LIS3dh with Thingy52

willemvde — Tue, 18 Jan 2022 17:57:38 GMT

The following code reads the whoAmI value from the lis2dh12 sensor inside the thingy52. I'm just leaving it here for people who are having the same trouble as me in the future.

Greetings

Willem

#include <stdio.h>
#include "boards.h"
#include "app_util_platform.h"
#include "app_error.h"
#include "nrf_drv_twi.h"
#include "nrf_delay.h"


#include "nrf_log.h"
#include "nrf_log_ctrl.h"
#include "nrf_log_default_backends.h"

#include "lis2dh12.h"

#include "nrf_twi_mngr.h"

/* TWI instance ID. */
#define TWI_INSTANCE_ID             0

#define MAX_PENDING_TRANSACTIONS    33

#define LIS2DH12_MIN_QUEUE_SIZE     32

NRF_TWI_MNGR_DEF(m_nrf_twi_mngr, MAX_PENDING_TRANSACTIONS, TWI_INSTANCE_ID);

NRF_TWI_SENSOR_DEF(m_nrf_twi_sensor, &m_nrf_twi_mngr, LIS2DH12_MIN_QUEUE_SIZE);

LIS2DH12_INSTANCE_DEF(m_lis2dh12, &m_nrf_twi_sensor, LIS2DH12_BASE_ADDRESS_HIGH);

static uint8_t m_sample = 0;

void print_identity(ret_code_t r, void *p_register_data)
{
    NRF_LOG_INFO("Identity: %d", *((uint8_t *)p_register_data));
}

/**
 * @brief Function for main application entry.
 */
int main(void)
{
    uint32_t err;

    nrf_drv_twi_config_t const config = {
       .scl                = 15,
       .sda                = 14,
       .frequency          = NRF_DRV_TWI_FREQ_100K,
       .interrupt_priority = APP_IRQ_PRIORITY_LOWEST,
       .clear_bus_init     = false
    };


    APP_ERROR_CHECK(NRF_LOG_INIT(NULL));
    NRF_LOG_DEFAULT_BACKENDS_INIT();

    NRF_LOG_INFO("TWI sensor example started.");
    NRF_LOG_FLUSH();

    err = nrf_twi_mngr_init(&m_nrf_twi_mngr, &config);
    APP_ERROR_CHECK(err);

    err = nrf_twi_sensor_init(&m_nrf_twi_sensor);
    APP_ERROR_CHECK(err);

    err = lis2dh12_init(&m_lis2dh12);
    APP_ERROR_CHECK(err);

    NRF_LOG_INFO("Here.");
    NRF_LOG_FLUSH();
    APP_ERROR_CHECK(err);

    while (true)
    {
        nrf_delay_ms(100);
        err = lis2dh12_who_am_i_read(&m_lis2dh12, print_identity, &m_sample);
        APP_ERROR_CHECK(err);
        NRF_LOG_INFO("Who am I: %x", m_sample);
        NRF_LOG_FLUSH();
    }
}

RE: Using LIS3dh with Thingy52

Sigurd Hellesvik — Thu, 23 Dec 2021 14:24:46 GMT

When I was searching for drivers before, I was looking for LIS3DH.
However, I just found that LIS2DH drivers are compatible(ref) with the LIS3DH.

In the nRF Connect SDK, there is a LIS2DH: Motion Sensor Monitor sample.

In the nRF 5 SDK, there is a driver for the LIS2DH as well, see this previous case.

I am sorry that I did not spot this compatibility earlier. I hope that this could still be of some use.

Regards,
Sigurd Hellesvik

RE: Using LIS3dh with Thingy52

willemvde — Tue, 14 Dec 2021 14:28:14 GMT

Thanks for making those 2 different SDKs clear for me. There is no time to switch SDK now, but I will keep this in mind when I'm starting a new BLE project.

For now, I'll keep trying to make the 'old' SDK work with the Thiingy. I'm making some progress so I'm hopeful.

Greetings

Willem

RE: Using LIS3dh with Thingy52

Sigurd Hellesvik — Tue, 14 Dec 2021 13:20:38 GMT

Hi Willem,

See Using the SDK with other boards and our GitHub for Thingy 52 header file.

Side note:
We have two different SDKs. The old nRF5 SDK, which you are using, and the newer nRF Connect SDK. See this nRF Connect SDK and nRF5 SDK statement for more information on the difference.
Personally, I think development for the Thingy:52 would be easier on the nRF Connect SDK, as it has integrated support for the Thingy:52.

Switching SDK would mean you have to learn the new one, and rewrite any code you have already made. So depending on how much time this would take, it could or could not be worth it. Up to you really, but now you know your alternatives.

Regards,
Sigurd Hellesvik

RE: Using LIS3dh with Thingy52

willemvde — Tue, 14 Dec 2021 10:29:35 GMT

Those standard drivers look very handy!

Thanks

RE: Using LIS3dh with Thingy52

willemvde — Tue, 14 Dec 2021 10:28:56 GMT

Hi Sigurd

This would help if I hadn't stumbled upon another problem. Namely, flashing the Thingy. I tried using the pca10040 and pca10056 Makefiles from an example, but it seems that the Thingy uses pca20020. I couldn't find a working Makefile online and making one by myself seems difficult.

Any suggestions on how to do this?

If what I'm trying isn't possible, I'll have to find an external accelerometer and use it on my nrf52840 devkit.

Greetings

Willem

RE: Using LIS3dh with Thingy52

Sigurd Hellesvik — Fri, 10 Dec 2021 08:06:48 GMT

Hi Willem,

For documentation for the Thingy:52, we got most of our documentation on our Infocenter. See this page for Thingy:52. And for the connectors of the Thingy:52, see Thnigy:52 Connectors.

Some extra useful information can be found at the Thingy:52 Product page: Downloads, such as Hardware files, where you can find a pdf containing all block diagrams for the Thingy. This is often useful for finding pinouts as well.

[quote user=""]I couldn't find any drivers for the LIS3dh that work on Thingies. That means I have to use SPI or I²C? [/quote]

If the sensor is interfaced using either SPI or I2C, it will always have to be interfaced using that communication protocol. Which communication protocol is up to the sensor, see the datasheet for each sensor to find how it can be interfaced.

A driver for a sensor is premade code that will use said interface for the sensor.
If you can not find any premade drivers for the sensor, you will have to write your own code to interface the sensor (using for example SPI). This would be called writing a custom driver for said sensor.

Did this answer your questions?

Regards,
Sigurd Hellesvik

RE: Using LIS3dh with Thingy52

AbhaySingh — Thu, 09 Dec 2021 17:14:34 GMT

Hi willemvde,

You can find driver for lis3dh and few example code from the below link.

https://github.com/STMicroelectronics/STMems_Standard_C_drivers

And then , you just have to write your own, plateform_write and plateform_read function.