Compute-Module-4
| ||
| ||
| ||
Overview
Introduction
I am the 4th generation IO board of the Raspberry Pi Compute Module. The Compute Module 4 IO Board is a baseboard officially released by the Raspberry Pi that can be used with the Raspberry Pi Compute Module 4. It can be used as the development system of the Compute Module 4 and as Embedded boards are integrated into end products, or systems can be created quickly using off-the-shelf components such as Raspberry Pi HAT and PCIe modules. Its interface is concentrated on the same side, which is convenient for users to use.
Product dimension
Compute Module 4 IO Board
Compute Module 4 IO Board
For more description, please visit: compute module 4_IO board
Notes
Do not plug or unplug any device while it is powered on.
Writing Image
- Write Image for Compute Module Boards eMMC version
- Write Image for Compute Module Boards Lite version
USB2.0
The USB port is disabled by default on the CM4 to save power. If you need to start, you need to add the following to the config.txt file:
dtoverlay=dwc2,dr_mode=host
After restarting:
If you use the latest Raspberry Pi OS (image after October 30, 2021) USB2.0 is OTG mode by default, CM4 will report an error:
config failed, hub doesn't have any ports! (err -19)
However, USB can still be used. If you want to remove this error, remove otg_mode=1 in [cm4] of config.txt, and add dtoverlay=dwc2, dr_mode=host (USB cannot be recognized without adding it).
PCIe Gen 2 x 1
PCle sockets are designed to accept standard PC PCle cards. You should make sure you have an OS driver for your card.
The PCle link has been successfully used with NVMe drives via a passive PCle adapter.
Note: PCle interface does not support MSI-X. Typical PCle devices will fall back to MSI.
RTC FAN
This extended version only supports 12V.
- Note: Please connect the fan before turning on the power of the baseboard and then complete the test. Please do not connect the fan after the baseboard is powered on, because the fan control chip has been powered on, otherwise, the chip will be flashed!
- Note: Before connecting, please confirm whether the rated voltage of the fan is consistent with the voltage connected to the fan.
Please note that DSI and CSI are prohibited when using RTC.
I2C-10 is used by default.
RTC (PCF85063a) on i2c-10, address is 0 x 51 (7-bit address)
FAN (EMC2301) on i2c-10, address is 0 x 2f (7-bit address)
If you need to add it to your program instead of the kernel, you can refer to the C and Python demo reference click here.
RTC
sudo nano /boot/config.txt #Add the following lines at the end dtparam=i2c_vc=on dtoverlay=i2c-rtc,pcf85063a,i2c_csi_dsi #Add # in front of dtparam=audio=on #dtparam=audio=on #Save and exit, restart sudo reboot
How to use Hwclock
Synchronize system clock to hardware clock:
sudo hwclock -w
Synchronize hardware clock to system clock:
sudo hwclock -s #The network or the NTP needs to be closed, otherwise it will be changed back.
Set the hardware clock time:
sudo hwclock --set --date="9/8/2021 16:45:05"
View hardware clock:
sudo hwclock -r
Display version information:
sudo hwclock --verbose
Fan
1: Check if the kernel version is higher than or equal to 6.1.31.
uname -a
2: Add the following content at config.txt:
dtoverlay=i2c-fan,emc2301,i2c_csi_dsi,midtemp=45000,maxtemp=65000
3: For more parameters, you can refer to this link
Troubleshooting
1: After configuration, you can use the command "i2cdetect -y 10" to check whether the configuration is valid, and the valid I2C address should be UU without digits.
2: RTC value is not accurate, or an invalid prompt appears, check whether the RTC battery is connected and whether the voltage of the RTC battery is normal.
3: All configurations need to be rebooted after being added to take effect.
4: If the fan does not rotate after adding the fan driver, you can press "1" to troubleshoot and check whether the configuration is effective. If it is valid, then you can check whether the kernel version is higher or equal to 6.1.31 (uname -a). If the version is lower than 6.1.31, this kernel cannot work. For more details, you can refer to this link.
DSI CSI
New Version (Bookworm)
The DSI screen is 800x480 resolution screen by default, please refer to the corresponding WIKI for other resolution screens
When using the official base board Compute Module 4 IO Board, note that the J6 jumper cap needs to be connected
DSI
#Add the following to the config.txt file: sudo nano /boot/firmware/config.txt #DSI0 (V1~V3) dtoverlay=vc4-kms-dsi-7inch,dsi0 #DSI1 (V4) dtoverlay=vc4-kms-dsi-7inch,dsi1
CSI
| Mode | CAM0 setup statement | CAM1 setup statement |
|---|---|---|
| OV9281 | dtoverlay=ov9281,cam0 | dtoverlay=ov9281,cam1 |
| IMX290/IMX327 | dtoverlay=imx290,clock-frequency=37125000,cam0 | dtoverlay=imx290,clock-frequency=37125000,cam1 |
| IMX378 | dtoverlay=imx378,cam0 | dtoverlay=imx378,cam1 |
| IMX219 | dtoverlay=imx219,cam0 | dtoverlay=imx219,cam1 |
| IMX477 | dtoverlay=imx477,cam0 | dtoverlay=imx477,cam1 |
| IMX296 | dtoverlay=imx296,cam0 | dtoverlay=imx296,cam1 |
| IMX708 | dtoverlay=imx708,cam0 | dtoverlay=imx708,cam1 |
sudo reboot
Note:
1. The single-port camera can only work on CAM0, that is, it is not possible to use CAM1 port alone. But you can use the CAM0 port alone, or connect the dual cameras 2. If the device is recognized, and the startup prompt "Camera frontend has timed out!" appears, please update "sudo rpi-update"
Test Camera
- Enter the camera detection command, and you can see that the camera has been detected
libcamera-hello --list-cameras
- Display the camera screen to the desktop
libcamera-hello -t 0
- Take a photo
libcamera-jpeg -o test.jpg
- Record a 10s video
libcamera-vid -t 10000 -o test.h264
Other commands
Check if the camera is detected
libcamera-hello --list-cameras
Open the corresponding camera
libcamera-hello --camera 1 libcamera-hello --camera 0
Take a photo
libcamera-jpeg -o test.jpg #You can add --camera to specify the camera
#The new system uses dual cameras #Remove camera_auto_detect=1 in config.txt #camera_auto_detect=1 #Add dtoverlay=imx219,cam1 dtoverlay=imx219,cam0 #Where imx219 is the camera sensor model and other sensors are supported dtoverlay=ov5647,cam0 dtoverlay=imx219,cam0 dtoverlay=ov9281,cam0 dtoverlay=imx477,cam0 dtoverlay=imx519,cam0 #Then reboot reboot #Open camera libcamera-hello -t 0 or libcamera-hello #Other instructions: #Check if the camera is detected libcamera-hello --list-cameras #Open the corresponding camera, preview for 5 seconds libcamera-hello --camera 1 libcamera-hello --camera 0 #Take photos libcamera-jpeg -o test.jpg #Shoot video libcamera-vid -t 10000 -o test.h264 #You can add --camera to specify the camera #-t <duration> option allows the user to choose how long the window is displayed in milliseconds
For more commands, you can click here.
- Note: If using a DSI interface display there will be an HDMI disabled, even if just compiling the corresponding file without connecting a DSI screen.
- Connecting either HDMI port will allow output of an image, regardless of which HDMI port is used. If two HDMI screens are connected, only HDMI0 has an image output.
- To enable two HDMI ports, remove the configuration from config.txt:
- And then reboot it.
Please refer to Raspberry Pi manual.
Old System Version (Buster and Bullseye)
Configure Files
CSI and DSI are disabled by default. When using the camera and DSI, three I2C devices, I2C-10, I2C-11, and I2C-0 will be occupied.
Booting is performed as follows:
wget https://files.waveshare.com/upload/7/75/CM4_dt_blob_Source.zip unzip -o CM4_dt_blob_Source.zip -d ./CM4_dt_blob_Source sudo chmod 777 -R CM4_dt_blob_Source cd CM4_dt_blob_Source/ #Execute (for version V1~V3) sudo dtc -I dts -O dtb -o /boot/dt-blob.bin dt-blob-disp0-double_cam.dts #Execute (for version V4) sudo dtc -I dts -O dtb -o /boot/dt-blob.bin dt-blob-disp1-double_cam.dts Add the following to the config.txt file: sudo nano /boot/config.txt Change dtoverlay=vc4-kms-v3d to dtoverlay=vc4-fkms-v3d #When using any DSI, HDMI1 has no image output, even if you are not connected to the DSI screen, as long as you compile the corresponding file, then HDMI1 will have no output #If you need to restore, delete the corresponding dt-blob.bin: sudo rm -rf /boot/dt-blob.bin #After execution, turn off the power and restart
Record Test
Connect to the camera and the DSI display:
1. Please make sure it is connected under powering off.
2. Connect to the power.
3. The display will be booted after waiting for a few seconds.
4. If it fails to boot, check whether /boot/dt-blob.bin exists, and reboot it if it exists.
Old Version (Buster)
The camera needs to run raspi-config, select Interfacing Options -> Camera -> Yes -> Finish -> Yes, reboot the system, open enable camera, and then restart to save the changes.
Test the Raspberry Pi camera.
Check the screen of the first connected camera:
sudo raspivid -t 0 -cs 0
Check the screen of the second connected camera:
sudo raspivid -t 0 -cs 1
Resources
Official Manuals
- Compute Module IO Board Datasheet
- Raspberry Pi Compute Module 4 IO Board Product Brief
- Raspberry Pi Compute Module 4 IO Board Datasheet
Demo
Demo (Unofficial demo):
FAQ
b) Check whether the /boot/dt-blob.bin file exists, if it cannot be used, delete it.
At present, CAM1 is the default in use. If you want to use CAM0, you'll need to follow the instructions in the configuration file to set up the camera for CAM0. If you want to use both interfaces simultaneously, you'll need to configure it using the dual-camera method.
{{{5}}}
It can be powered by 5V and GND of 40PIN or micro USB cable.
{{{5}}}
Support
Technical Support
If you need technical support or have any feedback/review, please click the Submit Now button to submit a ticket, Our support team will check and reply to you within 1 to 2 working days. Please be patient as we make every effort to help you to resolve the issue.
Working Time: 9 AM - 6 PM GMT+8 (Monday to Friday)