Issue with getting camera to work


171 posts   Page 7 of 7   1 ... 3, 4, 5, 6, 7
by jamesh » Thu Jun 06, 2013 10:58 pm
That's simply the camera not streaming data out - it's must be powering up and is identified so I2C must be working or the software would have failed earlier.
Unemployed software engineer currently specialising in camera drivers and frameworks, but can put mind to most embedded tasks. Got a job in N.Cambridge or surroundings? I'm interested!
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 11718
Joined: Sat Jul 30, 2011 7:41 pm
by panik » Fri Jun 07, 2013 12:28 am
Are you saying it's not kaputt?

I think it's the same problem that (for example/among others) @oxidizer and @pharar have.

jamesh wrote:
pharar wrote:
oxidizer wrote:Yes, an empty file is created in the home directory. I've also tried to running the raspi apps in various locations using root user (sudo) as well as the normal user (pi).

Exactly the same problem for me...
[...]


This is an odd one - not the same as the other errors reported. I'm not sure what can cause failure to connect the preview, and the error code appears invalid. I'll need to look in to it.

EDIT: Doh! This is a known issue with the -n flag - I've fixed it for the next release but in the meantime, just don't use the -n flag.


Not using the -n flag doesn't seem to help, so there might still be other issues. But you are right. It doesn't fail completely, so there might be hope.
Posts: 267
Joined: Fri Sep 23, 2011 12:29 pm
Location: Netherlands
by testhack » Fri Jun 07, 2013 12:50 am
This is good feedback. There has to be a more systemic issue (other than the static death theory). I know I barely touched the camera daughter board when I connected it. Frankly if the camera was that susceptible to static charge we would see a ton more reports of the camera board working and the failing (since the camera board is always exposed without a case).
I too ordered another camera board but hope we can find root cause to these failures since the boards don't seem to be completely dead.
Posts: 8
Joined: Mon Jun 03, 2013 3:22 pm
by jbeale » Mon Jun 10, 2013 4:31 am
Sorry for the incomplete report but this is what I know and can reconstruct from a flurry of trouble this morning.

I have been playing with my RPi camera for about two weeks with no significant troubles. My Pi was headless and I was using SSH to login and run raspistill and curl to send out the resulting image files to my FTP site. I tried this with both a Model B and a Model A, and all worked just fine. But I had never seen the live preview using this setup, since I never had a display on the RPi with the camera. I decided to see what I was missing so I connected the camera to a Model A I had already hooked up to a display (with everything off, of course). This was up to date with apt-get update / upgrade as of yesterday. Fired it up, but I just got
Code: Select all
    >raspistill -o image.jpg
    mmal: mmal_vc_component_create: failed to create component 'vc.ril.camera' (1:ENOMEM)
    mmal: mmal_component_create_core: could not create component 'vc.ril.camera' (1)
    mmal: Failed to create camera component
    mmal: main: Failed to create camera component


which I had not seen before. No idea why that happened; cables seemed correctly installed. I returned camera to other Model A board where it had worked before, and success, preview appeared. This is working in the basic console command line, I did not start X Windows. Then tried raspistill with long timeout, -t 99999 which I later stopped with Control-C. Bad news from this point on; camera would randomly refuse to respond, with the red light staying on. Shutdown, power off, reboot would make things better for a while, but then found SD card corruption. Boot message says could not read some block for several retries on boot; eventually worked, but then the command "ifconfig" caused the camera light to go on! (*) Clearly into a major malfunction now, so I am re-imaging the SD card from a backup (which fortunately I did a few days ago, using USBit). Posting here in case this helps anyone.

* UPDATE: just realized I still had a 'cron' task active that took a picture every 15 minutes, while I was also manually running raspistill at various times, so there may have been two instances of raspistill trying to run at once. Would like to think that should still not cause SD card corruption, but maybe that was the issue.
User avatar
Posts: 2027
Joined: Tue Nov 22, 2011 11:51 pm
by jamesh » Mon Jun 10, 2013 9:16 am
jbeale wrote:Sorry for the incomplete report but this is what I know and can reconstruct from a flurry of trouble this morning.

I have been playing with my RPi camera for about two weeks with no significant troubles. My Pi was headless and I was using SSH to login and run raspistill and curl to send out the resulting image files to my FTP site. I tried this with both a Model B and a Model A, and all worked just fine. But I had never seen the live preview using this setup, since I never had a display on the RPi with the camera. I decided to see what I was missing so I connected the camera to a Model A I had already hooked up to a display (with everything off, of course). This was up to date with apt-get update / upgrade as of yesterday. Fired it up, but I just got
Code: Select all
    >raspistill -o image.jpg
    mmal: mmal_vc_component_create: failed to create component 'vc.ril.camera' (1:ENOMEM)
    mmal: mmal_component_create_core: could not create component 'vc.ril.camera' (1)
    mmal: Failed to create camera component
    mmal: main: Failed to create camera component


