2001 RPi CM4 Ultra EN

Keywords

Raspberry Pi, CM4 Core board, 2.5G Ethernet, NVME SSD, WiFi6, 5G, RPiOS, OpenWrt

I. Introduction

The CM4_Ultra board is an expansion board designed based on the Raspberry Pi CM4 core board. It expands the single PCIe interface of the CM4 into four PCIe interfaces using a switch chip. The CM4_Ultra board features one PCIe M.2 M-KEY interface for connecting an NVMe SSD, one PCIe 2.5G Ethernet port, one PCIe M.2 A-KEY interface for connecting WiFi6, and one PCIe expansion for USB 3.0. Additionally, one of the USB 3.0 ports is connected to an M.2 B-KEY interface for external 5G expansion. The board supports all versions of the Raspberry Pi CM4 core board. The expansion board is ideally suited for a variety of applications requiring high-speed data acquisition, processing, and communication, such as WiFi6 testing terminals, remote image and video capture systems, live streaming, vehicle infotainment systems, TBOX-like vehicle data access devices, integrated media players, facial recognition, soft routers, gateways, remote image transmission, edge computing, and more.

II. Hardware Spec


Power Supply	1DC input, wide voltage range of 7-24V, DC5.5-2.1 connector. 1USB-C 5V3A port, supports 5V PD charger; Two power sources cannot be used simultaneously.
Nerwork	1native Gigabit Ethernet port. 1PCIe 2.5G Ethernet port (RTL8125). 1PCIe M.2 A-KEY interface for expanding WiFi6. 1USB 3.0 M.2 B-KEY interface for 5G, with a Nano SIM card slot and 4 SMA antenna connectors.
Storage	1PCIe M.2 M-KEY slot, supporting 2280-sized NVMe SSD, does not support SATA/GNFF drives. 1TF card slot, used for booting the OS with the lite version of the Raspberry Pi CM4 core board; if using the CM4 core board with eMMC, this TF card slot will be unavailable.
USB Ports	2USB 3.0-A host ports. 1USB 2.0 port, 1.25mm-4P. 1*USB OTG port (USB-A), also the flashing port for the eMMC core board.
Display	1standard HDMI port supporting 4K resolution. 1DSI1 (22PIN, 0.5mm, flip-down connection).
Camera	2*CSI1(22PIN, 0.5mm, flip-down connection).
Others	2fan power supplies, 2.54mm-2P, 5V and 3.3V. 1boot jumper, 2.54mm-2P, for flashing the eMMC core board. GPIO, 2.54mm 2*20P, fully compatible with the GPIO pins of Raspberry Pi 4B.
Size	PCB size：111135mm, immersion gold process and RoHS compliant, PCB materials are UL certified, flame‑retardant rating 94V‑0. Optional aluminum alloy case with 4 fixing holes for easy equipment installation. Case size: 114154*31mm.

The pin definitions for the 40-pin connector, from left to right:


	1	2	3	4	5	6	7	8	9	10	11	12	13	14	15	16	17	18	19	20
2pin	5V	5V	GND	G14	G15	G18	GND	G23	G24	GND	G25	G08	G07	IDSC	GND	G12	GND	G16	G20	G21
1pin	3V3	G02	G03	G04	GND	G17	G27	G22	3V3	G10	G09	G11	GND	IDSD	G05	G06	G13	G19	G26	GND

III. Flash OS

Raspberry Pi OS: 2024-07-04-raspios-bookworm-arm64.img.xz

You can download it in:

https://www.raspberrypi.com/software/operating-systems/#raspberry-pi-os-64-bit

For core boards with eMMC, the OS is flashed onto the eMMC. The core board does not have eMMC, the OS is flashed onto the TF card.

Use a core board with eMMC. Please use a jumper cap to short the BOOT and GND pin, and connect the USB 2.0-A OTG port to the computer using a USB Type-A cable (as shown in the figure below):

