Under Debian 8, the external I2C bus is now I2C-2.
I2C-1 is internal only, and used for talking to the PMIC and things like
that.
Don't use it, unless you really understand what you are doing.
--- Graham

==

On Fri, Mar 10, 2017 at 8:08 AM, christ christ <mamanechri...@gmail.com>
wrote:

> Hi Graham,
> I have been using the latest version of Debien, for three days now with
> the same result.
> On the other hand i checked with the oscilloscope the SDA and SCL lines
> are not acting like they are supposed to act (even on the default P9_19 and
> P9_20).
>
> Thought maybe they all need to be enable.Tried the following method but in
> vain (NO such file or directory is the response i'm getting)
> *To enable the I2c-1 on the BeagleBone Black Rev A, B and C:*
>
>    1. Rev A/B: Open the file /media/BEAGLEBONE/uEnv.txt in an editor
>    (vim/nano)
>    2. Rec C: Open the file /boot/uboot/uEnv.txt in an editor (vim/nano)
>    3. Add the key "capemgr.enable_partno="
>    4. Add the ports you want to enable, comma separated (BB-I2C0,
>    BB-I2C1, etc)
>    5. Reboot.
>
> Am i right to say the I2c buses are not enable? or is it another proble?
>
> On Thu, Mar 9, 2017 at 4:25 PM, Graham <gra...@flex-radio.com> wrote:
>
>> Then it is not wired or connected correctly.
>> Put an oscilloscope on the data and clock lines and see if they are doing
>> what they are supposed to do.
>> It also looks like you are using an old version of the OS.
>> Move to Debian 8, and you should see the I2C devices on bus 2.
>> Hook the I2C Clock to P9-19.  Hook the I2C data to P9-20.
>> You should not have to mess with the device tree or pin configuration.
>> Power and ground also required.
>>
>> --- Graham
>>
>> ==
>>
>> On Thursday, March 9, 2017 at 6:52:04 AM UTC-6, christ christ wrote:
>>>
>>> The MPU-9250 breakout from spark fun come with pull up resistors.
>>>
>>> On 09 Mar 2017 00:42, "Graham" <gra...@flex-radio.com> wrote:
>>>
>>>> Something is not wired right.
>>>> Did you put pull-up resistors on the I2C lines?
>>>> --- Graham
>>>>
>>>> ==
>>>>
>>>> On Wednesday, March 8, 2017 at 12:02:04 PM UTC-6, mamane...@gmail.com
>>>> wrote:
>>>>>
>>>>> Hi Guys,
>>>>>
>>>>> I’m struggling to get the device address (MPU-9250). i got to the
>>>>> following stage:
>>>>>
>>>>>
>>>>> root@beaglebone:~# sudo i2cdetect -r 0
>>>>> WARNING! This program can confuse your I2C bus, cause data loss and
>>>>> worse!
>>>>> I will probe file /dev/i2c-0 using read byte commands.
>>>>> I will probe address range 0x03-0x77.
>>>>> Continue? [Y/n] y
>>>>> 0 1 2 3 4 5 6 7 8 9 a b c d e f
>>>>> 00: — — — — — — — — — — — — —
>>>>> 10: — — — — — — — — — — — — — — — —
>>>>> 20: — — — — UU — — — — — — — — — — —
>>>>> 30: — — — — UU — — — — — — — — — — —
>>>>> 40: — — — — — — — — — — — — — — — —
>>>>> 50: UU — — — — — — — — — — — — — — —
>>>>> 60: — — — — — — — — — — — — — — — —
>>>>> 70: UU — — — — — — —
>>>>> root@beaglebone:~# sudo i2cdetect -r 1
>>>>> WARNING! This program can confuse your I2C bus, cause data loss and
>>>>> worse!
>>>>> I will probe file /dev/i2c-1 using read byte commands.
>>>>> I will probe address range 0x03-0x77.
>>>>> Continue? [Y/n] y
>>>>> 0 1 2 3 4 5 6 7 8 9 a b c d e f
>>>>> 00: — — — — — — — — — — — — —
>>>>> 10: — — — — — — — — — — — — — — — —
>>>>> 20: — — — — — — — — — — — — — — — —
>>>>> 30: — — — — — — — — — — — — — — — —
>>>>> 40: — — — — — — — — — — — — — — — —
>>>>> 50: — — — — UU UU UU UU — — — — — — — —
>>>>> 60: — — — — — — — — — — — — — — — —
>>>>> 70: — — — — — — — —
>>>>>
>>>>>
>>>>> But even after connecting my device It is still the same (I mean it
>>>>> still doesn't show the device's address). Any advise?
>>>>>
>>>>> Thanks
>>>>>
>>>>
>

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CANN_KV5OQzLvi9ckb%3D8yDKubQbbCQri8t-VO4aEVe4zSx2O64Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to