which I had not seen before. No idea why that happened; cables seemed correctly installed. I returned camera to other Model A board where it had worked before, and success, preview appeared. This is working in the basic console command line, I did not start X Windows. Then tried raspistill with long timeout, -t 99999 which I later stopped with Control-C. Bad news from this point on; camera would randomly refuse to respond, with the red light staying on. Shutdown, power off, reboot would make things better for a while, but then found SD card corruption. Boot message says could not read some block for several retries on boot; eventually worked, but then the command "ifconfig" caused the camera light to go on! (*) Clearly into a major malfunction now, so I am re-imaging the SD card from a backup (which fortunately I did a few days ago, using USBit). Posting here in case this helps anyone.

* UPDATE: just realized I still had a 'cron' task active that took a picture every 15 minutes, while I was also manually running raspistill at various times, so there may have been two instances of raspistill trying to run at once. Would like to think that should still not cause SD card corruption, but maybe that was the issue.


Certainly you cannot have two instances running at once (you'd get the error you describe), but I would not expect SD corruption if attempted.
Unemployed software engineer currently specialising in camera drivers and frameworks, but can put mind to most embedded tasks. Got a job in N.Cambridge or surroundings? I'm interested!
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 11718
Joined: Sat Jul 30, 2011 7:41 pm
by farmer » Wed Jun 12, 2013 1:53 pm
I also had this problem with the error
Code: Select all
mmal: mmal_vc_component_create: failed to create component 'vc.ril.camera' (1:ENOMEM)


in my case, the connector (the one with P5V04A SUNNY written on it) on the camera module was pulled loose, that probably happened when i tried to tape it onto a window. Just pushed it in again and now it's working again :)
Posts: 2
Joined: Sun Jun 09, 2013 10:54 pm
by mgvali » Thu Jun 20, 2013 1:29 pm
On field, installing, ensure the yellow connector labelled SUNNY is secured. There's a click when pushing the connector toward camera board.

Camera worked nicely until it started to skip frames (black frames in video), then failed completely the next day until I opened the enclosure to fix it.

Symptoms:
mmal: mmal_vc_component_create: failed to create component 'vc.ril.camera' (1:ENOMEM)

Can't say if it was not properly closed since factory or just somehow popped open while being handled, but still had some contact for a while when testing.
Posts: 1
Joined: Thu Jun 20, 2013 12:37 pm
by markyd » Wed Jul 03, 2013 12:43 pm
Hello I had the same issue with the camera board not working, lots of cable re-seating later and it worked. Suspect the small "Sunny" connector on the camera PCB to be honest .....
Posts: 38
Joined: Fri Jan 13, 2012 11:40 am
by dnhimelic » Wed Aug 28, 2013 9:56 pm
I had the exact same problem with my first camera board and in reading this post I found my problem.

Have you reseated the sensor itself on the camera board?
It had popped out just a little bit.
Works fine now...
Posts: 5
Joined: Thu Aug 01, 2013 12:18 am
by agnaedig » Sat Aug 31, 2013 1:12 am
Hi, i've just expirenced some problems with the raspi cam. "mmal: mmal_component_create_core: could not create component 'vc.ril.camera'"

I solve the problem changing the power adaptor, i realized it was the problem because it was working great until i needed to use a nokia 750mA ACDC for a moment, so i change it again with the official newarks adaptor 1 Amp and works great... hope this solve some problems for you....

Regards!
Posts: 1
Joined: Sat Aug 31, 2013 1:05 am
by spro504 » Fri Sep 27, 2013 5:56 pm
i ran into the same component failed, but i do not have the light turn on when i touch the ribbon cable, also i had my camera working before, but what happened is a shame. im using raspbian whezzy twice, i set up my pi with a battery in an ammo can with a camera hole, turned it sent a time lapse code to take a photo every 5 sec for 4 hours saw it was working and went and set it up in the park.
after two hours came home saw a photo of what seemed to be on the way back to the truck, but i couldnt do anything it seemed like it froze so i did what you never do to computers and unplugged the battery.... well sd card got messed up, it gets worse, as i decided to take a break my dog played and pulled the raspberry pi out the ammo can and yanked the ribbon cable out of the screwed down camera board, everything seemed ok as it always does reconnected everything and set it back up in the ammo can stuck my other sd card and started updating it, turned on the camera module and was about to go attempt the time lapse again when i got the "failed to create camera component" list, i think something got messed up but i thought i should share for others with the issue
Posts: 1
Joined: Fri Sep 27, 2013 5:44 pm
by Mansoor Ahmed » Sat Sep 28, 2013 10:49 am
Hello sir,

I am presently using Raspberry pi with camera, can i control the brightness and image capture and all using GPIO lines, if so please give me some idea regarding this.
thank you
Posts: 1
Joined: Thu Sep 19, 2013 11:26 am
by VeloSteve » Wed Nov 20, 2013 10:53 pm
Just one more "user experience" report.

I installed my new camera last night, and it worked fine.

It turns out that the instructions I followed were not the best, and I had not done an apt-get update and upgrade, so I did those AFTER the camera was working. The camera then would not work, with the "failed to create component 'vc.ril.camera' " message.

Naturally I thought that I had messed up something in software/firmware.

Wrong - after all kinds of checks and reboots didn't help, I detached the ribbon cable on both ends, detached the little connector on the camera board, and put everything back. Now it works fine. I'm guessing that the problem was the connector on the camera board.

I hardly touched the camera between the time when it first worked and when it didn't. That connector really needs to be more secure.
Posts: 5
Joined: Wed Oct 02, 2013 4:42 am
by donde » Thu Nov 21, 2013 5:37 pm
I have read only part of the posts about "Issue with getting camera to work".
I think this camera install procedure with motion is very good and understandable.

http://rbnrpi.wordpress.com/project-list/setting-up-wireless-motion-detect-cam/

Start off right from the beginning, installing the latest Wheezy and going from there following the above web site. Take it slow and easy and don't stop until done. Make a check sheet.
Posts: 79
Joined: Sat Feb 18, 2012 3:57 am
by aurangzaib » Sat Dec 14, 2013 9:32 am
I too had the same problem.
I have two 2 raspi.
Raspicam is working in one rpi but not with other, i used same memory card in both rpi. the non-working rpi was working with raspicam somedays ago nicely.
Posts: 2
Joined: Sat Aug 03, 2013 2:46 pm
by bantammenace2012 » Wed Jan 22, 2014 12:41 pm
Same error message for me. Here's what resolved it for me on this occasion.
1. sudo raspi-config, 5 DISABLE camera
2. shutdown and unplug p0wer
3. check ribbon cable is inserted properly at both ends
4. sudo raspi-config 5. ENABLE camera, reboot.
Posts: 59
Joined: Mon May 28, 2012 12:18 pm
by talon42 » Mon Apr 14, 2014 4:44 am
So similar issue to others with a bit of a twist. I have 2 cameras. One of which is a camera module from Arducam. I found that this particular camera module throws the error
'mmal: mmal_vc_component_create: failed to create component 'vc.ril.camera' (1:ENOMEM)"

if the disable_camera_led=1 is set in /boot/config.txt. It works fine if this line is removed. Checked cable. Running the most
recent Wheezy build. updated and upgraded.
Linux pi 3.10.25+ #622 PREEMPT Fri Jan 3 18:41:00 GMT 2014 armv6l GNU/Linux
Added into config.txt:
start_x=1 (already in)
start_file=start_x.elf
fixup_file=fixup_x.dat

if disabled_camera_led=1 then
running vcgencmd get_camera shows
supported=1 detected=0
if disabled_camera_led=0 or if the line is removed
supported=1 detected=1
Vendor claims this is identical to the "official" camera module (just has CS mount) so wondering if there is a defect or something else that could be done. Any ideas what else to check?
Posts: 3
Joined: Mon Apr 14, 2014 4:01 am
by 6by9 » Mon Apr 14, 2014 6:38 am
I would get on to the vendor of Arducam to confirm that they haven't done something funny and used the LED GPIO as a power control line for the camera itself. Certainly on the genuine PiCam it just goes to the LED, hence why it can be controlled independently of camera power.

If you're running "Linux pi 3.10.25+ #622 PREEMPT Fri Jan 3 18:41:00 GMT 2014", then you may have done 'apt-get udate', but you haven't done 'rpi-update'. The latest released kernel is 3.10.36+ and was released 4 April.
Ex-Broadcom engineer. The support I can provide now is limited - sorry.
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 598
Joined: Wed Dec 04, 2013 11:27 am
by talon42 » Tue Apr 15, 2014 2:14 pm
Updated to 3.10.37 this AM. Same issue.
Posts: 3
Joined: Mon Apr 14, 2014 4:01 am
by talon42 » Thu Apr 17, 2014 4:44 am
Response from vendor appears to indicate that there's a design flaw that will be fixed in the next revision.
Posts: 3
Joined: Mon Apr 14, 2014 4:01 am
by cweveritt » Tue Sep 16, 2014 3:09 am
jamesh wrote:I'm probably teaching grandma to suck eggs, but can I confirm from those having problems that the cable is well seat at both ends, the right way round, and the plastic tag is firmly engaged to clamp the cable in?

I don;t know what instructions you will have received, but here is a quick precis..

Pull up the black (on mine) tag on the top of the connector on the Pi itself. Slide in ribbon as far as it will go with the blue side facing the ethernet connector. Now firmly push down the black plastic tag. Ensure the cable doesn't move whilst doing this. Same process applies to the camera board itself, with blue side facing the black tag. Ensure cable is firmly gripped at both ends, is correctly insert at 90deg, and the right way round.

It also possible reseat the camera module itself if the above doesn't help. You can, very gently, with a fingernail, lever up the connector on the end of the short ribbon from the module, and remove the module completely. Blow on it to remove any fluff/debris, then gently reseat it again,making sure it's lined up correctly, and very gently press - you should feel it click in to place.


Pay close attention to the last paragraph above. I blew right by this and didn't catch it until I looked closely. What looks like a tag hanging off the camera is a connector which attaches the camera to the little pcboard. Mine had been knocked loose!!!
Posts: 4
Joined: Wed Oct 02, 2013 12:05 am