If I were going to RMA for this error, it would be for %50 of the cameras.
I would think you would want to address this - it's not just me. There are
a ton of folks having this issue.
Is there anyone I can call and speak with about this?
Thanks. Again - I would hate to abandon these cameras/RPi's as a teaching
tool, but we cannot keep replacing the cameras at this rate. I do not have
enough info to troubleshoot myself, as I have exhausted the options I have
read about on support pages.
On Mon, Dec 8, 2014 at 8:52 AM, element14support <email@example.com>
You can contact our Technical Support Team that may be able to assist
- Phone: 1 877 736 4835
- M-F: 8:00AM-8:00PM (EST)
>it's not just me. There are a ton of folks having this issue.
I am one of those ton of folks. I am puzzled why no one has addressed this
and given some sort of answer. It seems no one cares once the product is on the market.
So what if half of them fail???
I've been facing the same problem as well. I've been searching the internet for quite some time for a solution. The forums in the official RPi foundation website seem to be bending towards the camera modules becoming dysfunctional because of static discharge.
Though I seem to have found a possible solution to the problem on Github
I'm a beginner to all this and thus cannot figure out how to use this solution please do help if you manage to.
Hi - I've bought a couple dozen raspberry pi cameras from you folks for a class I teach... Over the past couple of years I have gotten this error on over half of them:
mmal: Received unexpected camera control callback event, 0x4f525245
The kids absolutely love using the cameras, but It's getting pretty expensive to support the class by re-purchasing them. This appears to be a hot topic around the internet on RPi forums, and I have yet to hear a successful fix. Apparently this is tied to a conflict in resources in-board, from https://www.bountysource.com/issues/1335530-kernels-3-10-w1_gpio-destroys-i2c-bus-0-raspicam-doesn-t-work-anymore
The problem is that the 1-wire module overwrite the gpio function selection for the I2C pins.
Before 1-wire is loaded *0x20200000 = 0x48024 and I2C works (GPIO0 and GPIO in I2C alt function)
After 1-wire is loaded *0x20200000 = 0x48921 and I2C fails (GPIO0 is set to an output)
No idea yet why that happens yet, but that explains why I2C (and camera) stops working.
I hate to stop using the camera with these pis (tried b, b+, A+ all have failed) but I don't know what else to do. Can you folks help?