Hi Rafael,
I am having problems with i2c read write too. The code only seems to pick
up odd values for some reason. I am a newbie to this domain in general and
would appreciate any assistance. Can you share the read instance of your
code or help me find fault in mine?
opResult = read(i2c
I don't understand what happened, but today the behavior changed again,
"i2cdetect -y -r 1" working as it is supposed to and my program doing
nothing at all. Maybe I got something wired wrong yesterday? But I don't
really care right now, since I also found a bug in my code (damm pointers)
and n
After some further testing I can clarify the behavior of the I2C-bus:
When I manually access the I2C-dev nothing happens, SDA and SCL keep 3.3V
the whole time.
When I use the command "i2cdetect -y -r 1" the SCL gets the typical
clock-look with about 4us high and low, except for its not going betw
>
> No, I thought the BBB has intenal pullups and according to the .dts they
> are enabled?
>
--
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 re
Do you have a pullup on the i2c line?
On Monday, March 31, 2014 1:59:46 AM UTC-7, Rafael Fiebig-Bindner wrote:
>
> Hi community,
>
> I am currently trying to access a temperature sensor via I2C. The problem
> is whenever I want to send data I get the error message: "Bad address",
> but the BBB
