deejot
Posts: 15
Joined: Sun Nov 10, 2013 11:26 am

Firmware upgrade stops cam?

Sun Nov 10, 2013 11:47 am

Hi there,

I just did a firmware update via rpi-update and now my cam module doesn't want to take pictures anymore. Error message is

Code: Select all

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
No second instance of raspistill is running at that time.

Can anyone confirm that?

vcgencmd version says

Code: Select all

Nov  7 2013 16:45:47
Copyright (c) 2012 Broadcom
version 8573b0747a17baf22e97e08254737a13d80430dd (clean) (release)
Helpless,

Daniel

jamesh
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 23708
Joined: Sat Jul 30, 2011 7:41 pm

Re: Firmware upgrade stops cam?

Sun Nov 10, 2013 12:04 pm

That's a very recent firmware - there may be a problem, but no-one else has reported. Please check all the connections.
Principal Software Engineer at Raspberry Pi (Trading) Ltd.
Contrary to popular belief, humorous signatures are allowed. Here's an example...
"My grief counseller just died, luckily, he was so good, I didn't care."

deejot
Posts: 15
Joined: Sun Nov 10, 2013 11:26 am

Re: Firmware upgrade stops cam?

Sun Nov 10, 2013 12:16 pm

Thanks for the quick reply. Checked, looked ok, but nevertheless replugged the camera. But no effect. Would a strace help?

SnowLeopard
Posts: 106
Joined: Sun Aug 18, 2013 6:10 am

Re: Firmware upgrade stops cam?

Sun Nov 10, 2013 4:57 pm

I have that same firmware and the camera is working fine.
Not sure what to suggest... maybe run raspi-config to renable the camera just in case?
Maybe the output of sudo vcdbg syms |grep -i cam will show something useful?

deejot
Posts: 15
Joined: Sun Nov 10, 2013 11:26 am

Re: Firmware upgrade stops cam?

Sun Nov 10, 2013 8:01 pm

Re-enabling was the first thing I tried...

Code: Select all

$ sudo vcdbg syms| grep cam
0xdec02020         4 0x00000000 cam_alloc_alloc_count
0xdec02024         4 0x00000000 cam_alloc_arena_allocs
0x1ef01458         4 0x00000000 cam_alloc_base
0xdec02028         4 0x00000000 cam_alloc_disable
0x1ef0145c         4 0x00000000 cam_alloc_size
0xdec0202c         4 0x00000000 cam_alloc_total_arena_count
0xdec02030         4 0x00000000 cam_alloc_used
0x1ef01740         4 0x00000000 g_camera_pool_size
0x1ef01744         4 0x00000000 g_camera_pool_start
$

jamesh
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 23708
Joined: Sat Jul 30, 2011 7:41 pm

Re: Firmware upgrade stops cam?

Sun Nov 10, 2013 9:18 pm

It looks like a memory problem can you check the GPU memory split?
Principal Software Engineer at Raspberry Pi (Trading) Ltd.
Contrary to popular belief, humorous signatures are allowed. Here's an example...
"My grief counseller just died, luckily, he was so good, I didn't care."

deejot
Posts: 15
Joined: Sun Nov 10, 2013 11:26 am

Re: Firmware upgrade stops cam?

Sun Nov 10, 2013 9:49 pm

I think it's set to 128MB but I can't tell you definitely at the moment because I just reflashed my SD card with an older backup image. With this one the camera is working, so no hardware issue here.

deejot
Posts: 15
Joined: Sun Nov 10, 2013 11:26 am

Re: Firmware upgrade stops cam?

Sun Nov 10, 2013 10:34 pm

So, re-flashing back to the non-working installation was faster than expected...

It was set to 128. Just tried setting to 256, didn't help. Cam LED remains lit btw.

timgover
Posts: 8
Joined: Thu Nov 07, 2013 7:40 pm

Re: Firmware upgrade stops cam?

Sun Nov 10, 2013 10:38 pm

Please could you post the raspistill command line and the output of "sudo vcdbg log msg" after the failure ?

deejot
Posts: 15
Joined: Sun Nov 10, 2013 11:26 am

Re: Firmware upgrade stops cam?

Sun Nov 10, 2013 10:46 pm

No problem:

Code: Select all

$ raspistill -o testpic.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

$ sudo vcdbg log msg
001248.352: HDMI:Setting property pixel encoding to Default
001248.376: HDMI:Setting property pixel clock type to PAL
001248.400: HDMI:Setting property content type flag to No data
001248.422: HDMI:Setting property fuzzy format match to enabled
001249.710: hdmi: HDMI:hdmi_get_state is deprecated, use hdmi_get_display_state instead
001249.731: hdmi: HDMI:hdmi_get_state is deprecated, use hdmi_get_display_state instead
004594.944: vchiq_core: vchiq_init_state: slot_zero = 0x4f000000, is_master = 1
004599.573: hdmi: HDMI:hdmi_get_state is deprecated, use hdmi_get_display_state instead
004601.997: cma: cma_hwm is zero - disabling cma service
$ 

SnowLeopard
Posts: 106
Joined: Sun Aug 18, 2013 6:10 am

Re: Firmware upgrade stops cam?

Mon Nov 11, 2013 12:41 am

deejot wrote:I think it's set to 128MB but I can't tell you definitely at the moment because I just reflashed my SD card with an older backup image. With this one the camera is working, so no hardware issue here.
That must be somewhat of a relief :)
What's different between old and new versions? vcgencmd version, uname -a, and what raspivid version?

deejot
Posts: 15
Joined: Sun Nov 10, 2013 11:26 am

Re: Firmware upgrade stops cam?

Mon Nov 11, 2013 7:36 pm

SnowLeopard wrote: That must be somewhat of a relief :)
Absolutely... ;)
What's different between old and new versions? vcgencmd version, uname -a, and what raspivid version?
OK, here we go:

Not working:

Code: Select all

$ vcgencmd version
Nov  7 2013 16:45:47
Copyright (c) 2012 Broadcom
version 8573b0747a17baf22e97e08254737a13d80430dd (clean) (release)
$ uname -a
Linux campi 3.10.18+ #585 Thu Nov 7 15:16:15 GMT 2013 armv6l GNU/Linux
$ raspivid -v

raspivid Camera App v1.3.4

Width 1920, Height 1080, filename (null)
bitrate 17000000, framerate 30, time delay 5000
H264 Profile high
Wait method : Simple capture
Initial state 'record'


Preview Yes, Full screen Yes
Preview window 0,0,1024,768
Opacity 255
Sharpness 0, Contrast 0, Brightness 50
Saturation 0, ISO 0, Video Stabilisation No, Exposure compensation 0
Exposure Mode 'auto', AWB Mode 'auto', Image Effect 'none'
Metering Mode 'average', Colour Effect Enabled No with U = 128, V = 128
Rotation 0, hflip No, vflip No
ROI x 0.000000, y 0.000000, w 1.000000 h 1.000000
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

$
That older backup:

Code: Select all

$ vcgencmd version
Oct  2 2013 19:02:03
Copyright (c) 2012 Broadcom
version 27c5a63b0c74c287a4cfa24ebdfd5aa5051a8d7d (clean) (release)
$ uname -a
Linux raspicam 3.6.11+ #557 PREEMPT Wed Oct 2 18:49:09 BST 2013 armv6l GNU/Linux
$ raspivid -v -o videotest2

raspivid Camera App v1.3

Width 1920, Height 1080, filename videotest2
bitrate 17000000, framerate 30, time delay 5000
H264 Profile high
Preview Yes, Full screen Yes
Preview window 0,0,1024,768
Opacity 255
Sharpness 0, Contrast 0, Brightness 50
Saturation 0, ISO 0, Video Stabilisation No, Exposure compensation 0
Exposure Mode 'auto', AWB Mode 'auto', Image Effect 'none'
Metering Mode 'average', Colour Effect Enabled No with U = 128, V = 128
Rotation 0, hflip No, vflip No
ROI x 0.000000, y 0.000000, w 1.000000 h 1.000000
Camera component done
Encoder component done
Starting component connection stage
Connecting camera preview port to preview input port
Starting video preview
Connecting camera stills port to encoder input port
Opening output file "videotest2"
Enabling encoder output port
Starting video capture
Finished capture
Closing down
Close down completed, all components disconnected, disabled and destroyed

$

deejot
Posts: 15
Joined: Sun Nov 10, 2013 11:26 am

Re: Firmware upgrade stops cam?

Tue Nov 12, 2013 8:07 am

BTW, by apt-get update && apt-get upgrade as well as rpi-update of that old backup I get the same result, so my conclusion is that there is something coming onto my system that spoils it.

If there's something left to do to help debugging that, please tell me. But on the other hand, if I'm the only one facing this particular problem... :?

User avatar
DougieLawson
Posts: 36173
Joined: Sun Jun 16, 2013 11:19 pm
Location: Basingstoke, UK
Contact: Website Twitter

Re: Firmware upgrade stops cam?

Tue Nov 12, 2013 8:52 am

deejot wrote:If there's something left to do to help debugging that, please tell me. But on the other hand, if I'm the only one facing this particular problem... :?
Check the hardware. Check the cable is connected correctly (by removing it and re-installing not just a visual check).
Find another Pi, try your camera on that system.
Find another camera, try that on your Pi.
Note: Having anything humorous in your signature is completely banned on this forum. Wear a tin-foil hat and you'll get a ban.

Any DMs sent on Twitter will be answered next month.

This is a doctor free zone.

lice
Posts: 1
Joined: Tue Nov 12, 2013 12:16 pm

Re: Firmware upgrade stops cam?

Tue Nov 12, 2013 6:46 pm

I ran into the same problem.
After I updated to 3.10.18 with "rpi-update", I receive the same error message by calling raspistill

Here is the some backgroundinformation:

Code: Select all

uname -a
Linux raspberrypi 3.10.18+ #590 Mon Nov 11 21:26:42 GMT 2013 armv6l GNU/Linux

Code: Select all

vcgencmd version
Nov 11 2013 21:39:21 
Copyright (c) 2012 Broadcom
version b9af2b65bf40fad8c80783f770cb726586caa72d (clean) (release)

Code: Select all

sudo vcdbg syms | grep -i cam
0x1eeff7e4         4 0x00000000 __CAMERA_POOL_END
0x1eeff7e0         4 0x00000000 __CAMERA_POOL_START
0xdec02020         4 0x00000000 cam_alloc_alloc_count
0xdec02024         4 0x00000000 cam_alloc_arena_allocs
0x1ef01938         4 0x00000000 cam_alloc_base
0xdec02028         4 0x00000000 cam_alloc_disable
0x1ef0193c         4 0x00000000 cam_alloc_size
0xdec0202c         4 0x00000000 cam_alloc_total_arena_count
0xdec02030         4 0x00000000 cam_alloc_used
0x1ef01c20         4 0x00000000 g_camera_pool_size
0x1ef01c24         4 0x00000000 g_camera_pool_start

Code: Select all

raspivid -v

raspivid Camera App v1.3.4

Width 1920, Height 1080, filename (null)
bitrate 17000000, framerate 30, time delay 5000
H264 Profile high
Wait method : Simple capture
Initial state 'record'


Preview Yes, Full screen Yes
Preview window 0,0,1024,768
Opacity 255
Sharpness 0, Contrast 0, Brightness 50
Saturation 0, ISO 0, Video Stabilisation No, Exposure compensation 0
Exposure Mode 'auto', AWB Mode 'auto', Image Effect 'none'
Metering Mode 'average', Colour Effect Enabled No with U = 128, V = 128
Rotation 0, hflip No, vflip No
ROI x 0.000000, y 0.000000, w 1.000000 h 1.000000
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
Hope, that anyone can help

Thanks

Edit: After Downgrade to version 3.6.11 everything is fine and the camera works

SnowLeopard
Posts: 106
Joined: Sun Aug 18, 2013 6:10 am

Re: Firmware upgrade stops cam?

Tue Nov 12, 2013 8:04 pm

