Skip to main content
Associate III
October 30, 2025
Solved

Regarding the Startup Confirmation of ASM330LHH

  • October 30, 2025
  • 1 reply
  • 174 views

Could you please let me know at what point we can confirm that the ASM330LHH has successfully started up at the hardware level?
If the WHO_AM_I register returns the expected response, can we consider that the device has initialized correctly?

Additionally, after enabling the sensors via CTRL1_XL and CTRL2_G, is it possible to verify proper startup by checking whether the value of STATUS_REG changes?
In a situation where the STATUS_REG value sometimes changes and sometimes does not, is it appropriate to judge that “no change” indicates the hardware has not successfully started?

Thank you very much for your guidance.

Best answer by Federica Bossi

Hi @ggob ,

Yes, reading the WHO_AM_I register and receiving the expected fixed device ID is the primary indication that the device is responding correctly at the hardware level and communication is established.

The STATUS_REG bits indicate the availability of new data for accelerometer and gyroscope, after enabling accelerometer and gyroscope by writing to CTRL1_XL and CTRL2_G, you should expect the STATUS_REG bits to change as new sensor data becomes available.

No change in STATUS_REG over a reasonable time period (considering configured ODR) may indicate the sensor is not producing data, possibly due to incomplete startup or configuration issues.

1 reply

Federica Bossi
Federica BossiBest answer
Technical Moderator
October 30, 2025

Hi @ggob ,

Yes, reading the WHO_AM_I register and receiving the expected fixed device ID is the primary indication that the device is responding correctly at the hardware level and communication is established.

The STATUS_REG bits indicate the availability of new data for accelerometer and gyroscope, after enabling accelerometer and gyroscope by writing to CTRL1_XL and CTRL2_G, you should expect the STATUS_REG bits to change as new sensor data becomes available.

No change in STATUS_REG over a reasonable time period (considering configured ODR) may indicate the sensor is not producing data, possibly due to incomplete startup or configuration issues.

In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.