Featured Articles
Announcing Pi
Technical Specifications
Raspberry Pi FAQs
Win a Pi
Raspberry Pi Wishlist
Actions
Forum Thread Details
  • State Suggested Answer
  • Replies 18 replies
  • Answers 2 answers
  • Subscribers 668 subscribers
  • Views 6021 views
  • Users 0 members are here
Related

i2c stop working

Former Member

Hello!

 

I am trying to solve my problem with i2c on a Raspberry Pi model B.

I have build myself a little weather station with some sensors connected via i2c.

It was working flawlessly for 3 months but now it suddenly stopped.

 

I made sure the /etc/modprobe.d/raspi-blacklist.conf and /etc/modules configuration files are still as they were.

The i2c_dev and i2c_bcm2708 modules are loaded after reboot but i2cdetect gives me:

 

Error: Could not open file `/dev/i2c-1' or `/dev/i2c/1': No such file or directory

 

I tried apt-get update, apt-get upgrade, rpi-update, ... but no luck so far.

 

Can anyone help me please?

Thanks for any ideas.

Parents
  • 0

    Your problem is due to you running the following command:

     

    sudo rpi-update

     

    This command is only meant to be used by those involved in testing the latest experimental versions of the the Raspberry Pi kernel. Unfortunately the latest test version has introduced some very radical changes that will cause these problems. The solution to your problem is to roll back to the latest stable operational version. This can be done with the following command:

     

    sudo apt-get --reinstall install libraspberrypi-bin libraspberrypi-dev libraspberrypi-doc libraspberrypi0 raspberrypi-bootloader

     

    The last stable version is 3.12.35+ #730

     

    You can find out which version you are using with this command:

     

    uname -a

  • 0 in reply to urkraft

    Hi. Thanks for your help, finally I am getting somewhere.

     

    Strange thing is that i2c stoped working before I did "sudo rpi-update".

     

    After

    sudo apt-get --reinstall install libraspberrypi-bin libraspberrypi-dev libraspberrypi-doc libraspberrypi0 raspberrypi-bootloader

    the uname -r was still giving me 3.18.5+. So I used rpi-update to manually roll back to 3.12.35+.

     

    After doing this i2c started working again but Pi developed yet an another problem.

     

    I have got three sensors (BMP085, MPU6050 and SHT10) on one board connected to the i2c GPIO pins.

    The only way i was able to read data from all of them was like this:

     

    1) read bmp085

    2) read mpu6050

    3) sudo modprobe -r i2c_bcm2708

    4) read sht10

    5) sudo modprobe i2c_bcm2708

     

    First four steps works great but when I do the last one Pi just freeze instantly. No black screen, no nothing, just freeze. This is very strange because I load i2c_bcm2708 when booting withnout a problem.

     

    Any ideas what can be wrong?

Reply
  • 0 in reply to urkraft

    Hi. Thanks for your help, finally I am getting somewhere.

     

    Strange thing is that i2c stoped working before I did "sudo rpi-update".

     

    After

    sudo apt-get --reinstall install libraspberrypi-bin libraspberrypi-dev libraspberrypi-doc libraspberrypi0 raspberrypi-bootloader

    the uname -r was still giving me 3.18.5+. So I used rpi-update to manually roll back to 3.12.35+.

     

    After doing this i2c started working again but Pi developed yet an another problem.

     

    I have got three sensors (BMP085, MPU6050 and SHT10) on one board connected to the i2c GPIO pins.

    The only way i was able to read data from all of them was like this:

     

    1) read bmp085

    2) read mpu6050

    3) sudo modprobe -r i2c_bcm2708

    4) read sht10

    5) sudo modprobe i2c_bcm2708

     

    First four steps works great but when I do the last one Pi just freeze instantly. No black screen, no nothing, just freeze. This is very strange because I load i2c_bcm2708 when booting withnout a problem.

     

    Any ideas what can be wrong?

Children
  • 0 in reply to Former Member

    I believe that something terribly wrong has happened with the central software repository for the raspberry pi in connection with the release of the Raspberry Pi 2 B today. I know that they have been experimenting with changes to the kernel that drastically effects how the devices work, and i see that the production version that is downloaded with apt-get dist-upgrade appears to be using the new device handling methods - which are not compatable with the old.

     

    I do not believe that this was intended at this point in time, and all raspberry pi related sites appear to be overloaded - probably both due to the release of the 2 B version as well as this major mistake.

     

    Rest assured that your problems are due to these changes and not to any faulty hardware - of that i am now 100% sure. I believe that the best course of action it to wait a few days and do a sudo apt-get update followed by a sudo apt-get dist-upgrade followed by a sudo reboot. The problem will eventually be fixed in a way that does not require adhoc fixes.

     

    Since i used about a half hour just to log in and functionality to reply to your post i do not plan on bothering with trying to access any Raspberry Pi related sites for a couple of days. By then i beieve that things will be under control again. Be patient image

  • 0 in reply to urkraft

    that's a good point about today's problems on raspberry pi related sites. Let's see what the future brings to us...