在Raspberry Pi CM5發(fā)布的那天，我發(fā)表了一篇關(guān)于Raspberry Pi CM5開(kāi)發(fā)套件的迷你評(píng)測(cè)，展示了如何組裝套件并啟動(dòng)RaspberryPi操作系統(tǒng)，還運(yùn)行了sbc-bench基準(zhǔn)測(cè)試來(lái)評(píng)估其性能。遺憾的是，在測(cè)試過(guò)程中，Broadcom BCM2712 CPU出現(xiàn)了降頻，這意味著當(dāng)CM5 IO板置于IO盒內(nèi)且處理器模塊5僅靠風(fēng)扇散熱時(shí)，散熱效果并不理想。因此，今天我將使用其他散熱方案重復(fù)相同的測(cè)試，即官方的Raspberry Pi CM5散熱器（僅散熱片）和上海晶珩的CM5主動(dòng)散熱器，后者類(lèi)似于RaspberryPi5的主動(dòng)散熱器，但專(zhuān)為CPU模塊設(shè)計(jì)。

但在那之前，我要做一些“清理工作”。自從上次我從NVMe SSD啟動(dòng)Raspberry Pi 操作系統(tǒng)以來(lái)，我發(fā)現(xiàn)攝像頭無(wú)法正常工作。因此，我將報(bào)告我在eMMC閃存上安裝Raspberry Pi 操作系統(tǒng)并使攝像頭正常工作的經(jīng)歷，這兩件事都進(jìn)行得不太順利。

將Raspberry Pi操作系統(tǒng)安裝到CM5的eMMC閃存

理論上，將Raspberry Pi操作系統(tǒng)安裝到CM5模塊的eMMC閃存上應(yīng)該很容易，因?yàn)橐延邢嚓P(guān)文檔說(shuō)明。

我們需要在J6接頭的左側(cè)插入一個(gè)跳線，標(biāo)記為“安裝跳線以禁用eMMC啟動(dòng)”，并按照下圖所示在IO板和主機(jī)之間連接一根USB-C電纜。

然后，我們需要安裝并運(yùn)行rpiboot，以便eMMC閃存作為主機(jī)上的USB存儲(chǔ)設(shè)備出現(xiàn)。

sudo apt install rpibootsudo rpiboot

該實(shí)用程序一直卡在等待主板的界面……而且我無(wú)法在系統(tǒng)中看到任何表明有新USB設(shè)備的信息。

RPIBOOT: build-date Jan 31 2022 version 0~20220315+git6fa2ec0+nowin-0ubuntu1Waiting for BCM2835/6/7/2711...

經(jīng)過(guò)幾次嘗試后，我認(rèn)為可能是Ubuntu 22.04存儲(chǔ)庫(kù)中的rpiboot版本太舊了。因此，我將其刪除，并從源代碼構(gòu)建了該實(shí)用程序：

sudo apt remove rpibootsudo apt install git libusb-1.0-0-dev pkg-config build-essentialgit clone --recurse-submodules --shallow-submodules --depth=1 https://github.com/raspberrypi/usbbootcd usbbootmakesudo make install

該命令的輸出現(xiàn)在看起來(lái)好多了……

jaufranc@CNX-LAPTOP-5:~/usbboot$ sudo rpibootRPIBOOT: build-date Dec 20 2024 version 20240422~085300 ef721cdaIf the device fails to connect then please see https://rpltd.co/rpibootfordebuggingtips.Waiting for BCM2835/6/7/2711/2712...2712: Directory not specified using default /usr/share/rpiboot/mass-storage-gadget64/Sending bootcode.binSuccessful read 4 bytesWaiting for BCM2835/6/7/2711/2712...Second stage boot serverFile read: mcb.binFile read: memsys00.binFile read: memsys01.binFile read: memsys02.binFile read: memsys03.binFile read: bootmainLoading: /usr/share/rpiboot/mass-storage-gadget64//config.txtFile read: config.txtLoading: /usr/share/rpiboot/mass-storage-gadget64//boot.imgFile read: boot.imgSecond stage boot server done

于是我啟動(dòng)了Raspberry Pi鏡像，選擇了Raspberry Pi OS的64位版本，以及名為“Raspberry Pi多功能USB設(shè)備”的存儲(chǔ)設(shè)備，其容量為31.3GB，這與我模塊上的32GBeMMC閃存相對(duì)應(yīng)。

我可以像將鏡像寫(xiě)入microSD卡那樣，將鏡像寫(xiě)入Raspberry Pi CM5。

一旦完成，操作系統(tǒng)就會(huì)從eMMC閃存中正常啟動(dòng)。

我們還可以使用lsblk命令來(lái)檢查eMMC閃存的分區(qū)：

pi@raspberrypi:~ $ lsblkNAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTSmmcblk0 179:0 0 29.1G 0 disk├─mmcblk0p1 179:1 0 512M 0 part /boot/firmware└─mmcblk0p2 179:2 0 28.6G 0 part /mmcblk0boot0 179:32 0 4M 1 diskmmcblk0boot1 179:64 0 4M 1 disk

