On Wednesday, October 16, 2013 at 1:02:59 AM UTC+3, clarkbr...@gmail.com
wrote:
>
> We are using the Invensense MPU6050 IMU on I2C with Beaglebone Black
> (Angstrom 3.8.13). We can use I2C-tools and file I/O thru /dev/i2c but the
> read speed is disappointingly slow. We only read the 3x gyros
I believe (via email correspondence) that the people at Tindie have
been busy with the Arduino sketch for the past 2 weeks and should have
something out within the next 2 weeks (my guess at their time frame)
I've been hounding Bosch for the Linux device
drivers.unfortunately nothing yet.
The new Bosch sensor really looks great! Do you know whether there are
already some arduino sketches available, as the author says in the
description at tindie? Would be cool to read some code and port them for
the beaglebone. Im about to build my own quadcopter and used the Bosch
BMA180
I understand the frustration with the Invense driver. I want to repeat my
post from earlier (May 6) that the I2C based chips are quite usable with
direct I2C reads and writes. I don't like the remaining I2C latency, but
the chips are quite nice. We progressed beyond our initial
Hi,
did you pursue your work on the mpu6050 ?
I have a hard time figuring how to use the invensense driver. Is it worth
it ?
thanks
Le mardi 13 mai 2014 22:46:55 UTC+2, thomas.g...@gmail.com a écrit :
Hi,
I have got a small project at home running the inv_mpu6050 driver on a
3.8.13
I gave up, repeated emails about Linux drivers were ignored, together
with the fact that it's not a true 9 DOF ...so I dumped the board
I'm hoping Bosch comes to the party with this little gem:
http://www.bosch-sensortec.com/en_GB/homepage/products_3/9_axis_sensors_5/ecompass_2/bno055_3/bno055_4
Hi,
well currently I am working on other projects.
To get the invensens driver up and running was a matter of either filling
the data necessary for the driver in the platform data (old school) or make
the driver aware of device tree information.
I have quickly had a look at the current
Hi Bruce
The link
https://android.googlesource.com/kernel/msm/+/android-msm-hammerhead-3.4-kk-fr2/drivers/staging/iio/imu/inv_mpu/README
says that i have to build the kernel to make it work.
On Monday, September 15, 2014 5:04:19 PM UTC+5:30, bruce@gmail.com
wrote:
Hi
Also been
Hi
Also been struggling to get Invensense driver to worknot very impressed
with Invensense to be honest. If you login to their support forum, there is
no mention of MPU9250 Linux kernel drivers.I found the tegra stuff,
emailed Invensense and asked them where they publish their
Hi,
I have got a small project at home running the inv_mpu6050 driver on a
3.8.13 kernel. To get it working I had to modify the driver, so that it
accepts device tree parameters, then I wrote a cape configuration for the
i2c and the mpu6050 device and voila it worked. I added the driver to the
Hi,
I have got a small project at home, running the inv-mpu6050 driver. To get
it to work I had to add device tree functionality to the driver and then
write a cape dtc for the beaglebone. As a result I have got the following
outputs:
cat /sys/devices/bone_capemgr.8/slots
0: 54:PF---
1:
No we never got this (the Invensense driver) working. We just stuck it out
with reading /dev/i2c. This is costing us a 20% time penalty which really
really hurts. We couldn't get anyone to take on fixing the unbelievably
long read times (~1msec) on /dev/i2c either.
Some of us are hoping the
Knowing this discussion is old, i have to ask did you get it working? And
my experience is with the bbw, not the bbb. but the i2c buss on my device
is 100khz. maximum is 400khz. I was able to get the accelerometer and gyro
values at a rate of 200hz without issue, which isn't the max the chip
Andrew,
Doing file I/O means read and write to /dev/i2c/etc. As you put it in your
question, they are the same thing and basically the same as using the
command line tools. This works out of the box. You need to know the device
registers pretty well because you will be accessing them. Some
Okay thanks for all the help!
I think I'm just going to get familiar with the registers and either write
or find a library rather than delve too much farther into drivers and such.
Maybe another day.
Thanks again for the pointers
Andrew
On Fri, Dec 27, 2013 at 6:55 PM, clarkbriggs...@gmail.com
Setting the SLEEP bit seemed to have done the trick, everything seems to
work now! (or at least at the surface)
I apologize for any beginner questions (this is my first trip into the
wonderful world of embedded linux). What is the difference between the
file approach and i2c?
I was planning on
I'm not sure I understand exactly what you are asking, but you can access
the i2c bus directly through linux file descriptors (i.e. like any other
normal file). No special device drivers are needed and if you are using
P_19 and P-20, it's enabled by default w/o custom device trees.
I made a blog
Mark,
I poked briefly at the reference you provided. The write up looks very
much the same as the Invensense MPU6050 driver in the Angstrom on the
Black. This seems reasonable. The Invensense author has done a good job
of getting it into the Linux tree and the various distributions have
Mark,
Near as I can tell, no one has done better than just file i/o via
/dev/i2c/... This works, but doesn't seem to expose or take advantage of
the Invensense kernel driver functionality. Plus it seems to be very
slow. Jason Kridner was tackling it a couple weeks ago, but didn't report
any
Did anyone every get the inv-mpu6050 kernel driver to work? I have the
device on the i2c bus and I can read and write registers using
*i2cset/i2cget*, but *modprobe inv-mpu605* doesn't make anything appear.
--Mark
On Saturday, November 2, 2013 11:51:04 AM UTC-4, clarkbr...@gmail.com wrote:
Jason,
I apologize for taking so long to answer. It wasn't quick to figure out
which breakout board we had with the MPU6050 on it. It is apparently a Kootek®
Arduino GY-521 MPU-6050 Module from Amazon.
Itis wired:
P9_1-Gnd
P9_3-VCC
P9_19 -SCL
P9_20 - SDA
Your P9_19 SCL and P9_20
On Fri, Nov 1, 2013 at 12:09 AM, Joshua Datko jbda...@gmail.com wrote:
Nevemind, that may be unrelated. I just rebooted and my device enumerated
fine. I think what's confusing (me) is the I2C2 by the SRM (P9_19/20) shoes
up as I2C1...
Yeah, this is a really confusing (well-known) issue where
On Tue, Oct 29, 2013 at 2:19 PM, Jason Kridner jkrid...@beagleboard.org wrote:
On Thu, Oct 17, 2013 at 6:12 PM, clarkbriggs...@gmail.com wrote:
AIW:
I went back thru the adafruit library and didn't find anything specific on
I2C, although it is listed as a topic. I have been looking at
So I've been struggling with I2C. Somebody on this list gave me the tip to
do:
echo BB-I2C1 /sys/devices/bone_capemgr.??**??/slots
which enables the third I2C bus and my device then was visible via
i2cdetect -y -r 1 on pins P9_19 and P9_20. Although, after doing that,
you'll have an i2c1
Nevemind, that may be unrelated. I just rebooted and my device enumerated
fine. I think what's confusing (me) is the I2C2 by the SRM (P9_19/20)
shoes up as I2C1...
some output:
ebian@arm:~$ ls -l /sys/bus/i2c/devices/i2c-*
lrwxrwxrwx 1 root root 0 Nov 1 04:02 /sys/bus/i2c/devices/i2c-0 -
25 matches
Mail list logo
