This document is a work in progress and is intended for advanced users.
For the camera to work with the Compute Module 3 (CM3), the firmware needs to be September 21st 2016 or newer (use vcgencmd version to check).
Note for designers attaching Camera Modules directly to CM carrier boards: it is NOT necessary to incorporate the crypto chip used on the Raspberry Pi–designed camera boards when attaching the OM5647 or IMX219 Camera Modules directly to the CM carrier board. The Raspberry Pi firmware will automatically detect the CM and allow communications with the Camera Module to proceed without the crypto chip being present.
** Note that unless explicitly stated otherwise, these instructions will work identically on Compute Module and Compute Module 3 Module+IO board(s). **
-
On the compute module, run
sudo raspi-configand enable the camera. -
Next, run
sudo wget http://goo.gl/U4t12b -O /boot/dt-blob.bin -
Connect the RPI-CAMERA board and Camera Module to the CAM1 port. As an alternative, the Pi Zero camera cable can be used.
-
Connect GPIO pins together as shown below.
-
(Optional) To add an additional camera, repeat step 3 with CAM0 and connect the GPIO pins for the second camera.
-
Finally, reboot for the dt-blob.bin file to be read.
Recent raspicam binaries (raspivid and raspistill) have the -cs (--camselect) option to specify which camera should be used.
From other applications, MMAL can be told which camera to use by setting MMAL_PARAMETER_CAMERA_NUM accordingly.
MMAL_PARAMETER_INT32_T camera_num = {{MMAL_PARAMETER_CAMERA_NUM, sizeof(camera_num)}, CAMERA_NUMBER};
status = mmal_port_parameter_set(camera->control, &camera_num.hdr);
The 15-way 1mm FFC camera connector on the Raspberry Pi model A and B is attached to the CAM1 interface (though it only uses two of the four available lanes).
The Compute Module IO board has a 22-way 0.5mm FFC for each camera port, with CAM0 being a two-lane interface and CAM1 being the full four-lane interface.
To attach a standard Raspberry Pi Camera Module to the Compute Module IO board, a small adaptor board, called RPI-CAMERA, is available. It adapts the 22W FFC to the Pi 15W FFC. As an alternative, the Pi Zero camera cable can be used.
To make the Raspberry Pi Camera Module work with a standard Raspbian OS, the GPIOs and I2C interface must be wired to the CAM1 connector. This is done by bridging the correct GPIOs from the J6 GPIO connector to the CD1_SDA/SCL and CAM1_IO0/1 pins on the J5 connector using jumper wires. Additionally, a dt-blob.bin file needs to be provided to override default pin states (the dt-blob.bin file is a file that tells the GPU what pins to use when controlling the camera. For more information on this, see the relevant section in the guide to attaching peripherals to a Compute Module here).
The pin numbers below are provided only as an example. LED and SHUTDOWN pins can be shared by both cameras, if required. The SDA and SCL pins must be either GPIO0 and GPIO1 or GPIO28 and 29 and must be individual to each camera.
- Attach the 0.5mm 22W FFC flexi (included with the RPI-CAMERA board) to the CAM1 connector (flex contacts face down). As an alternative, the Pi Zero camera cable can be used.
- Attach the RPI-CAMERA adaptor board to the other end of the 0.5mm flex (flex contacts face down).
- Attach a Raspberry Pi Camera to the other, larger 15W 1mm FFC on the RPI-CAMERA adaptor board (contacts on the Raspberry Pi Camera flex must face up).
- Attach CD1_SDA (J6 pin 37) to GPIO0 (J5 pin 1).
- Attach CD1_SCL (J6 pin 39) to GPIO1 (J5 pin 3).
- Attach CAM1_IO1 (J6 pin 41) to GPIO2 (J5 pin 5).
- Attach CAM1_IO0 (J6 pin 43) to GPIO3 (J5 pin 7).
The numbers in brackets are conventional, physical pin numbers, numbered from left to right, top to bottom. The numbers on the silkscreen correspond to the Broadcom SoC GPIO numbers.
The GPIOs used by the camera default to input mode on the Compute Module. In order to override the default pin states and define the pins used by the camera, we need to create a dt-blob.bin file from a source dts file with the relevant information for the GPU, and place this on the root of the first FAT partition.
Sample device tree source files are provided at the bottom of this document.
The pin_config section in the pins_cm { } (compute module) or pins_cm3 { } (compute module3) section of the source dts needs the camera's LED and power enable pins set to outputs:
pin@p2 { function = "output"; termination = "no_pulling"; };
pin@p3 { function = "output"; termination = "no_pulling"; };
To tell the firmware which pins to use and how many cameras to look for, add the following to the pin_defines section:
pin_define@CAMERA_0_LED { type = "internal"; number = <2>; };
pin_define@CAMERA_0_SHUTDOWN { type = "internal"; number = <3>; };
pin_define@CAMERA_0_UNICAM_PORT { type = "internal"; number = <1>; };
pin_define@CAMERA_0_I2C_PORT { type = "internal"; number = <0>; };
pin_define@CAMERA_0_SDA_PIN { type = "internal"; number = <0>; };
pin_define@CAMERA_0_SCL_PIN { type = "internal"; number = <1>; };
Attach the second camera to the (CAM0) connector as before.
Connect up the I2C and GPIO lines.
- Attach CD0_SDA (J6 pin 45) to GPIO28 (J6 pin 1).
- Attach CD0_SCL (J6 pin 47) to GPIO29 (J6 pin 3).
- Attach CAM0_IO1 (J6 pin 49) to GPIO30 (J6 pin 5).
- Attach CAM0_IO0 (J6 pin 51) to GPIO31 (J6 pin 7).
The Compute Module's pin_config section needs the second camera's LED and power enable pins configured:
pin@p30 { function = "output"; termination = "no_pulling"; };
pin@p31 { function = "output"; termination = "no_pulling"; };
In the Compute Module's pin_defines section of the dts file, change the NUM_CAMERAS parameter to 2 and add the following:
pin_define@CAMERA_1_LED { type = "internal"; number = <30>; };
pin_define@CAMERA_1_SHUTDOWN { type = "internal"; number = <31>; };
pin_define@CAMERA_1_UNICAM_PORT { type = "internal"; number = <0>; };
pin_define@CAMERA_1_I2C_PORT { type = "internal"; number = <0>; };
pin_define@CAMERA_1_SDA_PIN { type = "internal"; number = <28>; };
pin_define@CAMERA_1_SCL_PIN { type = "internal"; number = <29>; };