Hi Xi and Peter,
I have the same problem: I have a BerryGPS-IMU v3 interfacing with a Raspberry Pi Zero W. I am able to connect to the GPS, but I can’t find the I2C devices. I’ve worked through the IMU tutorial and the GPS one. Here are some relevant terminal outputs.
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: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --pi@raspberrypi:~ $ ls -l /dev/i2*
crw-rw---- 1 root i2c 89, 1 Mar 27 04:17 /dev/i2c-1
pi@raspberrypi:~ $ lsmod | grep i2c
i2c_bcm2835 16384 0
i2c_bcm2708 16384 0
i2c_dev 16384 0
pi@raspberrypi:~ $ grep i2c /boot/config.txt
dtparam=i2c_arm=on
dtparam=i2c1=onI won’t show the GPS output since I don’t want to dox myself, but the GPS is reading accurately. I have the hat soldered onto a double-stack header board, and what my solder joints lack in elegance they make up for in volume (see pic). I’ve already added more.
Any ideas for what might be causing the I2C devices to fail? Maybe I should interface directly with sales, but I want to make sure I haven’t missed anything first.
