You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 11, 2024. It is now read-only.
Looking at my Oscilloscope, the I2C bus is writing the correct buffer content, but what it is reading is completely wrong.
The problem is, after writing to the bus there is a stop condition. But the device longs for a repeated start.
I also tried single write and read operations with previously setting combined to "Y" and vice versa after the operations.
I already checked https://github.com/Pi4J/pi4j/issues/225 this to fix my problem. But i think i doing something wrong.
I also checked the bus speed.
I can change the file "combined" from Y to N and vice versa. But it´s the same output at the oscilloscope.
Maybe someone can show me the right direction for getting a solution.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello.
I want to read out an I2C device with registers which have 2 bytes long adresses. I am using the method:
i2cDevice.read(writeBuffer, 0, 2, readBuffer, 0 ,2)
Looking at my Oscilloscope, the I2C bus is writing the correct buffer content, but what it is reading is completely wrong.
The problem is, after writing to the bus there is a stop condition. But the device longs for a repeated start.
I also tried single write and read operations with previously setting combined to "Y" and vice versa after the operations.
I already checked https://github.com/Pi4J/pi4j/issues/225 this to fix my problem. But i think i doing something wrong.
I also checked the bus speed.
I can change the file "combined" from Y to N and vice versa. But it´s the same output at the oscilloscope.
Maybe someone can show me the right direction for getting a solution.
The text was updated successfully, but these errors were encountered: