camera module mmal error - help!!

[amboque]

Having no luck with my new camera board. Just received last few days and not quite sure what is the problem. I tried raspistill -o -v test.jpg I get the following output that never goes away and the camera light turns red and never turns off with mmal error shown below

raspistill Camera App v1.3.8

Width 2592, Height 1944, quality 85, filename test.jpg
Time delay 5000, Raw no
Thumbnail enabled Yes, width 64, height 48, quality 35
Link to latest frame enable no
Full resolution preview no
Capture method: Single Capture

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 1.000000, z 1.000000
Camera component done
Encoder component done
Starting component connection stage
Connecting camera preview port to video render
Connecting camera stills port to encoder input port
Opening output file test.jpg
Enabling encoder output port
Starting capture 0
mmal: No data received from sensor. Check all connections, including the Sunny one on the camera board

I have also tried

-reconnecting the cable couple of time
-reseating sunny (many times)
-enable/disable camera in raspi-config + reboot
- update (apt-get update/upgrade and rpi-update)

I'm using a 2A 5V adapter so I dont think power supply is the problem.

also run vcngencmd get_camera
the output is:
supported=1 detected=1
so i think the board knows the camera is there.

Any other thing that i missed or is it that i happen to have a dodgy camera

[jamesh]

I think you mean raspistill -v -o test.jpg?

If you have tried all the cable connections etc, including Sunny, then you may have a defective module (or a defective CSI port on the Pi itself). Note that the camera can be detected (that's done via I2C) but may still not be able to receive image data (done via CSI-2) if something is broken.

[amboque]

I think you mean raspistill -v -o test.jpg?.

yes i mean that. thanks for your reply

I just tried it on a different pi board. still giving the same error. looks like its not the CSI port.
maybe the cable? I'm gonna try formatting and reinstalling raspbian. Not sure how its going to help but i hope it works. save me from the hassle of trying to get a new camera module.

[Fonzi]

I have this exact same issue. Camera worked perfectly in the last year, with a first batch Pi B and with the latest Pi 2.
Now, it stopped working just leaving the LED lit but no image. With the verbose flag, i started getting:

mmal: Received unexpected camera control callback event, 0x4f525245

After some updates (OS and firmware) the only thing i get is "mmal: no data received from sensor. check all connections, including the sunny one on the camera board"

GPU has 256MB and PSU is 2A. I've even tried to underclock the board in order to avoid power issues.
I swapped the connector and checked if everything is firmly inserted into place.

My last test was to disconnect the small connector on the camera itself and raspistill detects the camera is missing. So, it looks like the board is fine but the camera is fried.

In my case, this was probably due to static. I moved my board in a van without any kind of special care so, you have that...
What i'm really afraid is reading some users with multiple modules, and they seem to be dying one after another.

[chof747]

Same issue with my camera module and a RPi Model B Rev.2

The Voltage between TP1/TP2 is 4.9 dropping to somewhat around 4.8 when running raspistill. Tested 2 cameras and both have the same issue. How can I check if the Port on the Pi is the issue.

uname - a returns:

Code: Select all

Linux raspberrypi 3.18.11+ #777 PREEMPT Sat Apr 11 17:24:23 BST 2015 armv6l GNU/Linux

output of lsmod:

Code: Select all

Module                  Size  Used by
arc4                    1964  0 
ecb                     2279  0 
md4                     3587  0 
md5                     2045  0 
hmac                    3067  0 
nls_utf8                1443  0 
cifs                  310275  0 
w1_therm                3325  0 
i2c_dev                 6709  0 
snd_bcm2835            21157  0 
snd_pcm                90778  1 snd_bcm2835
snd_seq                61097  0 
snd_seq_device          7209  1 snd_seq
snd_timer              23007  2 snd_pcm,snd_seq
snd                    66325  5 snd_bcm2835,snd_timer,snd_pcm,snd_seq,snd_seq_device
i2c_bcm2708             6200  0 
spi_bcm2708             6018  0 
w1_gpio                 4287  0 
wire                   31248  2 w1_gpio,w1_therm
cn                      5756  1 wire
uio_pdrv_genirq         3666  0 
uio                     9897  1 uio_pdrv_genirq

vcgencmd get_camera:

Code: Select all

supported=1 detected=1

/boot/config.txt:

Code: Select all

# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1

# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
#disable_overscan=1

# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720

# uncomment if hdmi display is not detected and composite is being output
#hdmi_force_hotplug=1

# uncomment to force a specific HDMI mode (this will force VGA)
#hdmi_group=1
#hdmi_mode=1

# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
#hdmi_drive=2

# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=4

# uncomment for composite PAL
#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800

# for more options see http://elinux.org/RPi_config.txt
start_x=1
gpu_mem=128
dtparam=i2c_arm=on
dtparam=spi=on
dtoverlay=w1-gpio

can somebody advice if there is any software / config issue?

Thx

Chris

[hungrycaiman]

Hi!

The exact same issue here:
mmal: No data received from sensor. Check all connections, including the Sunny one on the camera board

It's the first time i'm using the camera so i can't really tell if it worked before.

Linux raspberrypi 3.18.11+ #781 PREEMPT Tue Apr 21 18:02:18 BST 2015 armv6l GNU/Linux

Has someone figured it out? Thanks!

[zip000]

I'm seeing the same problem: mmal: No data received...

My camera worked last time I checked, but it has sat on a shelf for a while. One possibility in my case is that when I was plugging it in this morning, I absentmindedly plugged it into the Display Serial Interface instead of the CSI.

Does anyone know whether this could this have fried it? Or is it more likely a static problem or something else?

[ciudad]

Hello,

"I absentmindedly plugged it into the Display Serial Interface instead of the CSI."

You're not the only one... so did I (I haven't noticed it could be plugged in different places) ;o) And I got the same result !
The cable looks ok and I tested the camera on another board : I still have "mmal: No data received from sensor..."
Anyway to make the camera work again ?

[daveculp]

I am having the exact same issue with the exact same error messages. The camera worked before and now it doesnt. I am using a RPi 2.

Did a recent update break something?

[daveculp]

I have tried a few things to get it to work:

1. Made certain everything was up to date by running apt-get update and apt-get upgrade
2. I tried on my A+ and received the exact same errors.
3. I disabled i2C and SPI via raspi-config and received the same errors. Some googling led me to believe i2c may interfere with the camera.
4. Mildly cleaned the connectors on the camera cable.

Nothing worked. I have to assume that maybe my camera module went belly up. I just ordered a new one.

[kupo88]

hi,
i'm quite now to raspberry but i pretty know how to use...

i' ve bought a pi camera noir and it doesn't work. i've the same mmal error (check connector bla bla bla).

i was seeing around that the new 3.18.x kernel might be the problem... and i' m on that kernel because i've updated recently

i've also seen that trying to downgrade to 3.12x kernel should work, but when i downgrade with rpi update CODE_FIRMWARE the pi doesn't boot anymore. I've the last raspy model, and everytime i try to downgrade to EVERY firmware it stop booting. NO error during firmware downgrading.

So, what you suggest ?

camera module is broken?
why pi doesn't seem to accept kernel downgrade ?
ps: i've last noobs and raspbian version.

please tell me something...
thx to all in advice....

[PiLarz]

Hi.
I'm a Pi noob and i also got this error message. Can't get the camera to work.
"Mmal: no data received from sensor. check all connections, including the sunny one on the camera board".

I've tried everything mentioned in this thread. Hardware problem maybe? Has anyone tried with a different camera? Thinking of returning it and try another one..

[MoNurk]

Any resolution on this issue?

I've tried with two different cameras and I get the same error with both.
Also tried using a different PSU, fresh Raspbian build, but nothing helped
"No data received from sensor. Check all connections, including the Sunny one on the camera board"

[6by9]

If you get this message you have a hardware issue - either a dodgy connection, or a failed unit. I'm not sure how you expect anyone to resolve this magically for you via software.

Check:

• the SUNNY connector - they are known to partially disconnect.
• Check both ends of the flexi. Disconnect and reconnect them both. Check for any sharp bends in it as they can crack the tracks. Replace if necessary.
• Check your power supply is up to the job. Powering up the camera takes about 300mA IIRC, and can cause the power supply lines to drop too low to actually function.
• If possible check against another Pi and/or another Pi camera to identify which is causing issue.
  There has been at least one confirmed case of the CSI-2 connector on the main Pi having duff solder joints.
  The sensor modules are static sensitive and originally were intended to be embedded permanently in a mobile phone rather than exposed on a board. Most of the logic lines have some buffering on the small PCB so are likely to survive static shocks, but the CSI-2 lines go direct to the sensor so are going to be more sensitive.

If the camera fails to start up at all, then the sensor isn't detected on the I2C bus. If you get this error of no data received, then the CSI-2 lanes are at fault.

Yes, the message changed back in March because I got fed up with people reporting MMAL error 0x4f525245 having failed to search on the forums. It now tells you pretty much what the error is, but people still come here to ask - grrr!

I've had one (abused) sensor fail on me in the last few days with these errors. As I happen to have spares of most bits kicking around I did some swapping, and in my case it is the OV5647 module itself that has failed. It has been swapped between boards many times and floating around in a rucksack (generally in an antistatic bag) for the past few months, so it really is abuse.

[charliek]

More for the record, I have the same thing with a Pi NoIR camera. I landed this thread (or one like it) a while back, when the error message was more cryptic (MMAL error 0x4f525245).

Now that I've got other pi's (an A+, a B+ and now a B2), and a regular camera, I've been able to swap stuff around a little more. In my case, the problem seems to be with the camera-end of the board. I've reseated the sunny connecter many times, but I've not swapped the actual camera module itself because I'm reluctant to risk b0rking my other working one.

The camera worked twice, last year, and has been giving the error ever since.

As an ex IT technician, I am fairly confident that I have been suitably careful and haven't abused it in any way, but of course a rogue static discharge or a bump of some kind is always possible.

Given that there seem to be many instances of these errors, would the board benefit from some kind of revision?