Once the flashing process is complete, remove the shorting cap, then power on again to start the OS.

For the flashing method, please refer to:

How to flash OS

IV. Work with Raspberry Pi OS

4.1 Ethernet test

4.1.1 Ethernet connection

Connect the Gigabit Ethernet port to the upstream router, and execute ifconfig -a on the terminal, which displays the following:

eth0 is a Gigabit Ethernet and has obtained an IP address.

eth1 is a 2.5G Ethernet, but since no network cable is plugged in, it has not acquired an IP address.

4.1.2 2.5G Ethernet speed test

Plug the Ethernet cable into the 2.5G Ethernet port, and the OS will automatically obtain an IP address. Then, we open the terminal and install the speed-testing tool iperf3.

sudo apt-get install iperf3

2.5G Ethernet speed test results:

2.15Gbps (Client mode):

1.75Gbps (server mode):

Note: The speed test results of 2.5G networks are affected by network conditions and testing methods. The actual speed may vary, and this test is for reference only.

4.1.3 Gigabit Ethernet speed test：

Plug the network cable into the Gigabit Ethernet port, and the OS will automatically obtain an IP address. Then, we open the terminal and test using iperf3.

Native Gigabit Ethernet speed test results:

940Mb/s (Client mode):

823M (Server mode):

Note: The speed test results of 2.5G networks are affected by network conditions and testing methods. The actual speed may vary, and this test is for reference only.

4.2 SSD test

4.2.1 Basic operations of SSD

NVMe SSDs are for data storage only and cannot be used as a boot drive.

When you open the File Manager, you can see the partitions of the SSD. The screenshot is shown below:

To operate the SSD, click the partition icon, enter the login password, and then click "Authenticate". After successful authorization, you can perform operations on the SSD.

Now, when you return to the desktop, you will see the shortcut icon for the SSD partition:

You can also enter df in the terminal to see the SSD partition and its mounting information. We can use this SSD as a storage device:

If you need to perform operations such as partitioning and permanently mounting an SSD, please refer to this page.

4.2.2 SSD speed test

4.2.2.1 SSD interface speed test

We use the hdparm to test the SSD drive interface speed.

Install the hdparm software:

sudo apt install hdparm

Run the command multiple times to test the SSD speed repeatedly.

sudo hdparm -t /dev/nvme0n1

The test result shows that the SSD's interface speed is around 360MB/s.

4.2.2.2 Install the SAMBA file sharing service

SAMBA is a software for sharing files between Windows and Linux. We can use it to transfer files between Windows and Raspberry Pi via Ethernet, which allows us to test network speed.

Install SAMBA:

sudo apt install samba

Modify the SAMBA configuration file to add a shared node:

sudo nano /etc/samba/smb.conf

Add shared nodes at the end of the file:

[pi5]

comment = pi5 filesystem

path = /

available = yes

browseable = yes

public = yes

guest ok = yes

writable = yes

create mask = 0644

directory mask = 0755

valid users = mcuzone

force user = mcuzone

force group = mcuzone

The "mcuzone" in the last three lines represents the login username for the Raspberry Pi OS. Please modify it according to the actual situation.

After adding, save the file and then exit.

Grant SAMBA permissions to the username "mcuzone" (a custom password needs to be entered).

sudo smbpasswd -a mcuzone

Test and restart the SAMBA service:

sudo testparm

sudo service smbd restart

sudo service nmbd restart

After completing the setup, on a PC within the same local network as the CM5_NAS expansion board (using Windows 11 as an example), enter \192.168.8.61 in the file explorer (the address is that of the expansion board and may vary in practice). Then, enter the username and password (the password is the previously set SAMBA password, not the Raspberry Pi OS login password). Once done, we will be able to see the shared directory.

注Note: If "Remember my credentials" is checked, then after the SAMBA password is changed (i.e., after re-executing sudo smbpasswd -a mcuzone), the next time you try to access the shared address on Windows, the login will be denied. In this case, you need to go to Windows Credential Manager to delete or modify the saved credentials.

