I’m experiencing some weird behavior I’d like to hear if anyone else has come across…
I have I2C-1 configured to run at 100KHz and I have an SHT-21 on the bus with address 0x40 and I have the R24 kernel driver loaded for this device (it also registers and finds the chip)
The weirdness is that for some unknown reason the two data bytes which comes after the clock stretching is “garbled” and always reads close to zero.
See image below (sorry for the bad paint job in merging the photo - see attached file jetson_stretching for better resolution)
The oddity is that the SHT21 (Si7021 is what I’m using that is pin/function compatible) returns 0x00 and 0x20 as data bytes which is an illegal combination.
If I remove the Jetson module from my carrier board and attach an I2C debugger to the carrier and perform a read again I get a correct response:
I do not have other I2C devices on my bus than the Si7021 (SHT21) when testing both scenarios which leads me to believe there’s something fishy going on with the Jetson as the I2C debugger can read the chip just fine.
Has anyone seen anything like this before?