09-29-2016, 12:04 AM
(This post was last modified: 09-29-2016, 12:05 AM by MarkHaysHarris777.)
The first step is to use the i2c toolset to see if you can see your device address. if your device is on the wrong i2c bus you won't see the address. The (TWI) bus is reserved. Once you know the address of the device , then you can worry about reading it.
Usually, to read an i2c device you first have to write to it; this tells the device which register you want to read-- then you have to know whether the data is coming back to you little-endian or big-endian; and this can make a huge difference in terms of interpretation ( if you have the high and low orders confused the data is not going to make much sense ).
The data-sheet is going to be absolutely necessary.
Usually, to read an i2c device you first have to write to it; this tells the device which register you want to read-- then you have to know whether the data is coming back to you little-endian or big-endian; and this can make a huge difference in terms of interpretation ( if you have the high and low orders confused the data is not going to make much sense ).
The data-sheet is going to be absolutely necessary.
marcushh777 
please join us for a chat @ irc.pine64.xyz:6667 or ssl irc.pine64.xyz:6697
( I regret that I am not able to respond to personal messages; let's meet on irc! )
please join us for a chat @ irc.pine64.xyz:6667 or ssl irc.pine64.xyz:6697
( I regret that I am not able to respond to personal messages; let's meet on irc! )