Raspberry Pi CM5 攝像頭支持

如引言所述，當(dāng)將Raspberry Pi 攝像頭模塊3連接到CAM/DISP 0連接器時(shí)，它并不能即插即用。

pi@raspberrypi:~ $ rpicam-hello --listNo cameras available!

雖然有關(guān)于如何在CAM/DISP 0和CAM/DISP 1上啟用攝像頭的文檔，但文檔有些不完整，且部分內(nèi)容存在錯(cuò)誤。

我按照指示編輯了/boot/firmware/config.txt文件，將camera_auto_detect行注釋掉，并為RaspberryPiCameraModule3添加了overlay：

# Automatically load overlays for detected cameras#camera_auto_detect=1dtoverlay=imx708,cam0

重啟后，問(wèn)題解決了。

pi@raspberrypi:~ $ rpicam-hello --listAvailable cameras-----------------0 : imx708 [4608x2592 10-bit RGGB] (/base/axi/pcie@120000/rp1/i2c@88000/imx708@1a)Modes: 'SRGGB10_CSI2P' : 1536x864 [120.13 fps - (768, 432)/3072x1728 crop]2304x1296 [56.03 fps - (0, 0)/4608x2592 crop]4608x2592 [14.35 fps - (0, 0)/4608x2592 crop]

這很簡(jiǎn)單，沒(méi)有遇到任何問(wèn)題。

使用第二個(gè)相機(jī)的方法類(lèi)似，但CAM/DISP 1接口要求我們?cè)贘6上添加兩個(gè)跳線。

我決定使用Raspberry Pi AI相機(jī)進(jìn)行這次測(cè)試。我只有一根Raspberry Pi Zero相機(jī)線，因此無(wú)法同時(shí)測(cè)試兩個(gè)相機(jī)。AI相機(jī)在計(jì)算模塊文檔中沒(méi)有列出，但我們?cè)贕itHub上可以找到所需的overlay：

# Automatically load overlays for detected cameras#camera_auto_detect=1dtoverlay=imx708,cam0dtoverlay=imx500-pi5,cam1

我還安裝了imx500包以防萬(wàn)一，并重啟了系統(tǒng)：

sudo apt install imx500-allsudo reboot

但相機(jī)沒(méi)有被檢測(cè)到，所以我嘗試將Raspberry Pi Camera Module 3連接到CAM/DISP 1，并將config.txt文件更改如下：

# Automatically load overlays for detected cameras#camera_auto_detect=1#dtoverlay=imx708,cam0dtoverlay=imx708,cam1

與之前一樣：

pi@raspberrypi:~ $ rpicam-hello --listNo cameras available!

最后，我只使用imx500-pi5設(shè)備樹(shù)overlay在CAM/DISP 0上測(cè)試了Raspberry Pi AI相機(jī)，并且可以檢測(cè)到它。

pi@raspberrypi:~ $ rpicam-hello --listAvailable cameras-----------------0 : imx500 [4056x3040 10-bit RGGB] (/base/axi/pcie@120000/rp1/i2c@88000/imx500@1a)Modes: 'SRGGB10_CSI2P' : 2028x1520 [30.02 fps - (0, 0)/4056x3040 crop]4056x3040 [10.00 fps - (0, 0)/4056x3040 crop]

所以我無(wú)法使用CAM/DISP 1連接器。要么是我遺漏了什么，要么是這個(gè)第二個(gè)連接器只有在CM5 IO板上連接了兩個(gè)相機(jī)時(shí)才會(huì)工作，單個(gè)相機(jī)連接時(shí)不會(huì)工作。所以，以防萬(wàn)一，我將Raspberry Pi Touch Display 2連接到CAM/DISP 0，將AI相機(jī)連接到CAM/DISP 1，并進(jìn)行了以下配置：

# Automatically load overlays for detected cameras#camera_auto_detect=1#dtoverlay=imx708,cam0dtoverlay=vc4-kms-dsi-ili9881-7inch,dsi0dtoverlay=imx500-pi5,cam1
# Automatically load overlays for detected DSI displays#display_auto_detect=1

顯示器工作正常，但AI相機(jī)在第二個(gè)連接器上仍然無(wú)法工作，盡管imx500傳感器在內(nèi)核日志中顯示…

pi@raspberrypi:~ $ dmesg | grep csi[ 0.958143] platform 1f00128000.csi: Fixed dependency cycle(s) with /axi/pcie@120000/rp1/i2c@88000/imx500@1a[ 0.964771] platform 1f00128000.csi: bcm2712_iommu_probe_device: MMU 1000005280.iommu[ 0.964774] platform 1f00128000.csi: bcm2712_iommu_device_group: MMU 1000005280.iommu[ 0.964778] platform 1f00128000.csi: Adding to iommu group 2[ 0.964795] platform 1f00128000.csi: bcm2712_iommu_attach_dev: MMU 1000005280.iommu[ 2.484827] rp1-cfe 1f00128000.csi: bcm2712_iommu_of_xlate: MMU 1000005280.iommu[ 2.485163] rp1-cfe 1f00128000.csi: DW dphy Host HW v1.20[ 2.485175] rp1-cfe 1f00128000.csi: PiSP FE HW v0.1[ 2.487088] rp1-cfe 1f00128000.csi: found subdevice /axi/pcie@120000/rp1/i2c@88000/imx500@1api@raspberrypi:~ $ rpicam-hello --listNo cameras available!

