Introduction

As the IO board for the Raspberry Pi Compute Module 5, CM5-DUAL-ETH-4G/5G-BASE is a baseboard that can be used with the Raspberry Pi Compute Module 5. It features powerful functionality with onboard dual USB 3.2 Gen1 ports, M.2 M KEY, M.2 B KEY (4G/5G module interface), and dual network ports for user convenience.

Features and Precautions

1. Do not plug or unplug any device other than USB and HDMI when the device is powered on
2. Type-C can be used as a USB SLAVE interface to flash images or power the device.
3. Onboard 2 USB 3.2 Gen1 ports
4. Supports 4 screens to display different contents, adds MIPI DSI driver, regardless of whether a screen is connected, the system will default to be connected, the screen will display in split-screen mode (related to the system version)
5. Onboard M.2 M KEY interface, supports NVMe hard drive protocol (or AI modules of the PCIe protocol) 6. Onboard M.2 B KEY interface, supports connecting 4G/5G communication modules 7. Onboard BOOT switch, you can turn the BOOT switch to ON before powering on, connect the device to a computer via Type-C to allow the device into flashing mode
8. Do not connect other devices when using Type-C for flashing, otherwise insufficient power supply will cause the device to be unrecognized
9. The USB3.0 port has a maximum current output of 2A

Dimensions

Core Board Size

Baseboard Size

Case Size

Stay tuned...

Image Flashing

How to Flash

Enter flashing mode
1. Onboard BOOT switch, you can turn the BOOT switch to ON before powering on, connect the device to a computer via Type-C to allow the device into flashing mode

Click here for EMMC version
Click here for LITE version

M.2 M KEY (NVMe Hard Drive)

1. Enable PCIE interface

PI5B defaults to not having the PCIE interface enabled. Add to /boot/firmware/config.txt:
dtparam=pciex1

2. PCIE is gen2 by default, if you need to enable PCIE gen3, then add following to /boot/firmware/config.txt:

dtparam=pciex1_gen=3

3. After the modification, reboot the PI5, and the device can be recognized.

As shown in the figure below, SM2263 is identified as my SSD solid state drives, and the other PI5 is the RPI chip

4. Partition, skip this step if you have partitioned and formatted on other platforms (Note: Partitioning will delete all data on the SSD, please proceed with caution)

Lsblk     This command is executed to view the disk (if you want to see the details, run the sudo fdisk -l command)

Partition: 
sudo fdisk /dev/nvme0n1    The device number is the total device number, do not add p1, that is just a partition
How to use the partitioning tool fdisk:
n New partition
q Quit without saving
p Print the partition table
m Print the selection menu
D Delete the partition
w Save and exit
t Modify the ID number
Add the partition and execute n, then save and exit with w

5. Format

sudo mkfs.     Execute the command and press Tab key, you will see a lot of different suffixes, and the different suffixes are the formats you need to format

If I want to format it in ext4 file format, then execute the command:
sudo mkfs.ext4 /dev/nvme0n1p1
Wait a moment, once all "done" appear as below, it indicates that the formatting is completed

6. Mount

Create a mount directory
sudo mkdir toshiba
Mount the device
sudo mount /dev/nvme0n1p1 ./toshiba
Check the disk status
df -h

Read/Write Test

Enter the directory where the disk is mounted

cd toshiba

• Free up the memory

sudo sh -c "sync && echo 3 > /proc/sys/vm/drop_caches"

• Copy Raspberry Pi memory content to the hard disk (write)

sudo dd if=/dev/zero of=./test_write count=2000 bs=1024k

• Copy the hard drive content to the Raspberry Pi memory (/etc/fstab read )

 sudo dd if=./test_write of=/dev/null count=2000 bs=1024k

• Note: The test results vary for different cards and environments. The Raspberry Pi is significantly affected. If you want to test accurate performance, use a PC for the test
  

Auto Mount

Test shows there's no issue. If it's not required to be used as a system disk, but only for expanding the disk, set it to auto-mount

sudo nano /etc/fstab

