BMA-456 Understanding interrupt status retention after wake-up.

[DalesLandnet]

We are using the BMA456 in a ground based sensor. The sensor spends most of the time asleep consuming as little power as possible. Once every hour it wakes from deep sleep  makes some readings and  sends them  using LoRaWan protocol. We are using the BMA456 interrupt to wake up the sensor on an "Any Movement" interrupt. We are also looking  to use the double tap interrupt to wake the sensor on demand to allow us to use service tools.

Currently when we wake from deepsleep (ESP32) it performs a "warm" reset, when this occurs  we are reinitialising the BMA456 including  reloading the configuration file. We are currently using  BMA456MM feature set.

1. When should the the configuration file be reloaded?
2. Is there a way to read status of the BMA456 to know if there is a valid configuration file stored?
3. At what point does the interrupt state become reset not including reading the status?

[BSTRobin]

Hi DalesLandnet ,

Thank for your inquiry.
BMA456 also supports any motion and double tap features in low-power mode without the need to reload firmware. When any motion or double tap events occur, the sensor will report an interrupt signal to the host to wake it up. Then the host read the interrupt status register of BMA456 to check which type of interrupt trigger (any motion, double tap, etc.) it is.