Anything special required to enable new camera on new zero?

[pauly]

Just got the new pi zero and the v2 camera. First tried MotionEyeOS like I have on my other pi's and while it installs ok it doesn't recognise the camera. Fair enough the hardware is new and the MotionEyeOS developer doesn't have a zero to debug.

So then swapped the sd card out of my other pizero* (running raspbian jessie), enabled the camera using raspi-config and tried to take a pic, but no:

Code: Select all

$ raspistill -o /tmp/raspi.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
mmal: Camera is not enabled in this build. Try running "sudo raspi-config" and ensure that "camera" has been enabled

I've updated the version of raspi-config and tried again but still getting "camera is not enabled in this build". Anyone got this working yet? Have I missed something obvious? I've double checked the ribbon connector is in right way and the connections look good and straight.

I'm just going to apt-get update & upgrade & dist-upgrade see if that helps, and then try swapping the v2 camera for an older one.

*ooh yeah my other computer cost £4 too, when are those stickers going to be available?

[gregeric]

I'm just going to apt-get update & upgrade & dist-upgrade see if that helps, and then try swapping the v2 camera for an older one.

I expect you'll be reporting back here soon to say that did the trick - newer firmware is required to let the blob know that the Zero is camera-capable, & on which GPIO to communicate with it.

[Gavinmc42]

run sudo raspistill -d, to see if the camera works,
raspi-config camera enabled?

[gordon77]

NoIR v1.3 and v2.1 cameras work with my new Zero.

Simply swapped the sd card from my Pi2B, built from the latest Raspbian download.

[pauly]

I'm just going to apt-get update & upgrade & dist-upgrade see if that helps, and then try swapping the v2 camera for an older one.

I expect you'll be reporting back here soon to say that did the trick - newer firmware is required to let the blob know that the Zero is camera-capable, & on which GPIO to communicate with it.

You're not wrong, dist-upgrade did the trick. I guess I'll have to wait for MotionEyeOS to catch up but at least I can play in the meantime...
Thanks @Gavinmc42 also

[6by9]

Support was added to the firmware back at about the time Eben first announced that there was a new feature, so any firmware image since then should support it.
Easiest test is "vcgencmd get_camera" and see if it says supported is 0 or 1. If 0, you need newer firmware.

Of course if you're using a V2 sensor (8MP IMX219), then I'd advise you to grab the latest Raspbian to get the maximum goodness.

[doughadfield]

Hi all, I'm having exactly the same issue, with RPi Zero and (old) camera. Just got my new camera cables this morning the the post, so have been playing... I have a bunch of MotionEyeOs cameras around the place, using Model A boards, so was really looking forward to using Zeros, for their larger memory, faster cpu and much smaller footprint (the zero must be just about the IDEAL camera driver board!!). But I've hit the same problem as above. I have the same issue with a Raspian Lite image I downloaded from the raspberrypi.org website yesterday. So I'm hoping an upgrade to this image will make that work, then I'll try copying the firmware image files across to a MotionEyeOs image - wish me luck!!

Doug

[pauly]

Good luck! We need an update of MotionEyeOS in order for it to work on the new Zero. I am going to try Rasbian with just MotionEye installed on it while I wait for that.