#Add at the end
/dev/nvme0n1p1  /home/pi/toshiba  ext4  defaults  0  0
#/dev/nvme0n1p1 is the device name, /home/pi/toshiba refers to mounting to a directory, ext4 is the file system type, defaults uses the default mount option
#Make the changes take effect (reboot only after testing, otherwise it will fail to mount and boot)
sudo mount -a

#Then reboot
Check the device with lsblk

NVMe SSD Boot

Boot the Raspberry Pi with a TF card first, mount and test it, and make sure the hardware can work properly

Choose one of the following methods

Method 1

1. Run the following command:

sudo raspi-config

2. Reboot Raspberry Pi

If you find you can't modify it multiple times, please reconnect to the network and then try to modify it (wait for the network to synchronize the time automatically), or modify the file after setting the correct time

3. Flash the system to NVME, then connect the NVME to the expansion board, remove the TF card and power it on again

Method 2

1. Modify the BOOT_ORDER in the Raspberry Pi boot loader configuration:

sudo rpi-eeprom-config --edit 
Modify BOOT_ORDER=0xf41 to BOOT_ORDER=0xf416

For more information, please refer to BOOT_ORDER 

2. Reboot Raspberry Pi

If you find you can't modify it multiple times, please reconnect to the network and then try to modify it (wait for the network to synchronize the time automatically), or modify the file after setting the correct time

3. Flash the system to NVME, then connect the NVME to the expansion board, remove the TF card and power it on again

Fan Control

The PI5 fan defaults to starting when the temperature reaches 50 degrees. If you want to control it at other temperatures, you can do so by adding specific content to /boot/firmware/config.txt, for example:

dtparam=fan_temp0=36000,fan_temp0_hyst=2000,fan_temp0_speed=90
dtparam=fan_temp1=40000,fan_temp1_hyst=3000,fan_temp1_speed=150
dtparam=fan_temp2=52000,fan_temp2_hyst=4000,fan_temp2_speed=200
dtparam=fan_temp3=58000,fan_temp3_hyst=5000,fan_temp3_speed=255

Among which:

fan_temp0/1/2/3               Indicates the temperature (36000 means 36℃)

fan_temp0/1/2/3_speed  Indicates the corresponding rotational speed (value up to 255)

fan_temp0/1/2/3_hyst      Indicates the hysteresis temperature

For more details, please click here

Notice: There are only 4 temperatures: 0, 1, 2 and 3, and it's not possible to set other temperatures. The hysteresis temperature must not exceed the step range between two temperatures

MIPI

Support dual MIPI, customers can freely choose CSI or DSI connections

The DSI screen is 800x480 resolution screen by default, please refer to the corresponding WIKI for other resolution screens

DSI

#Add the following to the config.txt file:
sudo nano /boot/firmware/config.txt
# DSI0 
dtoverlay=vc4-kms-dsi-7inch,dsi0
# DSI1 
dtoverlay=vc4-kms-dsi-7inch,dsi1

CSI

Update the system:

sudo rpi-update 

sudo nano /boot/firmware/config.txt
Note: A single camera can only connect to MIPI0

Allow one connection to DSI and one connection to CSI, for example, use IMX219 to connect to MIPI1
For example, if you want to connect a DSI display to MIPI1, add the following to the config.txt file

dtoverlay=imx219,cam0
dtoverlay=vc4-kms-dsi-7inch,dsi1

Use the shortcut Ctrl+o to save the file, then press Enter

sudo reboot

Test Camera

1. Enter the camera detection command, and you can see that the camera has been detected

   rpicam-hello --list-cameras

   
   
   
2. Display the camera screen to the desktop

   rpicam-hello -t 0

3. Take a photo

   rpicam-jpeg -o test.jpg

4. Record a 10s video

   rpicam-vid -t 10s -o test.h264

Other commands
Check if the camera is detected

rpicam-hello --list-cameras

Open the corresponding camera

rpicam-hello --camera 1 -t 0
rpicam-hello --camera 0 -t 0

Take a photo

rpicam-jpeg -o test.jpg
#You can add --camera to specify the camera

Real-Time Clock (RTC)

There is no battery by default, and an additional RTC battery is required

