Hi Chris,
I did not mean to say that LINUX is not useful.
But yes, I can see your point: if you have to change the I2C clock that is
something different.
Martin H.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google G
Martin H. wrote:
> [-- text/plain, encoding 7bit, charset: UTF-8, 16 lines --]
>
> I freely admit that I don't know anything about LINUX. We don't use it.
> But why would you want to modify the device tree if I2C is running?
>
> We have I2C running with an LPC2468. All we did is putting a P8287
I freely admit that I don't know anything about LINUX. We don't use it.
But why would you want to modify the device tree if I2C is running?
We have I2C running with an LPC2468. All we did is putting a P8287 at each
end of the line.
And it works. No code modification was required.
Martin H.
--
Martin H. wrote:
> [-- text/plain, encoding quoted-printable, charset: UTF-8, 31 lines --]
>
> You might like to have a look at the P82B96 data sheet.
> Feature:
> "400kHz operation over at least 20 meters of wire"
>
> And you don't have to modifiy your I2C code!
>
Actually I have some P82B715P
... and the P82B71 ...
Martin H.
--
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 beagleboard+unsubscr
Just change the speed in board file or in dts
&i2c4 {
pinctrl-names = "default";
clock-frequency = <40>;
};
It is 400kHz you can change to 100kHz
or If you are using a board file
omap_register_i2c_bus(2, 400, drishti_i2c2_board_info,
ARRAY_SIZE(drishti_i2c2_board
You might like to have a look at the P82B96 data sheet.
Feature:
"400kHz operation over at least 20 meters of wire"
And you don't have to modifiy your I2C code!
Martin H.
Am Freitag, 29. August 2014 19:18:46 UTC+2 schrieb c...@isbd.net:
>
> I want to stretch the I2C bus to a few metres, I will u
The I2C protocol allows any slave device on the bus to 'stretch' the pulse
for as long as it wants by holding SCL low (in Standard mode, and Fast
mode, but not High-speed mode). This can slow the clock rate arbitrarily.
It's explained in specification:
I²C-bus Specification, Version 3.0 (Rev. 0
