Pi compute module 3 with two cams : unable to make it work


I use a board (www.embeddedpi.com) with a pi compute module 3 and two cameras.
I fail to make the cameras work with resinOS. However it works with Raspbian.

Camera 0 uses gpio 4 for shutdown, gpio 22 for led and pins 0/1 for I2C SDA/SCL.
Camera 1 uses gpio 5 for shutdown, gpio 21 for led and pins 28/29 for I2C SDA/SCL

I changed config.txt to gpu_mem=192 and start_x=1, and did a “modprobe bcm2835-v4l2”, hoping it was enough, but when calling raspistill, I have message :

mmal: Cannot read camera info, keeping the defaults for OV5647
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

Any idea ?


Hi there. I don’t have any experience with using the dual interface with the rpi compute module, but the system that sets this up is in the boot loader and resinOS uses the exact same boot loader as raspbian, so I think it must be a minor configuration issue.

One thing I would check is the /boot/config.txt in the raspbian image that works and copy all those values over into the resinOS image. This should ensure that all the correct settings are enabled. Another thing to double check is that you are using resinOS 2.0.3 because that will have the most recent kernel and bootloader inline with what ships on raspbian jessie.

let me know how things progress.


Hi Shaun.
I am using Resin OS 2.0.3+rev1.
I checked /boot/config.txt and used RESIN_HOST_CONFIG variables to adjust.
It seems not enough.

Maybe this is linked to device tree that I’ll have to migrate to resin, but I don’t know how to do exactly…
Can you help a little bit on chat ?


This went back-and-forth a little bit on our premium support channels.
The resolution was to put the camera configuration files within the resin-boot partition on the disk, either after the etch or by mounting the image. This sort of modification is on our roadmap to be able to achieve in a much more managed fashion.


By copying dt-blob.bin from a working raspbian to resin boot partition, it now works.
It was a problem of device tree.