- Uriah

Kernels >= 3.10: w1_gpio destroys i2c bus 0 (raspicam doesn't work anymore) issue #435

Apparently it is a firmware issue in the early RPI B+ Bcm chip. Where the gpio and camera clashes on a pin assignment, newer RPi's don't have this issue. There are a few workarounds but they only seem to work for a few people. Like blacklist i2c and gio kernels or revert to an older firmware. I have not found a working solution for my pi yet. Anyone familiar with this issue?
I will borrow a rpi from work and see if it has the same issue. I bought my pi from element14 which had an old stock of rpi's.

Thanks!
Also the issue is very old from 2013 and still open so apparently there is no firmware fix yet.

Now I got a new message and it looks more promising although no cigar yet!
The cam led is now lit continuously like when I started with the original image so I might have made things worse by the upgrade.
I have changed the available memory from 128 to 256mB and enabled the cam via raspiconfig.

pi@atlas3d ~ $ raspistill -n -o out.jpg
mmal: mmal_vc_component_enable: failed to enable component: ENOSPC
mmal: camera component couldn't be enabled
mmal: main: Failed to create camera component
mmal: Failed to run camera app. Please check for firmware updates

pi@atlas3d ~ $ vcgencmd get_camera
supported=1 detected=1
pi@atlas3d ~ $

Hi Uriah,

the camera is in the correct slot but the led on the cam is not turning on (it only flashes shortly after a boot so it seems to be connected). I followed the instructions from and RPI site (video) to the letter. The connection strip on the ribbon is facing the right way.
I upgraded the RPI to Jessie to see if it makes differences but not. So either the Pi is broken or the Cams. I have another Pi at work so will try it there with the camera's.
Can you let me know how I can get the original image for the SD? I might put that on another SD card and see if it makes a difference. Another issue I have is the WiFi which is not working. Probably because of my upgrade it lost its original drivers. I will look into that once the camera is working. I can live without it...:)

Thanks heaps!

- Uriah

pi@atlas3d ~ $ vcgencmd get_camera
supported=1 detected=0
pi@atlas3d ~ $ gpio readall
+-----+-----+---------+------+---+--B Plus--+---+------+---------+-----+-----+
| BCM | wPi |   Name  | Mode | V | Physical | V | Mode | Name    | wPi | BCM |
+-----+-----+---------+------+---+----++----+---+------+---------+-----+-----+
|         |        |    3.3v  |         |      |  1   || 2    |      |         | 5v        |         |        |
|   2    |   8   |   SDA.1|   IN   | 0   |  3   || 4    |      |        | 5V         |        |        |
|   3    |   9   |   SCL.1 |   IN   | 0   |  5   || 6    |     |         | 0v         |        |        |
|   4    |   7   | GPIO. 7 |  OUT | 0  |  7   || 8    | 0  | ALT0 | TxD       | 15   | 14   |
|         |        |      0v   |           |    |  9    || 10 | 0   | ALT0 | RxD      | 16   | 15   |
|  17   |   0   | GPIO. 1 |  OUT | 0  | 11 || 12  | 0   | OUT  | GPIO. 1 | 1     | 18   |
|  27   |   2   | GPIO. 2 |   IN   | 0  | 13  || 14  |      |         | 0v         |        |        |
|  22   |   3   | GPIO. 3 |   IN   | 0  | 15  || 16  | 0   | OUT  | GPIO. 4 | 4     | 23  |
|         |        |    3.3v   |         |     | 17  || 18  | 0   | OUT  | GPIO. 5 | 5     | 24  |
|  10   |  12  |    MOSI  |   IN  | 0  | 19  || 20   |     |        | 0v           |        |       |
|   9    |  13  |    MISO  |   IN  | 0  | 21  || 22  | 0   | IN    | GPIO. 6   | 6     | 25  |
|  11   |  14  |    SCLK  |   IN  | 0  | 23  || 24  | 0   | IN    | CE0        | 10   | 8    |
|         |        |      0v     |        |     | 25  || 26  | 0   | IN    | CE1        | 11    | 7   |
|   0    |  30  |   SDA.0 |   IN   | 0 | 27  || 28  | 0    | IN   | SCL.0      | 31    | 1   |
|   5    |  21  | GPIO.21 |   IN   | 0 | 29  || 30  |      |        | 0v           |         |      |
|   6    |  22  | GPIO.22 |   IN   | 0 | 31  || 32  | 0   | IN    | GPIO.26  | 26    | 12  |
|  13   |  23  | GPIO.23 |   IN   | 0 | 33  || 34  |      |        | 0v           |         |       |
|  19   |  24  | GPIO.24 |   IN   | 0 | 35  || 36  | 0   | IN    | GPIO.27  | 27    | 16  |
|  26   |  25  | GPIO.25 |   IN   | 0 | 37  || 38  | 0   | IN    | GPIO.28  | 28    | 20  |
|         |        |      0v     |         |    | 39  || 40  | 0   | IN    | GPIO.29  | 29    | 21  |
+-----+-----+---------+------+---+----++----+---+------+---------+-----+-----+
| BCM | wPi |   Name  | Mode | V | Physical | V | Mode | Name    | wPi | BCM |
+-----+-----+---------+------+---+--B Plus--+---+------+---------+-----+-----+

hope this helps with the identification of the issue....

"dpkg --print-architecture" will return "armel" for Debian and "armhf" for Raspbian

mine did returned "armhf". Apparently it should be Debian?

I made sure that the flat ribbon was inserted properly and even replaced the cam/ribbon with a new one since I thought it was defect.

Further I increased the memory to 256k (GPU in config.txt) and searched for this issue online beofre posting my request here. There were a few posts in the raspberry forum about this issue where they said that the GPIO and I2C bus clashes (2013). Since I have not seen anyone else with this issue in this Atlas3D forum, I thought it was a defect camera so replaced the cam with a new one but still the same issue.

Not sure if this additional info helps:
- After trying with no results: I used raspi-config to enable the camera and the advanced settings (I2C, SPI) with no results.
- When I start up the Pi, the cam led immediately turns on and always stays on.
- I have tried raspicam with just the Pi without the step electronics (GPIO) which returns same error
- It is a Pi B+ (version 1.2). I had the Pi working on a SD card previously before the kit arrived. After I insert the old working sd card, it refuses to boot. Just a # command turns up in the screen (HDMI).
- Finally I have updated the Pi with the latest distro and boot with as result same error but freelss does not start automatically anymore. Should I re-image a SD card with your distribution image? (not sure how to get that image)

raspistill -n -o out.jpg

- Uriah

The problem that I encounter is that I get the following error message:

Creating video mode camera resolution=1600x1200
mmal: mmal_vc_component_create: failed to create component 'vc.ril.camera' (1:ENOMEM)
mmal: mmal_component_create_core: could not create 'vc.ril.camera' (1)
Failed to create camera component open Failed to create camera component/home/pi/raspicam-0.1.3/src/private/private_impl.cpp 102
Exception: Error opening camera

I found info on this on the raspi forum: https://www.raspberrypi.org/forums/view … hp?t=39996

I have updated my Pi to the latest distro and bootcode (rpi-update). Now freelss doesn't start automatically and the same error continues to exist.
I have used Raspi-config, advanced settings to enable the I2C and SPI kernel support.

So far no luck. Anyone who have encountered this issue or can help trouble shooting?
Thanks Paul