When executing the df command in the terminal, the path marked in the red box is the SSD's path:

Enter the SSD directory in Windows:

4.2.2.3 SSD R/W testing over a Gigabit Ethernet

Connect the network cable to the Gigabit Ethernet, then conduct R/W speed tests on the SSD drive via the SAMBA file sharing service.

Write:

Read:

4.2.2.4 SSD R/W testing over a 2.5G Ethernet

Connect the network cable to the 2.5G Ethernet, then conduct R/W speed tests on the SSD drive via the SAMBA file sharing service.

Write:

Read:

Note: The speed of the SSD drive test is influenced by various factors such as network conditions, hard drive quality, file storage status, and OS environment. The above test results are for reference only and should not be considered as the final parameters of the actual product. In practical tests, the read speed can reach up to 270MB/s.

4.3 DSI test

The official two LCD screens for Raspberry Pi: the 1st-gen LCD has a resolution of 800×480, while the 2nd-gen LCD has a resolution of 1280×720. Both screens require additional power supply.

▶ Raspberry Pi 1st-Gen LCD Display:

Power up the OS, open the terminal and execute the following commands:

sudo nano /boot/firmware/config.txt

Insert the following lines at the end of the file:

dtoverlay=vc4-kms-dsi-7inch

After saving and restarting the OS, you can use the Raspberry Pi 7-inch touchscreen.

Upon restart, execute the following commands in the terminal in order:

wget http://www.mcuzone.com/wiki/2001_CM4_Ultra/Brightness.zip

unzip Brightness.zip

cd Brightness

sudo chmod +x install.sh

./install.sh

Then you can open the Brightness window from the Accessories menu to adjust the backlight of the 7-inch screen:

▶ Raspberry Pi 2nd-Gen LCD Display:

Power up the OS, open the terminal and execute the following commands:

sudo nano /boot/firmware/config.txt

Insert the following lines at the end of the file:

dtoverlay=vc4-kms-dsi-ili9881-7inch,dsi0

After saving and restarting the OS, you can use the Raspberry Pi 7-inch touchscreen.

▶ Notes:

1): If both the HDMI display and the 7-inch touchscreen are connected simultaneously, the 7-inch touchscreen may become the secondary screen. Simply power off the system, disconnect the HDMI display, and restart; the 7-inch touchscreen will then function as the primary display.

2): The added command actually enables the second display, meaning a dual-screen setup. Whether the second screen's hardware is installed or not, the system may still recognize it as a dual-display configuration. If you use PrtScn (Print Screen) to take a screenshot, it may capture both screens. In some cases, this could even cause the system to fail to boot. Therefore, if you don’t need this screen, it is recommended to remove or comment out this line in config.txt.

4.4 CSI test

We tested using the OV5467 camera, connecting it to either the CSI0 or CSI1 interface. After connecting, power on the board, open the terminal, and execute the following commands:

sudo nano /boot/firmware/config.txt

Insert the following lines at the end of the file:

dtoverlay=ov5647,cam0

dtoverlay=ov5647,cam1

Add according to your model in practice. Save and restart the OS, then you can use the OV5647 camera.

Execute the following command in the terminal:

ls /dev

You can then see the video0 and video1 devices (inserting one camera displays video0, inserting two cameras displays video0 and video1, regardless of whether they are connected to CSI0 or CSI1):

To preview the camera feed, execute libcamera-hello --camera 0 or libcamera-hello --camera 1 in the terminal (a single connected camera is camera 0, while two cameras are assigned as camera 0 and camera 1):

If a photo is required, please excute:

libcamera-jpeg -o test.jpg

