Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MPU6050 Remote I/O error on RasberryPI 4 #117

Open
paolov opened this issue Oct 13, 2019 · 2 comments
Open

MPU6050 Remote I/O error on RasberryPI 4 #117

paolov opened this issue Oct 13, 2019 · 2 comments

Comments

@paolov
Copy link

paolov commented Oct 13, 2019

I compiled the MPU6050-Pi-Demo code after changing to /dev/i2c-1 (otherwise I was getting "Failed to open device: Is a directory") and now I'm getting the error "Failed to write reg: Remote I/O error". Here is the log:

Initializing I2C devices...
Failed to write reg: Remote I/O error
Failed to write device(-1): Remote I/O error
Failed to write reg: Remote I/O error
Failed to write device(-1): Remote I/O error
Failed to write reg: Remote I/O error
Failed to write device(-1): Remote I/O error
Failed to write reg: Remote I/O error
Failed to write device(-1): Remote I/O error
Testing device connections...
Failed to write reg: Remote I/O error
MPU6050 connection failed
Failed to write reg: Remote I/O error
a/g:   6912      0      0        0      0      0

I can access the mpu with c# without problem at address 69 instead of 68 so I tried to initialize the mpu to address MPU6050_ADDRESS_AD0_HIGH but I'm getting the same error.
Here the result of 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: -- -- -- -- -- -- -- -- -- 69 -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
@paolov
Copy link
Author

paolov commented Oct 13, 2019

Just to confirm that at the end it works perfectly initializing to address 69. It was me making a mistake.
To recap, to make it working on RPi4 you have to change the folder to /dev/i2c-1 and use address accordingly to i2cdetect (69 in my case)

@richardghirst
Copy link
Owner

richardghirst commented Oct 15, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants