So it is running for the requisite 30s, then trying to stop (preview disapears), but is failing to stop the camera. Odd. I've not seen that before.AndyQ wrote:Running:
raspistill -t 30000 - runs fine and exits nicely.
raspistill -d -t 30000 - runs for about 20 seconds then preview freezes, errors appear then after approx 10 more seconds preview window disappears but raspistill doesn't exit. Need to reboot in order to switch the camera off or run raspistill/raspivid again.
Code: Select all
[email protected] ~ $ 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
Hmm. Can you try the very latest build of the camera apps? You might need to build yourself - not sure which version is in the update. I tried verylong with that and couldn't get it to go wrong.GekkePrutser wrote:Sorry to drag up this old topic but I'm seeing the same thing - the camera locking up. A reboot fixes it, but it's not a handy fix and sometimes it takes a while before I notice.
It seems to happen 'sometimes' intermittently, however I can replicate it every single time by using the 'verylong' exposure prefix. Taking a picture with raspistill and verylong, just ends up in it hanging forever, then when I finally kill the process the camera light just stays on forever until I reboot. And the camera doesn't work anymore from that point on (subsequent calls to raspistill end up hanging forever, which ends up in quite a few processes since I have them done periodically). This is something I can check for anyway by using a lock file but it shouldn't hang, really..
It would be great if I could reset this GPIO pin every time before I start taking a picure so I know the camera is in a sane state.
And that is with the latest app? (sudo rpi-update gets it)maddogdave wrote:I've tried the 'verylong' parameter and if the light levels were high then I got a normally exposed picture saved after the standard 5 second preview. When I lowered the light level the camera froze on the preview screen and I needed to reboot. Wondering if there is some kind of limit / threshold on either the light level or maximum exposure time that causes a conflict with verylong. Should the exposure time out and save the file after a preset maximum time (say 4 seconds / 30 seconds or so) or is the module waiting and not sensing enough light and therefore not completing the command.
All you have to do is go to the schematic of the Raspberry-Pi board and that tells you it is GPIO27 or GPIO5.....(or post which GPIO controls the camera power).
GPIO5 is the one I use to switch the camera LED on and off. It doesn't switch the camera off, so I'd bet on GPIO27 as well.Gert van Loo wrote:All you have to do is go to the schematic of the Raspberry-Pi board and that tells you it is GPIO27 or GPIO5.....(or post which GPIO controls the camera power).
As GPIO5 has the name "CAM_CLK" my bet is on the GPIO27 pin.
I really need to start reading things more carefully!Gert van Loo wrote:Gert van Loo wrote:Could be, I used the rev-1 schematic.Would that be different for Rev 1 and Rev 2 Pis Gert, since 27 is now on the P1 header?
I have not checked rev2.