Hello!
I'm hoping to understand what might cause a timeout on register 0x83. I understand 0x83 is a lock/unlock style register. During configuration, we run VL53L0X_get_info_from_device(Dev, 1) function to get SPAD information. This function appears to call another function called VL53L0X_device_read_strobe(VL53L0X_DEV Dev). The read strobe function tries to write 0x00 data to 0x83 register, then enters a timed polling loop, waiting until 0x83 register reflects 0x00 data. The function may time out if 0x83 register never reports 0x00 data.
My question is why can 0x83 register time out?
I don't think we have ever seen this behavior in years of use of the sensor. If we create a custom implementation of the API, is it necessary to be checking this 0x83 register to see writes go through? Why aren't other registers checked after writes?
If a sensor is experiencing this time out, what other behavior might be impacted? Does I2C communication still function?
Any help on the above questions would be much appreciated!