The photos are saved in the /home/mcuzone directory (i.e., the user's home directory). The photo effects are as follows:

4.5 USB test

After the OS boots up, we plug the wireless keyboard and mouse into the OTG interface, insert two USB 3.0 SD card readers into the USB 3.0 ports, and enter lsusb to check the USB devices.

Bus 002 Device 003: USB3.0-A, USB3.0 SD card reader.

Bus 002 Device 004: USB3.0-A, USB3.0 SD card reader.

Bus 003 Device 002: USB2.0-A (OTG) interface, wireless keyboard and mouse.

Verify that all identifications are normal; then run lsusb -t to check the USB ports' operating mode:

Bus 02: 5000M USB interface (USB 3.0).

Bus 03: 480M USB interface (USB 2.0).

All operating modes are functioning normally.

4.6 5G module test

Testing based on the Quectel 5G module RM500U-CN. The 5G module is now configured, working plug-and-play with the Raspberry Pi OS.

(If the user has their own 5G module, they need to configure it themselves or integrate the driver, otherwise plug-and-play will not be possible, and this section cannot be referenced.)

4.6.1 Identify 5G module:

Gigabit Ethernet connected to the upstream router, then in the terminal, execute the command ifconfig -a, and you can see the following network information:

From the figure above, it can be seen that both the Gigabit Ethernet and the 5G module have obtained IP addresses, and we have successfully pinged the website. This indicates that the network can use:

But if you disconnect the network cable, then pinging the IP succeeds, while pinging the domain name fails, as shown in the figure below:

This means that if you only use the 5G module for internet access, there is an issue with domain name resolution.

Therefore, it is necessary to check whether the OS's nameserver (i.e., the DNS server) is correct. Use the following command to open the resolv.conf file:

sudo nano /etc/resolv.conf

Please check if the current nameserver is correct. If not, change it to the SIM card's nameserver (usually its gateway address) or some common nameserver addresses (such as 114.114.114.114, etc.).

After the modifications were completed, we successfully pinged the domain name again, confirming that the 5G module is functioning normally.

However, after the OS reboot, the DNS entries in the resolv.conf file will revert to the default addresses. Therefore, if you need to enable 5G internet access automatically on startup, you will also need to modify the permissions of the resolv.conf file. Since /etc/resolv.conf is actually a soft link, you must recreate the resolv.conf file to change its permissions. The method is as follows:

sudo mv /etc/resolv.conf /etc/resolv.conf.link

sudo nano /etc/resolv.conf

This recreates the resolv.conf file. Add the following content to the new file:

nameserver 114.114.114.114

Save and exit, then execute:

sudo chattr +i /etc/resolv.conf

After performing the above steps, the resolv.conf file will remain unchanged even after an OS restart.

4.6.2 Modification of Network Priority

When both Ethernet and 5G are connected, the default preference is to use the 5G network for internet access.

Execute the route command to view the routing table. Since usb0 is listed first, the internet connection is currently through the 5G module.

If you want to prioritize the wired network for internet access, you can execute the following command:

Explanation of these two commands (separated by '&&'):

sudo ip route del default: Remove the default route from the routing table.

sudo route add -net default netmask 0.0.0.0 gw 192.168.8.1: Add the gateway of the wired network as a new default route (ensure to use the actual gateway address).

After the execution is completed, execute the route command to view the routing table. The current default route is the gateway of the wired network (eth0 ranks first):

This way, the network will default to using the wired connection. If you need to switch back to defaulting to the 5G network, please execute the following command:

sudo ip route del default && sudo route add -net default netmask 0.0.0.0 gw 192.168.42.1

Then you can reboot the OS.

192.168.42.1 is the default gateway for the 5G module; please refer to the actual configuration.

Note: After a reboot, the routing table resets. To ensure the network continues to use the wired or wireless connection as the default route post-restart, you'll need to execute sudo ip route del default && sudo route add -net default netmask 0.0.0.0 gw 192.168.8.1 again.

4.6.3 5G network speed test

We unplugged the network cable, leaving only the 5G network connection, and then entered the speed test website to conduct a speed test.

The results are as follows:

Note: The 5G module network speed test is affected by 5G signal and testing methods. The actual speed may vary, and this test is for reference only.

4.6.4 AT command operation

Connect the 5G module to the expansion board. After the OS starts, we enter lsusb, and the display is as follows:

Note down the ID value of the 5G module: 2c7c 0900。

Download minicom:

sudo apt-get install minicom

Use the following command to enable the ttyUSB serial port of the 5G module, where the value after echo is the ID value recorded earlier:

sudo modprobe option

sudo sh -c 'echo 2c7c 0900 > /sys/bus/usb-serial/drivers/option1/new_id'

After executing the above two commands, execute the following:

sudo minicom -D /dev/ttyUSB2

(Note: The choice of which serial port to use should be based on the ability to input and run AT commands after entering this port, ensuring that the display is not garbled and the results do not jump erratically.)

The first time you enter an AT command, there may be no echo. If you then input the command at and press Enter, and it returns "OK," it indicates that everything is working properly. If you need to check the echo, please type the command: ate1, then press Enter. After that, you can continue to type other commands and press Enter to see the results.

After entering minicom, we input AT commands for testing:

Common AT commands:

1) Check if the SIM card is detected:

