On Fri, May 12, 2017 at 9:44 AM, Graham Haddock <[email protected]> wrote:
> I take back what I said about a non standard read sequence. I re-read the > data sheet, and they describe a standard concatenated write/read sequence > for a single byte read. But I do note that they do not describe a simple > read only sequence, where the part would start reading from the last > register position. > Yeap, that's standard I2C comms, I knew that, but kept my mouth shut. Also for what it's worth, smbus I2C is the preferred I2C comms method in Linux. But it's not impossible to use the older protocol. > > A lot of the tools do not actually do the concatenated write/read, but > instead do a separate write-stop, read-stop. I have not seen a I2C part > that would not accept this. > > Do you have another "trusted" I2C device you could parallel across the bus > as a test device? > I use an MCP9808 temperature sensor on most of my boards when bringing up > a new design. > > Or as suggested by David, put a bus analyzer on the bus to see if the chip > is not sending good data, or the Beaglebone is loosing the good data when > the chip sends it. > > --- Graham > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORpdrYw9TaE%2BOC_9mEWvrv%2BiEXKY1Yh0c%3DUVeEXgjZcvqA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
