Runing LIS2DH12 on custom hardware

RE: Runing LIS2DH12 on custom hardware

HSPalm — Mon, 12 Aug 2024 08:30:11 GMT

Hi Kazi, thanks for your reply and sorry for my late feedback. I eventually solved this by resetting the device in main() if the sensor init fails. Because then the pins retain their value for the next boot cycle(?). Also it was an issue that that with high capacitance and long rise times on VDD pin driven by GPIO, so the timing of VDD andf other GPIO assertion was messed up.

RE: Runing LIS2DH12 on custom hardware

Kazi Afroza Sultana — Thu, 01 Aug 2024 08:12:52 GMT

Hello,

You can try to measure the i2c pins on a logic analyzer or oscilloscope.

RE: Runing LIS2DH12 on custom hardware

HSPalm — Fri, 26 Jul 2024 20:58:03 GMT

I used the shell command "device list" and LIS2DH shows as DISABLED, any idea why?

Edit: Also adding that an I2C scan resulted in 0 found devices

RE: Runing LIS2DH12 on custom hardware

HSPalm — Fri, 26 Jul 2024 19:58:39 GMT

Hi Kazi,
Thank you for replying.

On my custom hardware there is only this sensor, one button (P0.31) and RGB LED (P0.28-30) connected to GPIO pins. Other than that of course decoupling, power supply, antenna, crystals etc.

Very sorry for all the threads. I initially thought my problems were related to different things but wound up preceeding on the development while still having open tickets. My past two threads are somewhat related so I hope to keep them open until I have this problem figured out.

RE: Runing LIS2DH12 on custom hardware

Kazi Afroza Sultana — Fri, 26 Jul 2024 10:59:15 GMT

Hello,

The error shoes that application can not connect to the sensor. There could be several reasons for that. Have you checked that pins are not overlapping with other peripherals?

In our default board (nRF52dk_nrf52810) Pin 0.05 is for RTS and pin P0.06 is for TX.

You have several tickets for same problem. It is convenient and easy to follow if you stick on one ticket.