at+cpin?

If ready is returned, the card is recognized; if error is returned, check the hardware.

2) Check antenna signal quality (The following information is specific to the RM500U-CN model. Parameters may vary for different 5G models. Please refer to the AT command manual of your specific 5G module for details.):

at+CESQ

Example of return values:

+CESQ: 99,99,255,255,255,255,74,59,68

The last digit can calculate the RSRP value, which indicates the signal strength. The method is as follows:

Subtract 140 from this value to obtain the RSRP value. For example, in this case, RSRP=68-140=-72dBm, and then refer to the table:

RSRP(dBm)	Coverage Intensity Level	Notes
RSRP<=-105	6	Poor coverage. The service can hardly make calls.
-105<RSRP<=-95	5	Coverage is weak. Voice calls can be made outdoors, but the success rate is low with a high drop call rate. Indoor calls are nearly impossible to establish.
-95<RSRP<=-85	4	Coverage is average. various services can be initiated outdoors, providing low-rate data services. However, indoor call success rates are low, and the drop call rate is high.
-85<RSRP<=-75	3	Coverage is good. Outdoor areas support various services with medium-rate data, while indoor areas support services but only at low data rates.
-75<RSRP<=-65	2	With good coverage, high-speed data services can be initiated outdoors for various applications. Indoors, various services can be initiated with medium-rate data services.
RSRP>-65	1	The coverage is very good.

RSRP=-72dBm corresponds to coverage level 2, which indicates good coverage strength, meaning the signal strength is good.

3) Check network registration status:

at+cops?

Normally, it should return the network supporter's code: 7, where 7 represents 4G, and where 11 represents 5G.

Note: The above command at+CESQ should not include a question mark, while the other two commands require a question mark.

4) View the SIM card's IMEI code:

at+cgsn

5) Disable radio frequency:

at+cfun=0

Enable radio frequency:

at+cfun=1

The two commands mentioned above can be used in pairs to allow the module to re-register with the network without restarting the 5G module.

4.7 WiFi6 test

The CM4_Ultra expansion board supports WiFi6 (AX200) and WiFi6E (AX210) modules, both of which require driver installation to function.

For the Raspberry Pi Compute Module 4 (CM4) with built-in WiFi functionality, after installing the WiFi7/WiFi6 driver, the core board's WiFi will be automatically disabled and unavailable. Therefore, it is recommended to use only the Raspberry Pi CM4 core board without WiFi functionality.

Execute the command lspci in the terminal, and the section highlighted in the red box is the WiFi6 module:

The steps for installing the drivers are as follows:

4.7.1 Update the OS and header files

Execute the commands in the terminal:

sudo apt-get update