There are demo apps that use OpenMax instead of MMAL to access the camera. (https://github.com/tjormola/rpi-openmax-demos)
I would expect them to behave the same as raspistill/raspivid, but someone should test in case Murphy's Law has come into effect and they do not.
$ uname -a && vcgencmd version
Linux pi2 3.10.18+ #592 Tue Nov 12 23:18:39 GMT 2013 armv6l GNU/Linux
Nov 12 2013 23:39:45
Copyright (c) 2012 Broadcom
version 4aee5454c7955e7bc0bbb152ca4c0e26e75376e1 (clean) (release)
Update: FYI, latest version (shown above) works fine for me, but could swear I'm getting a tiny bit of flickering I wasn't getting just before the upgrade.
My impression is power is the issue... it is known that SD card power consumption varies (http://en.wikipedia.org/wiki/Secure_Dig ... onsumption) and the recent firmware changes are mostly relating to SD corruption issues, so could have an impact on available power.
Try a different power supply -- I have two identical "adafruit usb 501" and one is defective, so it can be frustrating!
http://elinux.org/R-Pi_Troubleshooting# ... r_problems shows how to measure power on the Pi while it's busy with a multimeter.

deejot
Posts: 15
Joined: Sun Nov 10, 2013 11:26 am

Re: Firmware upgrade stops cam?

Wed Nov 13, 2013 6:59 am

@lice: Thanks (in some way or another) for confirming.
SnowLeopard wrote:There are demo apps that use OpenMax instead of MMAL to access the camera. (https://github.com/tjormola/rpi-openmax-demos)
I would expect them to behave the same as raspistill/raspivid, but someone should test in case Murphy's Law has come into effect and they do not.
I may give it a go as well...
Update: FYI, latest version (shown above) works fine for me, but could swear I'm getting a tiny bit of flickering I wasn't getting just before the upgrade.
My impression is power is the issue... it is known that SD card power consumption varies (http://en.wikipedia.org/wiki/Secure_Dig ... onsumption) and the recent firmware changes are mostly relating to SD corruption issues, so could have an impact on available power.
Try a different power supply -- I have two identical "adafruit usb 501" and one is defective, so it can be frustrating!
http://elinux.org/R-Pi_Troubleshooting# ... r_problems shows how to measure power on the Pi while it's busy with a multimeter.
I measured between TP1 and TP2 and get a reading between 4.91V and 4.93V, regardless of what I'm doing, no visible drop below that when issuing the raspistill command. Is that already below the usable threshold in this case? My power supply is the one shown in the picture. It's rated 5V/5A, so should hopefully be good enough. Measuring here shows constant 5.01V (also during "shooting"). So this may point to a cabling issue between power supply and RPi which may be below optimum... :roll:

/EDIT: I may have to repeat measuring with the older backup, in order to locate a difference here.
Attachments
Netzteil_500.jpg
Netzteil_500.jpg (50.56 KiB) Viewed 14702 times

deejot
Posts: 15
Joined: Sun Nov 10, 2013 11:26 am

Re: Firmware upgrade stops cam?

Wed Nov 13, 2013 6:47 pm

OK, first thing I did was to tweak the output voltage of my power supply to 5.19V. That results in 5.01V between TP1 and TP2. Still, no working camera.

Just for my quite basic understanding of electronics: Are we talking about milliseconds of voltage drop? Is this generally measurable with a usual multimeter? Or would I need to get hold of a oscilloscope here?

kaos
Posts: 108
Joined: Mon Mar 26, 2012 8:14 pm

Re: Firmware upgrade stops cam?

Wed Nov 13, 2013 7:15 pm

Voltage glitches lasting milli- or even microseconds, can mess up electronics, and you are correct that you won't see such glitches on a normal multimeter, but filtering such glitches (as long as they are not too excessive) is what smoothing capacitors (C3 on the Raspi and probably a much larger one in your power supply) are supposed to cover. Given your results to date, I doubt that the power supply is to blame in your case. At the same time, I think we would have heard more about it if the latest firmware was causing problems for everyone, so there must be something special about your setup. How about software? What other software are you running or have installed? Could you make a fresh Raspbian install, with nothing but the camera software set up to see if that works? Another point; what is your memory split? I think JamesH was wondering elsethread if some new functionality of the camera might require more than 128MB for the GPU.

--
Regards, Kári.

deejot
Posts: 15
Joined: Sun Nov 10, 2013 11:26 am

Re: Firmware upgrade stops cam?

Wed Nov 13, 2013 9:30 pm

Thanks Kári for your comments.

gpu_mem was set to 128 and 256 with no effect.

I just did a fresh install of Raspian using NOOBS 1.2.1 (cam works) and then apt-get update/upgrade and rpi-update, cam still works.

Code: Select all

pi@raspberrypi ~ $ uname -a
Linux raspberrypi 3.10.18+ #594 PREEMPT Wed Nov 13 17:59:34 GMT 2013 armv6l GNU/Linux
pi@raspberrypi ~ $ vcgencmd version
Nov 12 2013 23:39:45
Copyright (c) 2012 Broadcom
version 4aee5454c7955e7bc0bbb152ca4c0e26e75376e1 (clean) (release)
pi@raspberrypi ~ $
Apart from standard, at this moment just the 8192cu module for the wifi plug is loaded. OK, what else is my RPi supposed to do? I have some DS18B20 temperature sensors attached to measure temperature, let's try this now. And... Bingo.

Code: Select all

pi@raspberrypi ~ $ raspistill -v -o test_.jpg

raspistill Camera App v1.3.5

Width 2592, Height 1944, quality 85, filename test_.jpg
[...lines omitted...]
Connecting camera stills port to encoder input port
Opening output file test_.jpg
Enabling encoder output port
Starting capture 0
Finished capture 0
Closing down
Close down completed, all components disconnected, disabled and destroyed

pi@raspberrypi ~ $ sudo modprobe w1_gpio
pi@raspberrypi ~ $ raspistill -v -o test_w1_gpio.jpg

raspistill Camera App v1.3.5

Width 2592, Height 1944, quality 85, filename test_w1_gpio.jpg
[...lines omitted...]
ROI x 0.000000, y 0.000000, w 1.000000 h 1.000000
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@raspberrypi ~ $
So, 1wire seems to be the showstopper here. @Lice, do you also use 1wire?

SnowLeopard
Posts: 106
Joined: Sun Aug 18, 2013 6:10 am

Re: Firmware upgrade stops cam?

Wed Nov 13, 2013 10:01 pm

Good job!
At this point, I'm guessing you should post an issue on Git (https://github.com/raspberrypi/firmware) since it is very specific to 1-wire and camera combination. Probably link to this thread to show all the other testing you've gone through.

deejot
Posts: 15
Joined: Sun Nov 10, 2013 11:26 am

Re: Firmware upgrade stops cam?

Thu Nov 14, 2013 6:33 am

OK, opened an issue there.

Difference between Nov 7 and Nov 13 firmwares now is that the camera now doesn't seem to do metering now, LED now just flashes, turns off and the error message appears instantly.

User avatar
jbeale
Posts: 3494
Joined: Tue Nov 22, 2011 11:51 pm
Contact: Website

Re: Firmware upgrade stops cam?

Thu Nov 28, 2013 5:56 am

I have this problem too. I do not have 1-wire. I've got a usb-wifi adaptor and that's it. Camera on my Model A was working fine until today when I did rpi-update, reboot, apt-get update, apt-get upgrade, raspi-config (enable camera), reboot. Now I get

Code: Select all

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
Note that I still have raspivid v1.2, shouldn't the update process have updated that?

Code: Select all

pi@rp5 ~ $ uname -a
Linux rp5 3.6.11+ #538 PREEMPT Fri Aug 30 20:42:08 BST 2013 armv6l GNU/Linux
pi@rp5 ~ $ vcgencmd version
Sep  1 2013 23:27:46
Copyright (c) 2012 Broadcom
version 4f9d19896166f46a3255801bc1834561bf092732 (clean) (release)
pi@rp5 ~ $ sudo vcdbg syms | grep -i cam
0x0eefdaa4         4 0x00000000 __CAMERA_POOL_END
0x0eefdaa0         4 0x00000000 __CAMERA_POOL_START
0xcec02020         4 0x00000001 cam_alloc_alloc_count
0xcec02024         4 0x00000000 cam_alloc_arena_allocs
0x0eeffb98         4 0x00000000 cam_alloc_base
0xcec02028         4 0x00000000 cam_alloc_disable
0x0eeffb9c         4 0x00000000 cam_alloc_size
0xcec0202c         4 0x00000000 cam_alloc_total_arena_count
0xcec02030         4 0x00000000 cam_alloc_used
0x0eeffe80         4 0x00000000 g_camera_pool_size
0x0eeffe84         4 0x00000000 g_camera_pool_start
pi@rp5 ~ $ lsmod
Module                  Size  Used by
snd_bcm2835            16432  0
snd_pcm                77728  1 snd_bcm2835
snd_seq                53482  0
snd_timer              20110  2 snd_pcm,snd_seq
snd_seq_device          6462  1 snd_seq
snd                    58744  5 snd_bcm2835,snd_timer,snd_pcm,snd_seq,snd_seq_device
snd_page_alloc          5169  1 snd_pcm
8192cu                490361  0
leds_gpio               2243  0
led_class               3570  1 leds_gpio

pi@rp5 ~ $ raspivid -v

raspivid Camera App v1.2

Width 1920, Height 1080, filename (null)
bitrate 17000000, framerate 30, time delay 5000
Preview Yes, Full screen Yes
Preview window 0,0,1024,768
Opacity 255
Sharpness 0, Contrast 0, Brightness 50
Saturation 0, ISO 400, Video Stabilisation No, Exposure compensation 0
Exposure Mode 'auto', AWB Mode 'auto', Image Effect 'none'
Metering Mode 'average', Colour Effect Enabled No with U = 128, V = 128
Rotation 0, hflip No, vflip No
ROI x 0.000000, y 0.000000, w 1.000000 h 1.000000
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
UPDATE: I have ruled out a hardware problem because I swapped in a different SD card and the camera is working again. On this one I have

Code: Select all

pi@rp2 ~ $ uname -a
Linux rp2 3.6.11+ #538 PREEMPT Fri Aug 30 20:42:08 BST 2013 armv6l GNU/Linux
pi@rp2 ~ $ vcgencmd version
Sep  1 2013 23:27:46
Copyright (c) 2012 Broadcom
version 4f9d19896166f46a3255801bc1834561bf092732 (clean) (release)
pi@rp2 ~ $ sudo vcdbg syms | grep -i cam
0x0eefdaa4         4 0x00000000 __CAMERA_POOL_END
0x0eefdaa0         4 0x00000000 __CAMERA_POOL_START
0xcec02020         4 0x00000000 cam_alloc_alloc_count
0xcec02024         4 0x00000000 cam_alloc_arena_allocs
0x0eeffb98         4 0x00000000 cam_alloc_base
0xcec02028         4 0x00000000 cam_alloc_disable
0x0eeffb9c         4 0x00000000 cam_alloc_size
0xcec0202c         4 0x00000000 cam_alloc_total_arena_count
0xcec02030         4 0x00000000 cam_alloc_used
0x0eeffe80         4 0x00000000 g_camera_pool_size
0x0eeffe84         4 0x00000000 g_camera_pool_start
pi@rp2 ~ $ lsmod
Module                  Size  Used by
snd_bcm2835            16432  0
snd_pcm                77728  1 snd_bcm2835
snd_seq                53482  0
snd_timer              20110  2 snd_pcm,snd_seq
snd_seq_device          6462  1 snd_seq
snd                    58744  5 snd_bcm2835,snd_timer,snd_pcm,snd_seq,snd_seq_device
snd_page_alloc          5169  1 snd_pcm
8192cu                490361  0
leds_gpio               2243  0
led_class               3570  1 leds_gpio
pi@rp2 ~ $ raspivid -v

raspivid Camera App v1.3.7

Width 1920, Height 1080, filename (null)
bitrate 17000000, framerate 30, time delay 5000
H264 Profile high
H264 Quantisation level 0, Inline headers No
Wait method : Simple capture
Initial state 'record'


Preview Yes, Full screen Yes
Preview window 0,0,1024,768
Opacity 255
Sharpness 0, Contrast 0, Brightness 50
Saturation 0, ISO 0, Video Stabilisation No, Exposure compensation 0
Exposure Mode 'auto', AWB Mode 'auto', Image Effect 'none'
Metering Mode 'average', Colour Effect Enabled No with U = 128, V = 128
Rotation 0, hflip No, vflip No
ROI x 0.000000, y 0.000000, w 1.000000 h 1.000000
mmal: mmal_vc_port_parameter_set: failed to set port parameter 64:0:ENOSYS
mmal: Function not implemented
Camera component done
mmal: mmal_vc_port_parameter_set: failed to set port parameter 48:2:ENOSYS
mmal: failed to set INLINE HEADER FLAG parameters
Encoder component done
Starting component connection stage
Connecting camera preview port to preview input port
Starting video preview
Connecting camera stills port to encoder input port
Enabling encoder output port
Closing down
Close down completed, all components disconnected, disabled and destroyed
Just for completeness I downloaded and compiled the current main-branch raspivid on the non-working SD card. Now it is 1.3.6 but it still doesn't work.

Code: Select all

pi@rp5 ~/userland/userland-master $ raspivid -v

raspivid Camera App v1.3.6

Width 1920, Height 1080, filename (null)
bitrate 17000000, framerate 30, time delay 5000
H264 Profile high
H264 Quantisation level 25, Inline headers No
Wait method : Simple capture
Initial state 'record'


Preview Yes, Full screen Yes
Preview window 0,0,1024,768
Opacity 255
Sharpness 0, Contrast 0, Brightness 50
Saturation 0, ISO 0, Video Stabilisation No, Exposure compensation 0
Exposure Mode 'auto', AWB Mode 'auto', Image Effect 'none'
Metering Mode 'average', Colour Effect Enabled No with U = 128, V = 128
Rotation 0, hflip No, vflip No
ROI x 0.000000, y 0.000000, w 1.000000 h 1.000000
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
Last update: I did apt-get update, apt-get upgrade, rpi-update on the second SD card and the camera still works. So- a mystery about the first card.

User avatar
with ice cream
Posts: 164
Joined: Mon Jul 30, 2012 7:25 am

Re: Firmware upgrade stops cam?

Mon Dec 09, 2013 9:11 am

An upgrade also rendered my camera inoperative:

Code: Select all

$ raspivid -v

raspivid Camera App v1.3.7

Width 1920, Height 1080, filename (null)
bitrate 17000000, framerate 30, time delay 5000
H264 Profile high
H264 Quantisation level 0, Inline headers No
Wait method : Simple capture
Initial state 'record'


Preview Yes, Full screen Yes
Preview window 0,0,1024,768
Opacity 255
Sharpness 0, Contrast 0, Brightness 50
Saturation 0, ISO 0, Video Stabilisation No, Exposure compensation 0
Exposure Mode 'auto', AWB Mode 'auto', Image Effect 'none'
Metering Mode 'average', Colour Effect Enabled No with U = 128, V = 128
Rotation 0, hflip No, vflip No
ROI x 0.000000, y 0.000000, w 1.000000 h 1.000000
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
motion also fails:

Code: Select all

$ sudo motion -n -c /etc/motion.conf
[-1242795168] [NTC] [ALL] conf_load: Processing thread 0 - config file /etc/motion.conf
[-1242795168] [NTC] [ALL] motion_startup: Motion mmaltest Started
[-1242795168] [NTC] [ALL] motion_startup: Logging to syslog
[-1242795168] [NTC] [ALL] motion_startup: Using log type (ALL) log level (WRN)
[1] [ALR] [VID] mmalcam_start: MMAL Camera thread starting... for camera (vc.ril.camera) of 1024 x 576 at 2 fps
[1] [ALR] [VID] mmalcam_start: MMAL Camera using video capture
mmal: mmal_vc_component_enable: failed to enable component: ENOSPC
[1] [ERR] [VID] camera component couldn't be enabled
[1] [ALR] [VID] MMAL Camera cleanup
[1] [WRN] [ALL] motion_init: Could not fetch initial image from camera Motion continues using width and height from config file(s)
[1] [WRN] [ALL] motion_loop: Retrying until successful connection with camera
Firmware before and after:

Code: Select all

## before
$ uname -a
Linux berry 3.6.11+ #538 PREEMPT Fri Aug 30 20:42:08 BST 2013 armv6l GNU/Linux
$ /opt/vc/bin/vcgencmd version
Sep  1 2013 23:27:46
Copyright (c) 2012 Broadcom
version 4f9d19896166f46a3255801bc1834561bf092732 (clean) (release)

## after
$ uname -a
Linux berry 3.10.22+ #606 PREEMPT Thu Dec 5 18:16:13 GMT 2013 armv6l GNU/Linux

$ /opt/vc/bin/vcgencmd version
Dec  2 2013 20:30:23
Copyright (c) 2012 Broadcom
version 0334d765c5cb144589b4d7a4ac68ae8f136491e1 (clean) (release)
Apart from a downgrade, what can be done?

Redsandro
Posts: 27
Joined: Mon Nov 25, 2013 7:19 pm
Location: The Netherlands
Contact: Website

Re: Firmware upgrade stops cam?

Sun Oct 26, 2014 4:02 pm

I now have the same problem.

I last touched my Raspberry Pi in 2013. A year ago. Too much little things that broke it, needing me to invest time, let me leave it alone. Today I thought: Let's play around with some updated packages.

First thing I did, make some pictures. I - stupidly, if it ain't broke, don't fix it - ran

Code: Select all

apt-get update && apt-get upgrade && rpi-update
Went from firmware #600 to firmware #717, and the camera is now broken. Wow.

I'll try again in 2015.

Return to “Camera board”