Are the NoIR camera sensor modules available for purchase seperately?

[alexmead]

I have spent a long time working through this error with several cameras and several RPi B boards. I am convinced at this point that somehow the connector is getting fried on the RPi board.

I originally had one board (Board 1) and one camera (Camera 1). Camera 1 worked for a bit with board 1, then started reporting the "MMAL error 0x4f525245" error. I ordered a new camera (Camera 2) thinking I fried Camera 1 as many in the forums spoke of. Right out of the box Camera 2 didn't work with Board 1, same error "MMAL error 0x4f525245". I also tried reloading the OS from scratch for camera 1 and camera 2 and board 1, this didn't work.

I then got the idea maybe it's the board 1, so I ordered two more RPi B's (Board 2 and Board 3). Board 2 worked with both camera 1 and camera 2 for a while, then it started reporting the new error "check the connector", which is apparently the same error with a changed message to be more informative (this is according to 6by9 above). I then decided to try very carefully to see if board 3 worked with the camera 1 and camera 2. Board 3 worked right out of the box, I even used the same SD card as was running on board 2 when I started have problems.

Given the extensive testing of RPi boards and cameras I am pretty sure something is happening with the connector on the RPi. The cameras still work on new boards even after they report this issue on old boards.

Does anyone have any idea why the connectors are the failing component? "duff solder joints" is suggested by 6by9. What does this mean? Is this a manufacture defect? I've been very carefully with the boards and am having trouble, I assure you my behavior has been within reasonable working expectations. Is the camera module just that sensitive?

Any thoughts on making these cameras work without buying new RPi's would be appreciated! Thanks!

[6by9]

Does anyone have any idea why the connectors are the failing component? "duff solder joints" is suggested by 6by9. What does this mean? Is this a manufacture defect?

viewtopic.php?f=43&t=109153
Only 1 confirmed instance. No further confirmed instances, and it would result in a Pi never working with the camera, not a failure after time.

[Heinz.Benjamin]

I have experienced the same issue. Camera works fine on another Pi but not on mine anymore, though I handled it with care.

Too bad, this board is so unreliable.

[Heinz.Benjamin]

If you get this message you have a hardware issue - either a dodgy connection, or a failed unit. I'm not sure how you expect anyone to resolve this magically for you via software.

I think, the point of the question was to find out, whether we are dealing with a hardware or software problem and how to resolve it. So thanks for your kind answer. Knowing now, that it is a hardware problem nobody would expect it to be "magically resolved" through software.

My camera also stopped working for no reason, but works fine on another board, which just causes me to get a new Pi. It's a pity, that this product is so unreliable.
Maybe the engineers in this forum should report these quality issues and help to resolve them instead of insulting their customers.

[texy]

I think you will find that many thousands of camera boards have sold, and 5+ million Pi's also. The number of reported failures in respect of units sold is extremely small - hardly what I would call 'unreliable'.
If you think you have a genuine hardware issue, then please return it to your supplier for a replacement.
Texy

[JohnCollis]

I started to get this error suddenly this afternoon after the camera had been working earlier. The same message was on two different machines. I think the cable was dislodged from the camera module, after I replaced it the message appeared, this was while the module was powered.

[DonVito]

I have exactly the same problem. I receive the following : mmal: No data received from sensor. Check all connections, including the Sunny one on the camera board . I checked the connections seems to be normal. The strange thing is that in the first use of the camera everything was fine, I took pictures I did a real time video streaming via VLC was great. Although, the next day of use couldn't receive data and received the error that I mentioned above. I don't think that is actually a software problem or firmware I think that is a hardware problem. Maybe these modules are faulty. Not sure yet. Anyway, before I order the new one , could please someone to give an idea of solution ? Thank you! D.V

[sfar67]

I am also having this same problem. It worked last month. Very disappointed

Code: Select all

>>> import picamera
>>> camera = picamera.PiCamera()
>>> Traceback (most recent call last):
  File "_ctypes/callbacks.c", line 314, in 'calling callback function'
  File "/usr/lib/python2.7/dist-packages/picamera/camera.py", line 129, in _control_callback
    "Received unexpected camera control callback event, 0x%08x" % buf[0].cmd)
picamera.exc.PiCameraRuntimeError: Received unexpected camera control callback event, 0x4f525245

[kevinfreitas]

Same issue here, unfortunately. Pi 2 B and camera module trying the basic raspistill -v -o test.jpg command. Here's what I've done to troubleshoot so far:

• Hook camera module up to old 2011 Pi, same command works just fine
• Double check that ribbon cable is seated properly at both the Pi board and camera
• Remove USB wifi dongle to reduce power draw

The only thing I've left to try is to replace the 1.35A USB wall wart I'm using to power the Pi 2 with a 2A supply. Given my troubleshooting about does this seem like it could be the problem? Is there any good way to verify this before I spend the $$?

Thanks so much! ~ Kevin

[kevinfreitas]

Seems I'm talking to myself here but just got a 2.5A supply in the mail, tried it out and... same error. Bad Pi 2 board in some regard.