VL53L0X_get_info_from_device（）中收到超时错误

我把它追逐到了一个叫做“频闪”的东西。它将0写入寄存器0x83并期望返回非零。然后当它变为非零时，它会写入1.我不知道这个寄存器是什么，也不知道它应该做什么，但它显然没有做它应该做的事情。
 
 
 您可以在文件vl53l0x_api_core.c中看到这一点，函数VL53L0X_device_read_strobe（）。
 
 嗯......不管它是否超时，我想它会写一个1。主要问题是为什么它超时？



以下为原文





I have chased it down to something called ''strobe''.  It writes a zero to register 0x83 and expects non-zero back.  Then when it gets non-zero back it writes a 1.  I have no idea what this register is, nor what it is supposed to do, but it obviously isn't doing what it is supposed to do.  


You can see this in file vl53l0x_api_core.c, function VL53L0X_device_read_strobe().

Hmmm.... I guess it writes a 1 no matter if it times out or not.  The main question is why is it timing out?

好的，所以我的实际问题是WrByte（）例程实际上并没有正确地通过i2c发送数据。现在它确实如此，我已经解决了这个问题，并且遇到了测距错误。但至少该设备不再悬挂。
 
 
 对ST说：请发布注册地图!!!



以下为原文





OK, so my actual problem was the WrByte() routine was not actually sending data correctly over the i2c.  Now it does, and I am past this problem and onto a ranging error.  But at least the device is no longer hanging.


And a word to ST: please publish a register map!!!

我有5个单位，我可以插入我的Pi。其中3个给出了浮点错误，其中2个给出了范围错误错误。我决定追逐浮点错误并在常规calc_macro_period_ps（）中找到除以零，因为0作为参数发送。通过重新排序在VL53L0X_perform_ref_spad_management（）之前发生的初始化值（并通过设置
 
 而不是没有值，具有浮点错误的3个单元现在实际上正在读取范围数据。现在，我所要做的就是找到一种方法来通过写入默认的内部值来修复损坏的单位，他们也可以做一些有用的事情。
 
 这仍然令人沮丧，因为我不知道ANYTHING的正确值应该是什么，也不知道为什么它们应该是那样。
 麦克风



以下为原文





I have 5 units I can plug into my Pi.  3 of them gave floating point errors, and 2 of them give the range fault error.  I decided to chase down the floating point error and found a divide by zero in routine calc_macro_period_ps() because 0 was sent in as a parameter.  By reordering the initialization values to occur before VL53L0X_perform_ref_spad_management() (and by setting

• uint8_t vcselPulsePeriodPCLK = 14;
  

• FixPoint1616_t seqTimeoutMilliSecs = 5;
  

instead of having no value, the 3 units which had floating point errors are now actually reading back range data.  Now, all I have to do is find a way to fix the broken units by writing over their default internal values and they might do something useful as well.

This is still frustrating though because I have no idea what the correct values for ANYTHING should be, nor why they should be that way.
Mike

以下为原文