我現(xiàn)在先放棄了……

Raspberry Pi散熱器和CM5主動(dòng)散熱器安裝

讓我們回到正題，為Raspberry Pi CM5安裝散熱器。

無(wú)論是官方的Raspberry Pi散熱器還是上海晶珩的CM5主動(dòng)散熱器，它們都采用了類(lèi)似的包裝，并且基本配備了相同的附件，即一些螺絲、厚墊片和三個(gè)貼合在散熱器底部的導(dǎo)熱墊。

上海晶珩散熱器只是額外增加了一個(gè)散熱風(fēng)扇。讓我們先從官方散熱器開(kāi)始。首先，我需要撕掉保護(hù)導(dǎo)熱墊的薄膜……

然后再將其放置在CM5模塊上，并確保其方向不會(huì)干擾CPU模塊上的內(nèi)置天線。

接著，我在IO板和CM5模塊之間放置了四個(gè)墊片，并用四個(gè)螺絲將所有東西固定好。

安裝上海晶珩主動(dòng)散熱器的步驟完全相同，只不過(guò)我們還需要連接風(fēng)扇的電線。

使用 Raspberry Pi CM5 的散熱器進(jìn)行基準(zhǔn)測(cè)試和CPU溫度監(jiān)測(cè)

讓我們?cè)跓o(wú)風(fēng)扇配置下，使用Pi散熱器，同時(shí)運(yùn)行sbc-bench.sh基準(zhǔn)測(cè)試腳本，并用rpi-monitor監(jiān)測(cè)CPU溫度。

