Hi! I got a GY-521 (or MPU-6050) for reading movement. I connect it to pin 1,3,5,6 (vcc, SDA, SCL, Ground) as most tutorials suggest. I have enabled I2C I find the device with
pi@raspberrypi:~ $ sudo i2cdetect -y 1 0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- 68 -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- --I can read the device id pi@raspberrypi:~ $ sudo i2cget -y 1 0x68 0x75
0x68but I get 0x00 for the x/y/z and ax/ay/az values whatever I do pi@raspberrypi:~ $ sudo i2cget -y 1 0x68 0x44
0x00 pi@raspberrypi:~ $ sudo i2cget -y 1 0x68 0x43 0x00 pi@raspberrypi:~ $ sudo i2cget -y 1 0x68 0x3b 0x00 pi@raspberrypi:~ $ sudo i2cget -y 1 0x68 0x3c 0x00using
So it reads temp, but get 0 back (get_temp adds 36.53) and crashes on reading ACCEL_XOUT0 which is 0x3B. Which was read to 0 by i2cget, unless that handles read error of course.
pi@raspberrypi:~ $ cat /etc/modules # /etc/modules: kernel modules to load at boot time. # # This file contains the names of kernel modules that should be loaded # at boot time, one per line. Lines beginning with "#" are ignored.
i2c-dev i2c-bcm2708
pi@raspberrypi:~ $ grep blacklist /etc/modprobe.d/* /etc/modprobe.d/blacklist-rtl8192cu.conf:blacklist rtl8192cu /etc/modprobe.d/blacklist-rtl8xxxu.conf:blacklist rtl8xxxu /etc/modprobe.d/fbdev-blacklist.conf:# This file blacklists most old-style PCI framebuffer drivers. /etc/modprobe.d/fbdev-blacklist.conf:blacklist arkfb /etc/modprobe.d/fbdev-blacklist.conf:blacklist aty128fb /etc/modprobe.d/fbdev-blacklist.conf:blacklist atyfb /etc/modprobe.d/fbdev-blacklist.conf:blacklist radeonfb /etc/modprobe.d/fbdev-blacklist.conf:blacklist cirrusfb /etc/modprobe.d/fbdev-blacklist.conf:blacklist cyber2000fb /etc/modprobe.d/fbdev-blacklist.conf:blacklist kyrofb /etc/modprobe.d/fbdev-blacklist.conf:blacklist matroxfb_base /etc/modprobe.d/fbdev-blacklist.conf:blacklist mb862xxfb /etc/modprobe.d/fbdev-blacklist.conf:blacklist neofb /etc/modprobe.d/fbdev-blacklist.conf:blacklist pm2fb /etc/modprobe.d/fbdev-blacklist.conf:blacklist pm3fb /etc/modprobe.d/fbdev-blacklist.conf:blacklist s3fb /etc/modprobe.d/fbdev-blacklist.conf:blacklist savagefb /etc/modprobe.d/fbdev-blacklist.conf:blacklist sisfb /etc/modprobe.d/fbdev-blacklist.conf:blacklist tdfxfb /etc/modprobe.d/fbdev-blacklist.conf:blacklist tridentfbonme /etc/modprobe.d/fbdev-blacklist.conf:blacklist vt8623fb
pi@raspberrypi:~ $ grep i2 /boot/config.txt dtparam=i2c_arm=on dtparam=i2s=on dtparam=i2c1=on
pi@raspberrypi:~ $ uname -a Linux raspberrypi 4.9.35+ #1014 Fri Jun 30 14:34:49 BST 2017 armv6l GNU/Linux
The above is from a pi Zero, I get the same result with a Pi 1b+ Anyone have any suggetions