sudo apt install -y raspberrypi-kernel-headers firmware-iwlwifi flex yacc

4.7.2 Download the source code

mkdir wifi && cd wifi

wget http://www.mcuzone.com/wiki/2004_CM4_WiFi7/backport-iwlwifi-20231029.tar.bz2

sudo tar -xvf backport-iwlwifi-20231029.tar.bz2

4.7.3 Prepare the compilation environment

Execute the commands in the terminal:

sudo make defconfig-iwlwifi-public

sudo sed -i 's/CPTCFG_IWLMVM_VENDOR_CMDS=y/# CPTCFG_IWLMVM_VENDOR_CMDS is not set/' .config

4.7.4 Compile source code

Execute the commands in the terminal:

sudo make -j 4

sudo make install

Note: If the OS freezes or reports errors during compilation when using -j 4, please try compiling with -j 2 or -j 1 instead.

Restart the OS:

sudo reboot

4.7.3 Test WiFi6 module

After entering the OS, click the network icon in the upper right corner of the desktop, and then click "Click here to set Wi-Fi country":

We select CN:

Restart the OS again, then manually connect to the WiFi in the upper right corner of the desktop and enter the password:

Once WiFi is connected successfully, view the network parameters:

Executing ifconfig -a in the terminal can also display network parameters (wlan0):

4.8 WiFi7 test

The NVMe interface of the expansion board can be paired with an NVMe to WiFi7 adapter to enable WiFi7 functionality. The assembly diagram is as follows:

Execute the command lspci in the terminal, and the section highlighted in the red box is the WiFi7 module:

4.8.1 Install the driver and firmware

The installation of the WiFi7 (BE200) driver is the same as that of WiFi6, except that after the driver installation is completed, the firmware needs to be installed separately. After firmware installation, the OS can support WiFi7 (BE200), WiFi6 (AX200), and WiFi6E (AX210).

Firmware installation steps are as follows:

Execute the commands in the terminal:

cd ..

cd Downloads

wget http://www.mcuzone.com/wiki/0011_MPW7/firmware_wifi7.zip

unzip firmware_wifi7.zip

sudo cp iwlwifi-gl-c0-fm-c0-86.ucode /lib/firmware

sudo cp iwlwifi-gl-c0-fm-c0.pnvm /lib/firmware

Restart the OS:

sudo reboot

4.8.2 Test WiFi7 module

After the driver installation is completed, test the following:

The method for connecting to the wireless network is the same as for the WiFi6 module. Please refer to the previous section.

Once WiFi is connected successfully, view the network parameters:

Executing ifconfig -a in the terminal can also display network parameters (wlan0):

V. Work with OpenWrt

The OpenWrt version we used for testing is: openwrt-bcm27xx-bcm2711-rpi-4-squashfs-sysupgrade-linux-6.1.98-20240723.img.gz. This OS already includes the WiFi6 driver and the driver for our company's compatible 5G module (WiFi6 AX200/AX210 has frequency band restrictions). Firmware is provided for evaluation purposes only.

The CM4_Ultra expansion board can be configured in OpenWrt as a one-in-one-out switch mode, with the native Gigabit on the expansion board serving as the WAN port (connected to the Internet) and 2.5G Ethernet or WiFi6 (2.4G only) configured as a LAN port for connecting to a PC. It is also possible to use a 5G module as WAN and Ethernet or WiFi6 as LAN.

5.1 Preparation

Connect the native Gigabit on the expansion board to the PC. After powering on the OS, go to Network & Internet settings in Windows, open the connected network under Ethernet, and check the default gateway IP address. This address is the backend configuration page address of the OpenWrt. As shown in the figure, the tested address in this article is 192.168.198.1:

Then open a web browser, enter 192.168.198.1 to access the OpenWrt system. The default username is root, and the default password is password:

5.2 Network interface configuration

Open "Network - Interfaces", then click "Add new interface":

