cancel
Showing results for 
Search instead for 
Did you mean: 

i2cdetect disrupts VL53L8CX operation, causing GO2 error

Voklaif
Associate

Hello,

I am using the VL53L8CX sensor on an I2C bus, and it operates normally until I run the i2cdetect command. After running i2cdetect, the sensor stops working properly, and calling vl53l8cx_check_data_ready() returns a GO2 error status.

Interestingly, if I have another sensor (e.g., a temperature sensor) enabled on the same I2C bus, the VL53L8CX recovers and continues working after i2cdetect. The temperature sensor is at a different address and only performs normal read operations.

  • Why does i2cdetect disrupt VL53L8CX?
  • Why does another sensor’s read operations seem to "fix" the issue?
  • How can I debug and prevent this problem without adding a secondary sensor?

Any insights or debugging tips would be greatly appreciated!

Thanks!

0 REPLIES 0