Update:
I think it's actually at Address 0x77. If I remove the SDI wire from the
breadboard to the BB, then it does not detect anything on 77. That should
be a good confirmation that it's on the bus.
Where do I go from here?
debian@beaglebone:~/sudo i2cdetect -r 2
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-2 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: -- -- -- -- -- -- -- 77
On Friday, March 4, 2016 at 9:02:58 PM UTC-5, AV8TOR wrote:
>
> Getting back to this after some days...
> I imagine the difference between I2C mode vs SPI is how it's physically
> interfaced to the board.
> I believe that my board is connected for I2C.
>
> debian@beaglebone:~$ i2cdetect -r 2
> WARNING! This program can confuse your I2C bus, cause data loss and worse!
> I will probe file /dev/i2c-2 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: -- -- -- -- -- -- -- --
>
> How do I interpret what I am seeing? The I2C docs don't make much sense to
> me.
>
> Thanks
> Mike
>
> On Monday, February 29, 2016 at 10:08:38 PM UTC-5, Nuno wrote:
>>
>> On 02/29/2016 08:28 PM, AV8TOR wrote:
>> > Update:
>> > I anticipate someone will want to know how the sensor is interfaced:
>> > Again, using the BMP085 as a reference for my BMP280
>> > The actual BMP280 pinout BMP280 Pinout
>> > <
>> https://learn.adafruit.com/adafruit-bmp280-barometric-pressure-plus-temperature-sensor-breakout/pinouts>
>>
>>
>> > the below steps snipped from this link: BMP On the Beaglebone Black
>> > <http://elinux.org/Beagleboard:BMP_on_the_Beagle_Bone_Black>
>> >
>> > 1. Connect GND from the BMP085 to P9.1 of your BBB.
>> > 2. Connect VIN from the BMP085 to P9.3 of your BBB.
>> > 3. Connect SCL from the BMP085 to P9.19 of your BBB.
>> > 4. Connect SDA from the BMP085 to P9.20 of your BBB. (NOTE: the
>> BMP280
>> > does not have SDA, so I'm using SDI instead)
>>
>> You might want to make sure that you are using the BMP280 in I2C mode,
>> instead of SPI mode, as it supports both.
>>
>> Before assigning a driver to it (your echo command), you can try to see
>> if it's actually being detected on the i2c bus and dump its registers
>> using the i2c tools (i2cdetect, i2cdump)
>>
>> You also didn't mention what linux/kernel versions you are running.
>> There's support for BMP280 on newer linux kernels within the kernel iio
>> framework as of 2014/2015.
>>
>> regards,
>> Nuno
>>
>> --
>>
>
--
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.
For more options, visit https://groups.google.com/d/optout.