Set the interface name to "WAN", select "DHCP client" for the interface protocol, choose "eth0" for the interface, and then click the "Submit” button:

In the firewall settings, choose the WAN port and click "Save". Do not click "Save & Apply":

Then click the "Return to Overview" button, and at the interface, click the "Edit" button for the LAN port:

In the physical settings, change the interface to eth1:

Then click the "Save & Apply" button, and the network configuration will be completed.

5.3 2.5G Ethernet test

After the network configuration is completed, the native Gigabit Ethernet becomes the WAN port, and the 2.5G Ethernet becomes the LAN port. Switch the Ethernet cable connected to the computer to the 2.5G port, then connect the native Gigabit Ethernet to the upstream router.

Access the OpenWrt page, click on "System - TTYD Terminal", after logging in (the default username is root, and the default password is password), enter ifconfig -a to check the IP address:

Here, eth0 is the 2.5G Ethernet, and eth1 is the Gigabit Ethernet .

You can also check the network port information under "Network - Interfaces".

Next, we will use the iperf3 speed testing software (pre-installed in the OS) on the TTYD terminal to conduct speed tests between the device and the PC:

When the expansion board acts as the Client mode:

When the expansion board acts as the Server mode:

Note: Network speed test results are influenced by network conditions and testing methods. Actual speeds may vary, and this test is for reference only.

5.4 SSD test

After logging into the admin panel, go to "System > Mount Points" to see the SSD automatically mounted:

Click on "Network Storage - Network Sharing". Be aware that there may be two "Network Sharing" options, choose the one marked Samba, not Ksmbd!

Add a shared directory, with the directory being the mounted SSD's address:

Then click the "Save & Apply" button.

After the configuration is complete, enter \\192.168.198.1 (the address is that of the extension board, it may vary in practice) in the file explorer, and you will see the shared directory:

Drag any file to the desktop to test read speed:

Drag and drop any file onto the SSD to test write speed:

Note: Test speeds are affected by various factors such as network conditions, SSD quality, file storage status on the SSD, etc. The above test results are for reference only and do not serve as final parameters for the actual product.

If Windows prompts that access is denied when trying to access a shared resource:

The Windows network policy needs to be modified. Press Windows + R, then type gpedit.msc to launch the Local Group Policy Editor. Go to Computer Configuration - Administrative Templates - Network - Lanman Workstation step by step. In the right content area, you can see the policy setting "Enable insecure guest logons". The status is '"Not configured".

Double-click the policy setting "Enable insecure guest logons", set its status to "Enabled", and click the OK button:

After setup, I retried and could access it successfully.

5.5 WiFi6 module test

5.5.1 Configure WiFi6

Following section 5.2, insert the WiFi6 module (AX200 or AX210) into the expansion board, connect the 2.5G Ethernet to the computer, and leave the Gigabit Ethernet unconnected. After logging into the backend, the wireless overview can be seen under "Network - Wireless":

Click the "Scan" button to scan for nearby wireless APs:

Choose one to connect, and select "WAN" for the firewall:

Then click "Submit", and after submitting, click "Save & Apply":

After success, return to the "Wireless Profile" to see that the wireless connection has been successfully established:

We log into the TTYD terminal and execute ifconfig -a to check the network parameters. We can see that the wireless network card (wlan0) has obtained an IP address:

Using this expansion board as a Client to conduct speed tests with the computer, the results are as follows:

If you need to use the expansion board as a Server, go to "Firewall - General Settings - Zones" and change the inbound data policy for WAN to accept:

Note: Network speed test results are affected by the network environment and testing methods. The actual speed may vary, and this test is for reference only.

5.5.2 Configure the WiFi6 module as a wireless AP

The AX210 can operate as a wireless AP in 2.4G mode, while the AX200 cannot function as a wireless AP. This section uses the AX210 for testing, achieving Gigabit Ethernet as WAN and the AX210 as LAN.

