I managed to connect I2C device gy-91 contains both MPU9250 & BMP280 IMU 10DOF sensor
But cannot read its data like we do in raspberry pi
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: 50 -- -- -- -- -- -- 57 -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
Please help
if you mean read i2c device data by shell command,you can try this command:
sudo i2cdump -y 1 0x50 //Read all reg data of I2c device:0x50
sudo i2cdump -y 1 0x57 //Read all reg data of I2C device:0x57
sudo i2cdump -y <i2cbus_number> <i2c_device_addr>
if you want to monitor all reg data of any I2C device ,Please try:
watch -n 0.1 sudo i2cdump -y 1 0x50 //update data per 0.1 s
watch -n 1 sudo i2cdump -y 1 0x50// update data per 1s
(or sudo watch -n 0.1 i2cdump -y 1 0x50 will work too)
watch -n
Be careful ,if you are running a program that can read data from any i2c device,Do not use “i2cdump” command to monitor i2c device data simultaneously. “i2cdump” will interfere the data read from your program. At least, it happened on my own test.
Hope my answer will help you a little.
@karthikbalu.meng your device(s) aren’t being detected by i2cdetect. 0x50 and 0x57 are I2C ID EEPROM chips on the module and baseboard respectively. Make sure your device is powered and the I2C pins are connected to pins 3 and 5.
1 Like