The CR/ML1220 can be used to power the RTC

Software Debugging

The default device is /dev/rtc0

Regarding time, by inputting "date" in the command line, you can see the current time. Connecting the Raspberry Pi system to the network will automatically synchronize the time. If the default RTC device is connected and functioning properly, the RTC time will be updated after the automatic network synchronization

sudo hwclock -r Read the RTC time, if there are multiple RTC devices, you can use -f to select the corresponding devices (for example: sudo hwclock -f /dev/rtc1 -r)

Hwclock

System clock -> Hardware clock (RTC)

sudo hwclock -w

Synchronize hardware clock (RTC) -> System clock

sudo hwclock  -s
 #Need to turn off the network, or disable network time synchronization, otherwise it will be changed back

Set the hardware clock time (RTC):

sudo hwclock --set --date="9/8/2023 16:45:05"

View the hardware clock (RTC)

sudo hwclock -r

Show version information.

sudo hwclock --verbose

Automated Wakeup

To support a low-power mode for wake-up alarms, add the configuration:

sudo -E rpi-eeprom-config --edit
#Add the following 2 lines
POWER_OFF_ON_HALT=1
WAKE_ON_GPIO=0
#Restart the device after adding (if you connect to the serial port log, you can see that there are update related logs)
sudo reboot
#You can use the following methods to test the function:
echo +600 | sudo tee /sys/class/rtc/rtc0/wakealarm
sudo halt  or  sudo poweroff
#10 minutes later, it will be awakened and restarted

RTC Battery Charging

Note: Before adding this, make sure your RTC battery allows charging and check the maximum allowable voltage

sudo nano /boot/firmware/config.txt
#Add
dtparam=rtc_bbat_vchg=3000000
#Among these, 3,000,000 represents the maximum voltage. Charging will stop when it reaches 3V, and trickle charging is initiated when the voltage is below 3V

USB

There are two USB3.2 Gen2 port onboard, with a current limit of 2A

2500M Ethernet Port (ETH1)

RJ45 2500M network port, supports 10M / 100M / 1000M / 2500M network access

Using RTL8156 scheme

The Raspberry Pi OS supports drive-free, which may not be available for third-party systems or cannot achieve 2500M speed

4G/5G

The board itself does not support 4G/5G and needs to be connected to the module through the M.2 B KEY interface. The M.2 B KEY only has USB 3.0 channels and does not support PCIe devices
Connect 4G/5G module and SIM card

If you need to turn off the 4G/5G module, you can control it using GPIO6 (BCM encoding 6). A high level output on GPIO6 turns off the module, while a low level output turns it on
It takes a certain amount of time (about 30 seconds) to turn off or on the module

M.2 4G/5G Network Card

M.2 Status LED status description:

Before configuration, please confirm that the module has been powered on
For 5G, please refer to 5G configuration

4G Configuration

sudo apt-get install minicom
sudo minicom -D /dev/ttyUSB2
#Enter the following command:
AT+CUSBPIDSWITCH=9011,1,1
#Return OK to proceed
#Then wait for the network card to restart
#This command only needs to be set once; the next time it powers on, it will default to this mode
#If unable to obtain the USB0 network card, execute:
sudo dhclient -v usb0

For RNDIS dial-up, please refer to: RNDIS Dial-up Internet

After performing the steps above normally, it will detect the USB0 network card (if you are not connected to other USB network cards)

If you are using an IoT card, such as a mobile IoT card, and have successfully registered on the network; however, dial-up internet access fails and you cannot ping, you can try one of the following AT commands to select the optimal frequency band:

AT+CNBP=0x0002000000400183,0x000001E000000000,0x0000000000000021
AT+CNBP=0x0002000000400180,0x480000000000000000000000000000000000000000000042000001E200000095,0x0000000000000021

AT Command

If unable to connect to the network, you can check the status with the command AT

sudo apt-get install minicom
sudo minicom -D /dev/ttyUSB2

Common AT Commands

The following AT commands are general for 4G/5G modules

For more AT commands, please refer to: AT_Command_V2.00
For more documents, please refer to: SIMCom