pi@raspberrypi:~ $ sudo ./sbc-bench.sh -rStarting to examine hardware/software for review purposes...
sbc-bench v0.9.68
Installing needed tools: distro packages already installed, mhz, cpufetch,cpuminer.Done.Checking cpufreq OPP. Done.Executing tinymembench. Done.Executing RAM latency tester. Done.Executing OpenSSL benchmark. Done.Executing 7-zip benchmark. Done.Throttling test: heating up the device, 5 more minutes to wait. Done.Checking cpufreq OPP again. Done (11 minutes elapsed).
Results validation:
* Measured clockspeed not lower than advertised max CPU clockspeed* No swapping* Background activity (%system) OK* No throttling
Full results uploaded to https://0x0.st/XCd-.txt
# Raspberry Pi Compute Module 5 Rev 1.0
Tested with sbc-bench v0.9.68 on Sat, 21 Dec 2024 1420 +0700. Fullinfo:[https://0x0.st/XCd-.txt](http://0x0.st/XCd-.txt)
### General information:
Information courtesy of cpufetch:
SoC: Broadcom BCM2712Technology: 16nmMicroarchitecture: Cortex-A76Max Frequency: 2.400 GHzCores: 4 coresFeatures: NEON,SHA1,SHA2,AES,CRC32
BCM2712, Kernel: aarch64, Userland: arm64
CPU sysfs topology (clusters, cpufreq members, clockspeeds)cpufreq min maxCPU cluster policy speed speed core type0 0 0 1500 2400 Cortex-A76 / r4p11 0 0 1500 2400 Cortex-A76 / r4p12 0 0 1500 2400 Cortex-A76 / r4p13 0 0 1500 2400 Cortex-A76 / r4p1
4041 KB available RAM
### Governors/policies (performance vs. idle consumption):
Original governor settings:
cpufreq-policy0: performance / 2400 MHz (conservative ondemand userspacepowersaveperformanceschedutil/15001600 1700 1800 1900 2000 2100 22002300 2400)
Tuned governor settings:
cpufreq-policy0: performance / 2400 MHz
Status of performance related policies found below /sys:
/sys/module/pcie_aspm/parameters/policy: default [performance] powersavepowersupersave
### Clockspeeds (idle vs. heated up):
Before at 52.9°C:
cpu0 (Cortex-A76): OPP: 2400, ThreadX: 2400, Measured: 2399
After at 79.3°C:
cpu0 (Cortex-A76): OPP: 2400, ThreadX: 2400, Measured: 2399
### Performance baseline
* memcpy: 5607.4 MB/s, memchr: 14150.3 MB/s, memset: 12426.6 MB/s* 16M latency: 117.8 118.8 118.3 118.0 119.6 119.6 141.0 135.3* 128M latency: 133.8 132.8 134.0 144.3 133.9 132.6 133.3 134.4* 7-zip MIPS (3 consecutive runs): 11145, 10906, 11012 (11020 avg), single-threaded:3203* `aes-256-cbc 540078.51k 1003701.74k 1256093.44k 1332879.02k 1365472.60k1367829.16k`* `aes-256-cbc 540615.20k 1003659.80k 1255990.53k 1332837.72k 1365235.03k1368178.69k`
### PCIe and storage devices:
* Raspberry RP1 PCIe 2.0 South Bridge: Speed 5GT/s, Width x4, driver inuse:rp1,* 29.1GB "Samsung BJTD4R" HS400 Enhanced strobe eMMC 5.1 card as /dev/mmcblk0:date07/2024,manfid/oemid:0x000015/0x0100,hw/fwrev: 0x0/0x0300000000000000
### Swap configuration:
* /var/swap on /dev/mmcblk0p2: 512.0M (0K used) on MMC storage
### Software versions:
* Debian GNU/Linux 12 (bookworm)* Build scripts: http://archive.raspberrypi.com/debian/ bookworm main* Compiler: /usr/bin/gcc (Debian 12.2.0-14) 12.2.0 / aarch64-linux-gnu* OpenSSL 3.0.15, built on 3 Sep 2024 (Library: OpenSSL 3.0.15 3 Sep 2024)* ThreadX: 26826259 / 2024/09/23 1456
### Kernel info:
* `/proc/cmdline: reboot=w coherent_pool=1M 8250.nr_uarts=1 pci=pcie_bus_safecgroup_disable=memorynuma_policy=interleavesmsc95xx.macaddr=2C678D:E8vc_mem.mem_base=0x3fc00000vc_mem.mem_size=0x40000000console=ttyAMA10,115200console=tty1root=PARTUUID=4825a0d7-02rootfstype=ext4fsck.repair=yesrootwaitquietsplashplymouth.ignore-serial-consolescfg80211.ieee80211_regdom=TH`* Vulnerability Spec store bypass: Mitigation; Speculative Store Bypassdisabledviaprctl* Vulnerability Spectre v1: Mitigation; __user pointer sanitization* Vulnerability Spectre v2: Mitigation; CSV2, BHB* Kernel 6.6.62+rpt-rpi-2712 / CONFIG_HZ=250
All known settings adjusted for performance. Device now ready for benchmarking.Once finished stop with [ctrl]-[c] to get info about throttling, frequencycapand too high background activity all potentially invalidating benchmarkscores.All changes with storage and PCIe devices as well as suspicious dmesgcontentswill be reported too.
Time fake/real load %cpu %sys %usr %nice %io %irq Temp VCore PMIC DC(V)1421: 2400/2400MHz 3.51 2% 0% 2% 0% 0% 0% 73.8°C 0.8945V 2.9W 5.13V^C
Cleaning up. Done.Checking cpufreq OPP again. Done.
Clockspeeds now at 72.7°C:
cpu0 (Cortex-A76): OPP: 2400, ThreadX: 2400, Measured: 2399
Results validation:
* Measured clockspeed not lower than advertised max CPU clockspeed* No swapping* Background activity (%system) OK* No throttling

測(cè)試期間的環(huán)境溫度約為26°C，未發(fā)現(xiàn)降頻現(xiàn)象。然而，在使用CPUminer進(jìn)行運(yùn)算時(shí)，CPU的負(fù)載溫度仍然相當(dāng)高，達(dá)到了79.3°C。而在使用7-zip進(jìn)行多核壓縮時(shí)，CPU溫度從未超過(guò)68.8°C。

看看它與帶有內(nèi)置風(fēng)扇但沒(méi)有散熱片的Raspberry Pi CM5 IO外殼（環(huán)境溫度：32°C）相比如何。

對(duì)于大多數(shù)人來(lái)說(shuō)，Raspberry Pi CM5散熱器應(yīng)該是一個(gè)合適的冷卻系統(tǒng)，但如果你打算在高溫（35°C以上）環(huán)境下或熱量積聚的機(jī)箱內(nèi)運(yùn)行設(shè)備，它可能就不夠了。

順便提一下，我讓CM5套件運(yùn)行了一整夜，下面的圖表顯示了環(huán)境溫度對(duì)CPU空閑溫度的影響。

從16:00時(shí)的46°C降到6:00時(shí)的38°C，同時(shí)室內(nèi)溫度從27°C下降到19°C（根據(jù)天氣預(yù)報(bào)估計(jì)）。

使用上海晶珩 CM5主動(dòng)散熱器 進(jìn)行基準(zhǔn)測(cè)試和CPU溫度監(jiān)測(cè)

現(xiàn)在，讓我們使用主動(dòng)散熱器來(lái)運(yùn)行基準(zhǔn)測(cè)試：

pi@raspberrypi:~ $ sudo ./sbc-bench.sh -rStarting to examine hardware/software for review purposes...
sbc-bench v0.9.68
Installing needed tools: distro packages already installed. Done.Checking cpufreq OPP. Done.Executing tinymembench. Done.Executing RAM latency tester. Done.Executing OpenSSL benchmark. Done.Executing 7-zip benchmark. Done.Throttling test: heating up the device, 5 more minutes to wait. Done.Checking cpufreq OPP again. Done (11 minutes elapsed).
Results validation:
* Measured clockspeed not lower than advertised max CPU clockspeed* No swapping* Background activity (%system) OK* No throttling
Full results uploaded to https://0x0.st/8rH_.txt
# Raspberry Pi Compute Module 5 Rev 1.0
Tested with sbc-bench v0.9.68 on Sun, 22 Dec 2024 1435 +0700. Fullinfo:[https://0x0.st/8rH_.txt](http://0x0.st/8rH_.txt)
### General information:
Information courtesy of cpufetch:
SoC: Broadcom BCM2712Technology: 16nmMicroarchitecture: Cortex-A76Max Frequency: 2.400 GHzCores: 4 coresFeatures: NEON,SHA1,SHA2,AES,CRC32
BCM2712, Kernel: aarch64, Userland: arm64
CPU sysfs topology (clusters, cpufreq members, clockspeeds)cpufreq min maxCPU cluster policy speed speed core type0 0 0 1500 2400 Cortex-A76 / r4p11 0 0 1500 2400 Cortex-A76 / r4p12 0 0 1500 2400 Cortex-A76 / r4p13 0 0 1500 2400 Cortex-A76 / r4p1
4040 KB available RAM
### Governors/policies (performance vs. idle consumption):
Original governor settings:
cpufreq-policy0: ondemand / 2400 MHz (conservative ondemand userspacepowersaveperformanceschedutil/15001600 1700 1800 1900 2000 2100 22002300 2400)
Tuned governor settings:
cpufreq-policy0: performance / 2400 MHz
Status of performance related policies found below /sys:
/sys/module/pcie_aspm/parameters/policy: default [performance] powersavepowersupersave
### Clockspeeds (idle vs. heated up):
Before at 43.0°C:
cpu0 (Cortex-A76): OPP: 2400, ThreadX: 2400, Measured: 2398
After at 65.5°C:
cpu0 (Cortex-A76): OPP: 2400, ThreadX: 2400, Measured: 2399
### Performance baseline
* memcpy: 5707.8 MB/s, memchr: 14187.6 MB/s, memset: 12935.3 MB/s* 16M latency: 118.9 117.1 119.8 117.9 120.3 118.9 141.0 136.2* 128M latency: 133.6 132.5 133.7 142.7 134.3 132.3 133.1 134.4* 7-zip MIPS (3 consecutive runs): 11154, 11152, 11174 (11160 avg), single-threaded:3209* `aes-256-cbc 540286.17k 1003793.09k 1255994.45k 1332805.63k 1365428.91k1367692.63k`* `aes-256-cbc 540545.85k 1003955.39k 1256114.35k 1332834.30k 1364443.14k1367905.62k`
### PCIe and storage devices:
* Raspberry RP1 PCIe 2.0 South Bridge: Speed 5GT/s, Width x4, driver inuse:rp1,* 29.1GB "Samsung BJTD4R" HS400 Enhanced strobe eMMC 5.1 card as /dev/mmcblk0:date07/2024,manfid/oemid:0x000015/0x0100,hw/fwrev: 0x0/0x0300000000000000
### Swap configuration:
* /var/swap on /dev/mmcblk0p2: 512.0M (0K used) on MMC storage
### Software versions:
* Debian GNU/Linux 12 (bookworm)* Build scripts: http://archive.raspberrypi.com/debian/ bookworm main* Compiler: /usr/bin/gcc (Debian 12.2.0-14) 12.2.0 / aarch64-linux-gnu* OpenSSL 3.0.15, built on 3 Sep 2024 (Library: OpenSSL 3.0.15 3 Sep 2024)* ThreadX: 26826259 / 2024/09/23 1456
### Kernel info:
* `/proc/cmdline: reboot=w coherent_pool=1M 8250.nr_uarts=1 pci=pcie_bus_safecgroup_disable=memorynuma_policy=interleavesmsc95xx.macaddr=2C678D:E8vc_mem.mem_base=0x3fc00000vc_mem.mem_size=0x40000000console=ttyAMA10,115200console=tty1root=PARTUUID=4825a0d7-02rootfstype=ext4fsck.repair=yesrootwaitquietsplashplymouth.ignore-serial-consolescfg80211.ieee80211_regdom=TH`* Vulnerability Spec store bypass: Mitigation; Speculative Store Bypassdisabledviaprctl* Vulnerability Spectre v1: Mitigation; __user pointer sanitization* Vulnerability Spectre v2: Mitigation; CSV2, BHB* Kernel 6.6.62+rpt-rpi-2712 / CONFIG_HZ=250
All known settings adjusted for performance. Device now ready for benchmarking.Once finished stop with [ctrl]-[c] to get info about throttling, frequencycapand too high background activity all potentially invalidating benchmarkscores.All changes with storage and PCIe devices as well as suspicious dmesgcontentswill be reported too.
Time fake/real load %cpu %sys %usr %nice %io %irq Temp VCore PMIC DC(V)1436: 2400/2400MHz 3.78 39% 0% 39% 0% 0% 0% 60.6°C 0.8942V 2.6W 5.13V^C
Cleaning up. Done.Checking cpufreq OPP again. Done.
Clockspeeds now at 58.4°C:
cpu0 (Cortex-A76): OPP: 2400, ThreadX: 2400, Measured: 2399
Results validation:
* Measured clockspeed not lower than advertised max CPU clockspeed* No swapping* Background activity (%system) OK* No throttling* ondemand cpufreq governor used by distro but io_is_busy not set to 1onallcores-

環(huán)境溫度約為25°C。沒(méi)有發(fā)生降頻現(xiàn)象，CPU溫度在使用CPUminer時(shí)最高達(dá)到67.2°C，而在使用7-zip時(shí)最高為63.9°C。

它看起來(lái)很不錯(cuò)，但有一個(gè)問(wèn)題是，當(dāng)我關(guān)閉系統(tǒng)時(shí)，風(fēng)扇會(huì)以全速運(yùn)轉(zhuǎn)，而且墻上的電源插座會(huì)顯示有2.3瓦的功耗……

最后的測(cè)試是將CM5主動(dòng)散熱器安裝在IO外殼內(nèi)。在用四個(gè)螺絲將主板固定在底部后，我連接了外部WiFi天線。我還拆除了外殼頂部的風(fēng)扇。

我們最終得到了一個(gè)帶有外殼的完整系統(tǒng)。風(fēng)扇并沒(méi)有完全居中，但對(duì)于獲取冷卻所需的進(jìn)氣口來(lái)說(shuō)已經(jīng)足夠了。

是時(shí)候運(yùn)行sbc-bench.sh的文件測(cè)試了：

pi@raspberrypi:~ $ sudo ./sbc-bench.sh -rStarting to examine hardware/software for review purposes...
sbc-bench v0.9.68
Installing needed tools: distro packages already installed. Done.Checking cpufreq OPP. Done.Executing tinymembench. Done.Executing RAM latency tester. Done.Executing OpenSSL benchmark. Done.Executing 7-zip benchmark. Done.Throttling test: heating up the device, 5 more minutes to wait. Done.Checking cpufreq OPP again. Done (11 minutes elapsed).
Results validation:
* Measured clockspeed not lower than advertised max CPU clockspeed* No swapping* Background activity (%system) OK* No throttling
Full results uploaded to https://0x0.st/8rHy.txt
# Raspberry Pi Compute Module 5 Rev 1.0
Tested with sbc-bench v0.9.68 on Sun, 22 Dec 2024 1429 +0700. Fullinfo:[https://0x0.st/8rHy.txt](http://0x0.st/8rHy.txt)
### General information:
Information courtesy of cpufetch:
SoC: Broadcom BCM2712Technology: 16nmMicroarchitecture: Cortex-A76Max Frequency: 2.400 GHzCores: 4 coresFeatures: NEON,SHA1,SHA2,AES,CRC32
BCM2712, Kernel: aarch64, Userland: arm64
CPU sysfs topology (clusters, cpufreq members, clockspeeds)cpufreq min maxCPU cluster policy speed speed core type0 0 0 1500 2400 Cortex-A76 / r4p11 0 0 1500 2400 Cortex-A76 / r4p12 0 0 1500 2400 Cortex-A76 / r4p13 0 0 1500 2400 Cortex-A76 / r4p1
4044 KB available RAM
### Governors/policies (performance vs. idle consumption):
Original governor settings:
cpufreq-policy0: ondemand / 2400 MHz (conservative ondemand userspacepowersaveperformanceschedutil/15001600 1700 1800 1900 2000 2100 22002300 2400)
Tuned governor settings:
cpufreq-policy0: performance / 2400 MHz
Status of performance related policies found below /sys:
/sys/module/pcie_aspm/parameters/policy: default [performance] powersavepowersupersave
### Clockspeeds (idle vs. heated up):
Before at 44.1°C:
cpu0 (Cortex-A76): OPP: 2400, ThreadX: 2400, Measured: 2399
After at 68.8°C:
cpu0 (Cortex-A76): OPP: 2400, ThreadX: 2400, Measured: 2399
### Performance baseline
* memcpy: 5704.2 MB/s, memchr: 14175.1 MB/s, memset: 12902.3 MB/s* 16M latency: 117.0 116.9 120.3 123.1 120.1 118.7 140.4 133.6* 128M latency: 133.6 132.6 133.9 143.8 133.9 132.2 132.9 134.0* 7-zip MIPS (3 consecutive runs): 11056, 10937, 11060 (11020 avg), single-threaded:3201* `aes-256-cbc 540240.68k 1003708.86k 1256076.37k 1332945.24k 1365475.33k1367780.01k`* `aes-256-cbc 540632.86k 1003822.31k 1256136.02k 1332974.93k 1365194.07k1368216.92k`
### PCIe and storage devices:
* Raspberry RP1 PCIe 2.0 South Bridge: Speed 5GT/s, Width x4, driver inuse:rp1,* 29.1GB "Samsung BJTD4R" HS400 Enhanced strobe eMMC 5.1 card as /dev/mmcblk0:date07/2024,manfid/oemid:0x000015/0x0100,hw/fwrev: 0x0/0x0300000000000000
### Swap configuration:
* /var/swap on /dev/mmcblk0p2: 512.0M (0K used) on MMC storage
### Software versions:
* Debian GNU/Linux 12 (bookworm)* Build scripts: http://archive.raspberrypi.com/debian/ bookworm main* Compiler: /usr/bin/gcc (Debian 12.2.0-14) 12.2.0 / aarch64-linux-gnu* OpenSSL 3.0.15, built on 3 Sep 2024 (Library: OpenSSL 3.0.15 3 Sep 2024)* ThreadX: 26826259 / 2024/09/23 1456
### Kernel info:
* `/proc/cmdline: reboot=w coherent_pool=1M 8250.nr_uarts=1 pci=pcie_bus_safecgroup_disable=memorynuma_policy=interleavesmsc95xx.macaddr=2C678D:E8vc_mem.mem_base=0x3fc00000vc_mem.mem_size=0x40000000console=ttyAMA10,115200console=tty1root=PARTUUID=4825a0d7-02rootfstype=ext4fsck.repair=yesrootwaitquietsplashplymouth.ignore-serial-consolescfg80211.ieee80211_regdom=TH`* Vulnerability Spec store bypass: Mitigation; Speculative Store Bypassdisabledviaprctl* Vulnerability Spectre v1: Mitigation; __user pointer sanitization* Vulnerability Spectre v2: Mitigation; CSV2, BHB* Kernel 6.6.62+rpt-rpi-2712 / CONFIG_HZ=250
All known settings adjusted for performance. Device now ready for benchmarking.Once finished stop with [ctrl]-[c] to get info about throttling, frequencycapand too high background activity all potentially invalidating benchmarkscores.All changes with storage and PCIe devices as well as suspicious dmesgcontentswill be reported too.
Time fake/real load %cpu %sys %usr %nice %io %irq Temp VCore PMIC DC(V)1429: 2400/2400MHz 3.60 49% 0% 49% 0% 0% 0% 63.4°C 0.8948V 2.8W 5.13V1429: 2400/2400MHz 1.32 0% 0% 0% 0% 0% 0% 60.0°C 0.8948V 2.3W 5.13V1429: 2400/2400MHz 0.48 0% 0% 0% 0% 0% 0% 59.5°C 0.8953V 2.7W 5.13V^C
Cleaning up. Done.Checking cpufreq OPP again. Done.
Clockspeeds now at 60.0°C:
cpu0 (Cortex-A76): OPP: 2400, ThreadX: 2400, Measured: 2399
Results validation:
* Measured clockspeed not lower than advertised max CPU clockspeed* No swapping* Background activity (%system) OK* No throttling* ondemand cpufreq governor used by distro but io_is_busy not set to 1onallcores-

環(huán)境溫度仍然保持在25°C左右。CPU溫度在使用CPUminer時(shí)上升到68.3°C，而在使用7-zip時(shí)上升到65.5°C，只比主板不在外殼內(nèi)時(shí)高了幾度。

Raspberry Pi CM5 散熱方案比較

讓我們來(lái)比較一下我們?yōu)镽aspberry Pi CM5測(cè)試過(guò)的四種散熱方案。

只有IO外殼帶風(fēng)扇（沒(méi)有散熱片）的方案出現(xiàn)了CPU降頻，而在環(huán)境溫度為25-26°C時(shí)，無(wú)論是Raspberry Pi CM5散熱器還是上海晶珩 CM5主動(dòng)散熱器都沒(méi)有出現(xiàn)降頻。對(duì)于大多數(shù)人來(lái)說(shuō)，被動(dòng)散熱就足夠了，但如果你的系統(tǒng)設(shè)計(jì)在高溫（35°C以上）環(huán)境下運(yùn)行，或者你希望超頻你的CM5，那么主動(dòng)散熱器可能會(huì)帶來(lái)一些好處。

在CM5 IO板關(guān)閉時(shí)關(guān)閉風(fēng)扇

你還會(huì)注意到，主動(dòng)冷卻系統(tǒng)的關(guān)機(jī)功耗高得驚人，這是因?yàn)橄到y(tǒng)關(guān)閉時(shí)風(fēng)扇會(huì)以全速旋轉(zhuǎn)。Raspberry Pi 最初解釋說(shuō)，“將EEPROM的‘POWER_OFF_ON_HALT=0’設(shè)置應(yīng)該可以固定風(fēng)扇，但會(huì)犧牲一些功耗”。我正準(zhǔn)備嘗試，但在閱讀了該線程的更多內(nèi)容后，發(fā)現(xiàn)這并不起作用。Raspberry Pi于12月19日發(fā)布了一個(gè)修復(fù)程序。新的pieeprom固件尚未通過(guò)apt提供，因此我們需要從Github下載并按照以下步驟進(jìn)行安裝：

wget https://github.com/timg236/rpi-eeprom/raw/927596fc312b6c2ddcf33f7b7608938241403586/firmware-2712/latest/pieeprom-2024-12-19.binsudo rpi-eeprom-update -d -f ./pieeprom-2024-12-19.bin

以下是該命令的輸出結(jié)果：

*** CREATED UPDATE ./pieeprom-2024-12-19.bin ***
CURRENT: Sun Dec 15 1250 AM UTC 2024 (1734221810)UPDATE: Thu Dec 19 1113 AM UTC 2024 (1734609433)BOOTFS: /boot/firmware'/tmp/tmp.4SKLxJWPj1' -> '/boot/firmware/pieeprom.upd'
UPDATING bootloader. This could take up to a minute. Please wait
*** Do not disconnect the power until the update is complete ***
If a problem occurs then the Raspberry Pi Imager may be used to createa bootloader rescue SD card image which restores the default bootloaderimage.
flashrom -p linux_spi:dev=/dev/spidev10.0,spispeed=16000 -w /boot/firmware/pieeprom.updVerifying updateVERIFY: SUCCESSUPDATE SUCCESSFUL

我本來(lái)也打算更改EEPROM配置，但沒(méi)必要了，因?yàn)镻OWER_OFF_ON_HALT已經(jīng)被設(shè)置為零：

