Hi Sparkfun
I ordered the AS7265x triad about a month ago and played with it over the holiday. I am moderately certain I am looking at a a hardware issue, but I want to be sure I’m not missing something. I’ve been trying many iterations to characterize what I see.
I am using a RPi4 with a Quik jumper cable. When I connect the sensor, the red LED consistently (100%) turns on. However, the status LED is almost never enabled (~5%). This is completely consistent with what I see when I probe via i2cdetect. If the blue LED isn’t present, then i2cdetect doesn’t show anything at all.
When the blue LED does turn on, the device can be seen by i2cdetect. When this happens, I get to the second set of problems:
The Device Status does NOT aways return 48 (slave 1 & slave 2 devices are present). I sometimes get 48, in which case I can continue just fine. There are also times that I get a non-48, but after a softReset or two, I get a 48. (This isn’t something I should have to do, but I’m trying to characterize). If I try to work with the device with a non-48 code, then I see what I would expect:
Basic commands, like extracting the hardware/firmware versions, work just fine. While operations that involve ‘device select’ (getting temperature, raw or calibrated readings) don’t work quite as expected: I get the same reading from U_J_D, regardless of the device I’ve selected.
In the rare times that the device boots up properly (blue LED + 48 for slave health), I see reasonable results, although I have caught duplication when reading raw/calibrated registers (e.g. U == J == D when looking at a light source)
To recap:
-
Blue status LED rarely on (~5% of boots), which is consistent with i2cdetect from the host device
-
When blue status LED is on, the slave status read isn’t showing the expected value (48) the vast majority of the time, although repeated software resets sometimes clear this.
-
When the status LED and slave status do work, the board usually operates as I expect, although I see occasional duplication (e.g. U==J==D when looking at a light source where I know U != J != D)
-
Other I2c devices work just fine with the hardware.
-
The same problem occurs (no blue LED) if I plug the board into another pi.
At this point, I would like to continue experimenting with the board, but I can’t reboot 50x in hope of getting the indicator LED to come up. I want to make sure I’m not missing something obvious before I ask for a replacement.
