we're using LSM6DSOTR and communicating that with I2C and it working as expected but sometimes we suddenly see some issues and they are unpredictably happening at any moment of time. there are mainly two issues that we have seen till now.

[MDarj.1]

we're using LSM6DSOTR and communicating that with I2C and it working as expected but sometimes we suddenly see some issues and they are unpredictably happening at any moment of time.

there are mainly two issues that we have seen till now and that are listed below:

1. when we try to read WHOAMI register, the value needed to be returned is 0x6C (as per datasheet) but we're getting 0x00 and when we try reading value for X,Y,Z registers, it returns a fixed value and never changes even after moving vigorously. We also enabled tap interrupt and we're seeing that being detected, but XYZ values are not changing.
2. In second scenario it's mostly similar to first except in this we're not able to detect the interrupt as well.

These issues we have not seen previously but now, we have other peripherals also on the same I2C bus and they are responding correctly. So we're wondering what could be the cause for this and how we can resolve this issue

[Eleon BORLINI]

Hi @MDarj.1​ ,

There are some problems on the I2C communication for sure.

I'm wondering if it could be related to an hardware issue, i.e. to some interferences on the I2C lines.

Are you using a custom design? If so, did you follow the recommendation that you can find in the datasheet, p. 35?

 

Also, do you have the possibility to test another part? Maybe the one currently under test was damaged during the operation (you might check it by measuring its current consumption).

-Eleon

[Eleon BORLINI]

Hi @MDarj.1​ ,

any update about this issue?

-Eleon

[MDarj.1]

Hi Eleon Borlini

Thanks for your reply. I will update for this.

Wait for my response/update.

Regards

Minesh