pi@raspberrypi:~ $ sudo rpi-eeprom-config[all]BOOT_UART=1POWER_OFF_ON_HALT=0
# Default BOOT_ORDER for provisioning# SD -> NVMe -> USB -> NetworkBOOT_ORDER=0xf2461

這不起作用。雖然使用了新的固件版本，但事實(shí)證明，這是因?yàn)槲矣脕?lái)刷寫(xiě)固件的命令使用了固件中的配置……

pi@raspberrypi:~ $ sudo rpi-eeprom-updateBOOTLOADER: up to dateCURRENT: Thu Dec 19 1113 AM UTC 2024 (1734609433)LATEST: Sun Dec 15 1250 AM UTC 2024 (1734221810)RELEASE: latest (/lib/firmware/raspberrypi/bootloader-2712/latest)Use raspi-config to change the release.pi@raspberrypi:~ $ sudo rpi-eeprom-config[all]BOOT_UART=1BOOT_ORDER=0xf461NET_INSTALL_AT_POWER_ON=1

因此，我不得不使用以下命令行更改配置，并添加‘POWER_OFF_ON_HALT=0’：

sudo rpi-eeprom-config --edit

我們還需要再重啟一次。讓我們最后一次檢查引導(dǎo)加載程序版本和配置文件：

pi@raspberrypi:~ $ sudo rpi-eeprom-config[all]BOOT_UART=1BOOT_ORDER=0xf461NET_INSTALL_AT_POWER_ON=1POWER_OFF_ON_HALT=0pi@raspberrypi:~ $ sudo rpi-eeprom-updateBOOTLOADER: up to dateCURRENT: Sun Dec 15 1250 AM UTC 2024 (1734221810)LATEST: Sun Dec 15 1250 AM UTC 2024 (1734221810)RELEASE: latest (/lib/firmware/raspberrypi/bootloader-2712/latest)Use raspi-config to change the release.