Continuing from the previous section, we will now connect the Gigabit Ethernet to the upstream router. Then, click "Edit" in "Network - Wireless":

Modify according to the following image:

Please change "Mode" to "Access Point AP", set "Network" to "lan", and you can define the wireless AP name yourself. Here, we name it "AX210":

Click "Save & Apply", then go to "Network - Interfaces" and delete WWAN:

Please click "Modify" for LAN:

Enter the physical settings of the LAN (change the original 2.5G LAN to AX210 LAN), and confirm the settings as shown in the figure below:

Click "Save & Apply", then go to "Network - Wireless", disable and then enable this AP first:

Then we can search for this AP. We connect to this AP, and the password is the same as the one for the wireless AP we connected to in the previous section:

The internet speed test results are as follows:

Note: Network speed test results are affected by the network environment and testing methods. The actual speed may vary, and this test is for reference only.

5.5 5G module test

With a 5G module, we can configure the OpenWrt to accept 5G as WAN and Ethernet port as LAN or wireless WiFi as LAN (2.4GHz mode only).

Insert the 5G module (this document uses the RM500U-CN as an example) and the SIM card, then connect from the computer to the 2.5G Ethernet, leaving the native Gigabit Ethernet unconnected.

Start the OS, click on "System - TTYD Terminal," log in, and enter ifconfig -a to check the network interfaces:

You can see there is a network card named usb0, which is the 5G module, but it has no IP address.

Go to "Network - Interfaces", and click "Add new interface":

Configure according to the diagram below to add a new interface, which this document names "5GWAN":

Click "Submit", then go to "Firewall Settings" and set the firewall zone to "WAN":

Then click "Save & Apply". After it succeeds, return to "Network - Interfaces". At this point, you will see that the 5G module has obtained an IP address, and the PC can access the internet through this 5G module:

The internet speed test results on the PC are as follows:

Note: Network speed test results are affected by the network environment and testing methods. The actual speed may vary, and this test is for reference only.

In the previous section, we have set up the WiFi as a wireless AP, so we connected our mobile phone to this wireless AP and then tested the network speed on the phone. The results are as follows:

Note: Network speed test results are affected by the network environment and testing methods. The actual speed may vary, and this test is for reference only.

VI. Power consumption test information

**This power consumption test uses a USB-C port connected to a 5V 3A power supply**
	Standby powerconsumption	Power usage during system operation	Modules use each other	System powerconsumption
No external devices	0.756A		Transferring files from the computer to the SSD over WiFi6	1.25A
Use 5G module only	0.9A	1.9A (test speed)	Transferring files from the SSD to the computer over WiFi6	1.72A
Use SSD only	0.847A		Transferring files from the SSD to the computer over 2.5G Ethernet	1.588A
Use WiFi6 only	0.83A	1.15A	Transferring files from the computer to the SSD over 2.5G Ethernet	1.668A
All devices connected	1.15A		Download files from webpages to SSD over 5G module	1.88A

Note: The above data is our company's test data and is for reference only.

VII. The compatibility test of the CM5 core board

▶ Raspberry Pi OS:

Boot	Supports booting via the eMMC version of the CM5 core board. The CM5 core board without eMMC cannot boot from a TF card but can boot using an SSD via the SSD interface.
Device Name	HDMI output	USB2.0-A ports	USB3.0-A ports	SSD	Gigabit Ethernet	2.5G Ethernet	Core Board WiFi
Compatible or not?	√	√	√	√	√	√	√
Device Name	WiFi6	5G module	DSI1	CSI0	CSI1	CSI1 used as DSI
Compatible or not?	√	√	√	×	√(cam0)	√(dsi0)
Note: √ = compatible, × = incompatible. The text in parentheses indicates the differences from the CM4 core board.

Contact Us

QQ：8204136

Email: mcuzone@vip.qq.com

Tel: +86(0)13957118045

If there are any omissions, errors, or infringements on this page, please contact us through the above methods. Thank you!