這是怎么回事？看起來(lái)固件又恢復(fù)到了舊版本。這通常是因?yàn)樾碌囊龑?dǎo)加載程序有問(wèn)題，所以它正在使用恢復(fù)映像，但這里看起來(lái)是隨機(jī)的……所以我再次刷寫(xiě)了映像（不使用其配置），并重啟了設(shè)備。這次一切都恢復(fù)正常了，所以我們現(xiàn)在可以準(zhǔn)備關(guān)機(jī)了：

pi@raspberrypi:~ $ sudo rpi-eeprom-updateBOOTLOADER: up to dateCURRENT: Thu Dec 19 1113 AM UTC 2024 (1734609433)LATEST: Sun Dec 15 1250 AM UTC 2024 (1734221810)RELEASE: latest (/lib/firmware/raspberrypi/bootloader-2712/latest)Use raspi-config to change the release.pi@raspberrypi:~ $ sudo rpi-eeprom-config[all]BOOT_UART=1BOOT_ORDER=0xf461NET_INSTALL_AT_POWER_ON=1POWER_OFF_ON_HALT=0pi@raspberrypi:~ $ sudo shutdown now

風(fēng)扇確實(shí)關(guān)閉了，系統(tǒng)關(guān)閉時(shí)的功耗為1.6瓦。如果你想進(jìn)一步降低關(guān)機(jī)時(shí)的功耗，你需要將WAKE_ON_GPIO設(shè)置為0，就像我在Raspberry Pi 5 2GB上所做的那樣。一些HAT可能與此更改不兼容……

我要感謝Raspberry Pi提供了Raspberry Pi CM5開(kāi)發(fā)套件以供評(píng)測(cè)，還要感謝上海晶珩提供了CM5主動(dòng)散熱器，為我們提供了更好的散熱解決方案。