TECHNICAL AND RELIABILITY DATA FOR RASPBERRY PI PRODUCTS (INCLUDING DATASHEETS) AS MODIFIED FROM
TIME TO TIME (“RESOURCES”) ARE PROVIDED BY RASPBERRY PI (TRADING) LTD (“RPTL) "AS IS" AND ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE
LAW IN NO EVENT SHALL RPTL BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THE RESOURCES, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
DAMAGE.
RPTL reserves the right to make any enhancements, improvements, corrections or any other modifications to the
RESOURCES or any products described in them at any time and without further notice.
The RESOURCES are intended for skilled users with suitable levels of design knowledge. Users are solely responsible for
their selection and use of the RESOURCES and any application of the products described in them. User agrees to
indemnify and hold RPTL harmless against all liabilities, costs, damages or other losses arising out of their use of the
RESOURCES.
RPTL grants users permission to use the RESOURCES solely in conjunction with the Raspberry Pi products. All other use
of the RESOURCES is prohibited. No licence is granted to any other RPTL or other third party intellectual property right.
HIGH RISK ACTIVITIES. Raspberry Pi products are not designed, manufactured or intended for use in hazardous
environments requiring fail safe performance, such as in the operation pf nuclear facilities, aircraft navigation or
communication systems, air traffic control, weapons systems or safety-critical applications (including life support
systems and other medical devices), in which the failure of the products could lead directly to death, personal injury or
severe physical or environmental damage (“High Risk Activities”). RPTL specifically disclaims any express or implied
warranty of fitness for High Risk Activities and accepts no liability for use or inclusions of Raspberry Pi products in High
Risk Activities.
Raspberry Pi products are provided subject to RPTL’s Standard Terms. RPTL’s provision of the RESOURCES does not
expand or otherwise modify RPTL’s Standard Terms including but not limited to the disclaimers and warranties expressed
in them.
Figure 1. The
Raspberry Pi Compute
Module 4 (CM4).
The Raspberry Pi Compute Module 4 (CM4) is a System on Module (SoM) containing processor, memory, eMMC Flash
and supporting power circuitry. These modules allow a designer to leverage the Raspberry Pi hardware and software
stack in their own custom systems and form factors. In addition these modules have extra IO interfaces over and above
what is available on the Raspberry Pi boards, opening up more options for the designer.
The design of the CM4 is loosely based on the Raspberry Pi 4, Model B, and for cost sensitive applications it can be
supplied without the eMMC fitted; this version is called the Raspberry Pi Compute Module 4 Lite (CM4Lite).
While previous generations of the Compute Module have all shared the same DDR2-SODIMM-mechanically-compatible
form factor, the new CM4 and CM4Lite are different. The electrical interface of the CM4 is via two 100-pin high density
connectors, and the new physical form factor has a smaller footprint overall when the connectors are taken into account.
This change is due to the addition of new interfaces; an additional second HDMI, PCIe, and Ethernet. The addition of these
new interfaces, especially PCIe, would not have been possible while preserving the previous form factor.
NOTE
Unless otherwise stated, for this document CM4 also refers to CM4Lite.
Options for 1GB, 2GB, 4GB or 8GB LPDDR4-3200 SDRAM (see Appendix B)
•
Options for 0GB (CM4Lite), 8GB, 16GB, or 32GB eMMC Flash memory (see Appendix B)
•
Peak eMMC bandwidth 100MBytes/s (four times faster than previous Compute modules)
◦
Option (see Appendix B) for certified radio module with:
•
2.4 GHz, 5.0 GHz IEEE 802.11 b/g/n/ac wireless
◦
Bluetooth 5.0, BLE
◦
On board electronic switch to select between PCB trace or external antenna
◦
Gigabit Ethernet PHY supporting IEEE 1588
•
1 × PCIe 1-lane Host, Gen 2 ( 5Gbps )
•
1 × USB 2.0 port ( highspeed )
•
28 × GPIO supporting either 1.8v or 3.3v signalling and peripheral options:
•
Up to 6 × UART
◦
Up to 6 × I2C
◦
Up to 5 × SPI
◦
1 × SDIO interface
◦
1 × DPI (Parallel RGB Display)
◦
1 × PCM
◦
Up to 2× PWM channels
◦
Up to 3× GPCLK outputs
◦
2 × HDMI 2.0 ports (up to 4Kp60 supported)
•
MIPI DSI:
•
1 × 2-lane MIPI DSI display port
◦
1 × 4-lane MIPI DSI display port
◦
MIPI CSI-2:
•
1 × 2-lane MIPI CSI camera port
◦
1 × 4-lane MIPI CSI camera port
◦
1 × SDIO 2.0 (CM4Lite)
•
Single +5v PSU input.
•
1.2. Features4
Raspberry Pi Compute Module 4
Chapter 2. Interfaces
2.1. Wireless
The CM4 can be supplied with an onboard wireless module based on the Broadcom BCM43456 supporting both,
2.4 GHz, 5.0 GHz IEEE 802.11 b/g/n/ac wireless
•
Bluetooth 5.0, BLE.
•
These wireless interfaces can be individually enabled or disabled as required. For instance, in the case of a kiosk
application, a service engineer could enable wireless operation and then disable it once finished.
The CM4 has an onboard antenna. If used it should be positioned in the product such that it is not surrounded by metal,
including any ground plane (see Chapter 3 for further details). Alternatively there is a standard U.FL connector on the
module, see Figure 1, so that an external antenna can be used.
Raspberry Pi has an antenna kit which is certified to be used with the CM4. If a different antenna is used then seperate
certification will be required.
WARNING
Raspberry Pi Trading will not be able to assist with certification for third-party antennas.
The selection of internal or external antenna is done at boot time using the config.txt file, and can not be changed during
operation. The config.txt options are dtparam=ant1 to select the internal antenna, or dtparam=ant2 for the external
antenna.
2.1.1. WL_nDisable
This pin serves a number of functions;
1. It can be used to monitor the enable/disable state of wireless networking. A logic high means the wireless
networking module is powered up.
2. When driven or tied low it prevents the wireles network module from powering up. This is useful to reduce power
consumption or in applications where it is required to physically ensure the wireless networking is disabled.
NOTE
On CM4 modules without wireless, this pin is reserved.
2.1.2. BT_nDisable
This pin serves a number of functions;
1. It can be used to monitor the enable/disable state of Bluetooth. A logic high means the Bluetooth module is powered
up.
2. When driven, or tied low, it prevents the Bluetooth module from powering up. This is useful to reduce power
consumption, or in applications where it is required to physically ensure the Bluetooth is disabled.
2.1. Wireless5
Raspberry Pi Compute Module 4
NOTE
On CM4 modules without wireless, this pin is reserved.
2.2. Ethernet
The CM4 has an onboard Gigabit Ethernet PHY — the Broadcom BCM54210PE — some of the major features of this PHY
include;
IEEE 1588-2008 compliant
•
Detection and correction of swapped pairs
•
MDI crossover, pair skew and pair polarity correction
•
A standard 1:1 RJ45 MagJack is all that is necessary to provide an Ethernet connection to the CM4. Typical wiring of a
MagJack supporting POE, and with added ESD protection, can be seen in Figure 2.
Figure 2. Ethernet
schematic interface
for the Raspberry Pi
Compute Module 4
supporting POE, and
with added ESD
protection.
The differential Ethernet signals should be routed as 100Ω differential pairs, with suitable clearances. Length matching
between pairs should be better than 50mm, so in the typical case no length matching is required. However the signals
within a pair need to be length matched, ideally to better than 0.15mm.
The PHY also supports up to 3 LEDs to give user status feedback, these are low active. These LEDs can have a range of
functions, and you should consult your OS driver to see which functions are supported by your driver.
The PHY also provides SYNC_IN and SYNC_OUT at 1.8v signalling to support IEEE 1588-2008.
2.3. PCIe (Gen2 x1)
The CM4 has an internal PCIe 2.0 x1 host controller. While on the Raspberry Pi 4, Model B this has been connected to a
USB 3 host controller (using the Via Labs VLI805), on the CM4 the product designer is free to choose how the interface is
used.
2.2. Ethernet6
Raspberry Pi Compute Module 4
WARNING
You should ensure that there is a suitable OS driver for any host controller that is chosen before proceeding to a
prototype.
Connecting up a PCIe device follows the standard PCIe convention. The CM4 has onboard AC coupling capacitors for CLK
and PCIe_TX signals. However the PCIe_RX signals need external coupling capacitors close to the driving source (the
device TX). Additionally the PCIe_CLK_nREQ must be connected to ensure the CM4 produces a clock signal, and the
PCIe_nRST should also be connected to ensure the device is correctly reset when required.
The differential PCIe signals should be routed as 90Ω differential pairs, with suitable clearances. There is no need to
match the lengths between pairs, only the signals within a Pair need to be length matched ideally to better than 0.1mm.
TIP
The PCIe Interface doesn’t support MSI-X usually PCIe devices will fall back to MSI. There is a limit of upto 32 IRQs
available. If the device has problems with interupts then adding pci=nomsi to cmdline.txt (and reboot) often fixes the
issue.
2.4. USB 2.0 (Highspeed)
The USB 2.0 interface supports up to 480MBps signalling. The differential pair should be routed as a 90Ω differential pair.
The P N signals should ideally be matched to 0.15mm
TIP
The USB interface is disabled to save power by default on the CM4 . To enable it you need to add
dtoverlay=dwc2,dr_mode=host to the config.txt file
NOTE
The port is capable of being used as a true USB On-The-Go (OTG) port. While there is no official documentation, some
users have had success making this work. The USB_OTG pin is used to select between USB host and device that is
typically wired to the ID pin of a Micro usb connector. To use this functionality it must be enabled in the OS that is
used. If using either as a fixed slave or fixed master, please tie the USB OTGID pin to ground
2.5. GPIO
There are 28 pins available for general purpose I/O (GPIO), which correspond to the GPIO pins on the Raspberry Pi 4,
Model B 40-pin header. These pins have access to internal peripherals; I2C, PWM, SPI, and UART. The BCM2711 ARM
Peripherals book describes these features in detail, and the multiplexing options available. The drive strength and slew
rate should ideally be set as low as possible to reduce any EMC issues.
The SOC GPIO bank is powered by GPIO_VREF, this can either be connected to the +1.8v from the CM4 for 1.8v signalling
GPIO, or +3.3v from the CM4 for +3.3v signalling. You should keep the load on the 28 GPIO pins to below 50mA in total.
2.6. Dual HDMI 2.0
The CM4 supports two HDMI 2.0 interfaces each one capable of driving 4K images. If both HDMI outputs are used then
each can be driven upto 4Kp30, however if only HDMI0 interface is being used then images up to 4Kp60 are possible.
HDMI signals should be routed as 100Ω differential pairs, each signal within a pair should ideally be matched to better
2.4. USB 2.0 (Highspeed)7
Raspberry Pi Compute Module 4
than 0.15mm. Pairs don’t typically need any extra matching as they only have to be matched to 25mm.
CEC is also supported, an internal 27K pullup resistor is included in the CM4.
Basic onboard ESD protection is provided for the I2C EDID signals and the CEC signals, internal pullup and down resistors
are also provided. On the {rpi4} the HDMI signals don’t have any extra ESD protection , depending on the application extra
ESD protection maybe required.
2.7. CSI-2 (MIPI Serial Camera)
The CM4 supports two camera ports; CAM0 (2 lanes) and CAM1 (4 lanes). CSI signals should be routed as 100Ω differential
pairs, each signal within a pair should ideally be matched to better than 0.15mm.
The documentation around the CSI interface can be found on the Raspberry Pi website while Linux kernel drivers can be
found on Github.
NOTE
Camera sensors supported by the official Raspberry Pi firmware are; the OmniVision OV5647, Sony IMX219 and Sony
IMX477, no security device is required on Compute Module devices to use these camera sensors.
2.8. DSI (MIPI Serial Display)
The CM4 supports two display ports; DISP0 (2 lanes) and DISP1 (4 lanes). Each lane supports a maximum of data rate per
lane of 1Gbit/s.
Although Linux kernel drivers are available, the DSI interface is not currently documented. Only DSI displays supported by
the official Raspberry Pi firmware are supported, DSI signals should be routed as 100Ω differential pairs, each signal
within a pair should ideally be matched to better than 0.15mm.
NOTE
While only official DSI displays are supported, other displays can be added using the parallel DPI interface which is
available as a GPIO alternate function. The CM4 supports up to 3 displays of any type (HDMI, DSI, DPI) at any one time.
2.9. I2C (SDA0 SCL0)
This internal I2C bus is normally allocated to the CSI1 and DSI1 as these devices are controlled by the firmware. It can be
used as a general I2C bus if the CSI1 ad DSI1 interfaces aren’t being used or are being controlled by the firmware. For
example libcamera runs on the ARM and doesn’t use the firmware so in this case you may use CSI1 and this I2C bus.
2.10. I2C (ID_SD ID_SC)
This I2C bus is normally used for identifying HATs and controlling CSI0 and DSI1 devices. If the firmware isn’t using the
I2C bus e.g. CSI0 and DSI0 aren’t being used then these pins may be used if required.
2.11. SDIO/eMMC (CM4Lite only)
If the CM4Lite is used, which does not have on-board eMMC, then the eMMC signals are available on the connector so
that an external eMMC or SDCARD can be used.
The SD_PWR_ON signal is used to enable an external power switch to turn on power to the SDCARD, for eMMC it typically
2.7. CSI-2 (MIPI Serial Camera)8
Raspberry Pi Compute Module 4
isn’t used. When SD_VDD_override is high, this signal is used to force 1.8v signalling on the SDIO interface. Typically this is
used with eMMC memory.
Figure 3. CM4Lite
SDCARD interface.
2.12. Analog IP0/IP1
These are the two spare inputs on the MXL7704. The MXL7704 datasheet should be consulted if these pins are to be
used. Onboard filtering is provided by a 100nF capacitor to ground for each signal. On the Raspberry Pi 4, Model B these
are connected to the USB C connector CC1 and CC2 pins.
2.13. Global_EN
Pulling this pin low puts the CM4 in the lowest possible power down state. After software shutdown Global_EN needs to
be pulled low for > 1ms to restart the power system on the CM4.
TIP
It is recommended to only pull this pin low once the OS has shutdown.
2.14. RUN_PG
This pin when high signals that the CM4 has started. Driving this pin low resets the module, this should be done with
caution as if files on a filesystem are open they will not be closed.
2.15. nRPI_BOOT
During boot if this pin is low booting from eMMC will be stopped and booting will be transferred to rpi boot which is via
USB.
2.12. Analog IP0/IP19
Raspberry Pi Compute Module 4
2.16. LED_nACT
This pin is designed to drive an LED to replicate the green LED on the Raspberry Pi 4, Model B. Under Linux this pin will
flash to signify eMMC access, while if there is an error during booting this LED will flash error patterns which can be
decoded using the look up table on the Raspberry Pi website.
2.17. LED_PWR
This pin needs to be buffered to drive an LED. The signal is designed to replicate the red power LED on the Raspberry Pi 4,
Model B.
2.18. EEPROM_nWP
It is recommended that final products pull this pin low to prevent the end users changing the contents of the on board
EEPROM. See the Raspberry Pi 4, Model B documentation for instructions on the software settings required to support
EEPROM Write protection .
2.16. LED_nACT10
Raspberry Pi Compute Module 4
Chapter 3. Electrical and Mechanical
3.1. Mechanical
The CM4 is a compact 40 × 55mm module. The Module is 4.7mm deep, but when connected the height will be 5.078 or
3. BCM2711 SOC height including solder balls 2.378 ± 0.11mm
4. Stacking height either:
a. 1.5mm with mating connector (clearance under CM4 0mm) : DF40C-100DS-0.4v
b. 3.0mm with mating connector (clearance under CM4 1.5mm): DF40HC(3.0)-100DS-0.4v
Figure 4. Mechanical
specification of the
Raspberry Pi Compute
Module 4
If the on board wireless antenna is used (see Section 2.1) it must be orientated towards the edge of the plastic enclosure
and any close by metal must have cut outs or the wireless performance will be degraded. It is suggested that there is at
least 10mm clearance around the PCB antenna, but the designer must check the performance.
There must not be any metal, including ground planes, under the antenna. The ground plane cutout must be a minimum
of 6.5mm × 11mm, but ideally at least 8mm × 15mm. If these requirements can’t be met wireless performance may be
degraded, especially in the 2.4GHz spectrum. It is recommended that the external antenna is used where possible.
3.1. Mechanical11
Raspberry Pi Compute Module 4
NOTE
The location and arrangement of components on the Compute Module may change slightly over time due to revisions
for cost and manufacturing considerations; however the maximum component heights and PCB thickness will be kept
as specified.
A step file of the CM4 is available as part of the CM4 design data package, this is for guidance only and is subject to
changes over time due to revisions.
3.2. Thermal
The CM4 dissipates less power than the Raspberry Pi 4, Model B as it has less metal in the PCB and connectors so it has
less passive heat sinking. Therefore despite it consuming less power it may run warmer than the Raspberry Pi 4, Model B.
The BCM2711 will reduce the clock rate to try and keep its temperature below 85°C. So in high ambient temperatures it is
possible that the clock will also be automatically throttled back.
Operating temperature range: 0°C - 80°C
Table 1. Absolute
maximum ratings
Table 2. DC
characteristics
3.3. Electrical Specification
WARNING
Stresses above those listed in Table 2 may cause permanent damage to the device. This is a stress rating only;
functional operation of the device under these or any other conditions above those listed in the operational sections of
this specification is not implied. Exposure to absolute maximum rating conditions for extended periods may affect
device reliability.
19Ethernet_nLED1Low Active Ethernet speed indicator ( 3.3V signal) Typically a Yellow LED is connected to
this pin. A low State indicates the 1Gbit or 10Mbit Link : IOL = 8mA @ VOL< 0.4V
20EEPROM_nWP
21Pi_nLED_ActivityLow Active Pi Activity LED. 20mA Max 5V tolerant ( VOL<0.4V). ( this is the signal that drives
22GNDGround (0V)
23GNDGround (0V)
24GPIO26GPIO Typically a 3.3V signal but can be a 1.8V signal by connecting GPIO_Vref to 1.8V
25GPIO21GPIO Typically a 3.3V signal but can be a 1.8V signal by connecting GPIO_Vref to 1.8V
26GPIO19GPIO Typically a 3.3V signal but can be a 1.8V signal by connecting GPIO_Vref to 1.8V
27GPIO20GPIO Typically a 3.3V signal but can be a 1.8V signal by connecting GPIO_Vref to 1.8V
28GPIO13GPIO Typically a 3.3V signal but can be a 1.8V signal by connecting GPIO_Vref to 1.8V
Leaving floating NB internally pulled up to CM4_3.3V via 100K ( VIL <0.8V) but can be
grounded to prevent writing to the on board EEPROM which stores the bootcode
the Green LED on the Raspberry Pi 4, Model B )
29GPIO16GPIO Typically a 3.3V signal but can be a 1.8V signal by connecting GPIO_Vref to 1.8V
30GPIO6GPIO Typically a 3.3V signal but can be a 1.8V signal by connecting GPIO_Vref to 1.8V
Chapter 4. Pin Out14
Raspberry Pi Compute Module 4
31GPIO12GPIO Typically a 3.3V signal but can be a 1.8V signal by connecting GPIO_Vref to 1.8V
32GNDGround (0V)
33GNDGround (0V)
34GPIO5GPIO Typically a 3.3V signal but can be a 1.8V signal by connecting GPIO_Vref to 1.8V
35ID_SCGPIO Typically a 3.3V signal but can be a 1.8V signal by connecting GPIO_Vref to 1.8V
36ID_SDGPIO Typically a 3.3V signal but can be a 1.8V signal by connecting GPIO_Vref to 1.8V
37GPIO7GPIO Typically a 3.3V signal but can be a 1.8V signal by connecting GPIO_Vref to 1.8V
38GPIO11GPIO Typically a 3.3V signal but can be a 1.8V signal by connecting GPIO_Vref to 1.8V
39GPIO8GPIO Typically a 3.3V signal but can be a 1.8V signal by connecting GPIO_Vref to 1.8V
40GPIO9GPIO Typically a 3.3V signal but can be a 1.8V signal by connecting GPIO_Vref to 1.8V
41GPIO25GPIO Typically a 3.3V signal but can be a 1.8V signal by connecting GPIO_Vref to 1.8V
42GNDGround (0V)
43GNDGround (0V)
44GPIO10GPIO Typically a 3.3V signal but can be a 1.8V signal by connecting GPIO_Vref to 1.8V
45GPIO24GPIO Typically a 3.3V signal but can be a 1.8V signal by connecting GPIO_Vref to 1.8V
46GPIO22GPIO Typically a 3.3V signal but can be a 1.8V signal by connecting GPIO_Vref to 1.8V
47GPIO23GPIO Typically a 3.3V signal but can be a 1.8V signal by connecting GPIO_Vref to 1.8V
48GPIO27GPIO Typically a 3.3V signal but can be a 1.8V signal by connecting GPIO_Vref to 1.8V
49GPIO18GPIO Typically a 3.3V signal but can be a 1.8V signal by connecting GPIO_Vref to 1.8V
50GPIO17GPIO Typically a 3.3V signal but can be a 1.8V signal by connecting GPIO_Vref to 1.8V
51GPIO15GPIO Typically a 3.3V signal but can be a 1.8V signal by connecting GPIO_Vref to 1.8V
52GNDGround (0V)
53GNDGround (0V)
54GPIO4GPIO Typically a 3.3V signal but can be a 1.8V signal by connecting GPIO_Vref to 1.8V
55GPIO14GPIO Typically a 3.3V signal but can be a 1.8V signal by connecting GPIO_Vref to 1.8V
56GPIO3GPIO Typically a 3.3V signal but can be a 1.8V signal by connecting GPIO_Vref to 1.8V.
Internal 1.8K pull up to GPIO_Vref
57SD_CLKSDCARD Clock signal (only available on CM4Lite)
58GPIO2GPIO Typically a 3.3V signal but can be a 1.8V signal by connecting GPIO_Vref to 1.8V.
Internal 1.8K pull up to GPIO_Vref
59GNDGround (0V)
60GNDGround (0V)
61SD_DAT3SDCARD/eMMC Data3 signal (only available on CM4Lite)
62SD_CMDSDCARD/eMMC Command signal (only available on CM4Lite)
63SD_DAT0SDCARD/eMMC Data0 signal (only available on CM4Lite)
64SD_DAT5SDCARD/eMMC Data5 signal (only available on CM4Lite)
65GNDGround (0V)
Chapter 4. Pin Out15
Raspberry Pi Compute Module 4
66GNDGround (0V)
67SD_DAT1SDCARD/eMMC Data1 signal (only available on CM4Lite)
68SD_DAT4SDCARD/eMMC Data4 signal (only available on CM4Lite)
69SD_DAT2SDCARD/eMMC Data2 signal (only available on CM4Lite)
70SD_DAT7SDCARD/eMMC Data7 signal (only available on CM4Lite)
71GNDGround (0V)
72SD_DAT6SDCARD/eMMC Data6 signal (only available on CM4Lite)
73SD_VDD_OverrideForce SDCARD/eMMC interface to 1.8V signalling if set to 3.3V, otherwise leave
74GNDGround (0V)
75SD_PWR_ONOutput to Power switch for SDCARD. CM4 sets this pin High (3.3V) to signal that Power to
76ReservedDo not Connect anything to this pin.
unconnected. Typically only used if external eMMC is connected
the SDCARD should be turned on. If booting from the SDCARD is required then a pullup
should be fitted (only available on CM4Lite)
77+5V (Input)4.75V-5.25V Main power input
78GPIO_VREF
79+5V (Input)4.75V-5.25V Main power input
80SCL0IIC Clock pin ( Raspberry Pi GPIO45) Typically used for Camera and Displays Internal 1.8K
81+5V (Input)4.75V-5.25V Main power input
82SDA0IIC Data pin ( Raspberry Pi GPIO44 ) Typically used for Camera and Displays Internal 1.8K
83+5V (Input)4.75V-5.25V Main power input
84CM4_3.3V (Output)3.3V +/-2.5% Power Output max 300mA per pin for a total of 600mA. This will be powered
85+5V (Input)4.75V-5.25V Main power input
86CM4_3.3V (Output)3.3V +/-2.5% Power Output max 300mA per pin for a total of 600mA. This will be powered
87+5V (Input)4.75V-5.25V Main power input
88CM4_1.8V (Output)1.8V +/-2.5% Power Output max 300mA per pin for a total of 600mA. This will be powered
Must be connected to CM4_3.3V ( pins 84 and 86 ) for 3.3V GPIO or CM4_1.8V ( pins 88 and
90) for 1.8V GPIO. This pin cannot be floating or connected to ground
pull up to CM4_3.3V
pull up to CM4_3.3V
down during power off or GLOBAL_EN being set low
down during power off or GLOBAL_EN being set low
down during power off or GLOBAL_EN being set low
89WL_nDisableCan be left floating if driven low the wireless interface will be disabled. Internal pulled up via
1.8K to CM4_3.3V
90CM4_1.8V (Output)1.8V +/-2.5% Power Output max 300mA per pin for a total of 600mA. This will be powered
down during power off or GLOBAL_EN being set low
91BT_nDisableCan be left floating if driven low the Bluetooth interface will be disabled. Internal pulled up
via 1.8K to CM4_3.3V
92RUN_PGBidirectional pin. Can be driven low ( via a 220R resistor) to Reset the CM4 CPU. As an
Output a high signals Power Good and CPU running. Internally pulled up to +3.3V via 10K
Chapter 4. Pin Out16
Raspberry Pi Compute Module 4
93nRPIBOOTA low on this pin force booting from an RPI server ( e.g PC or a Raspberry Pi)Ê if not used
94AnalogIP1Analogue input of the MAX7704. Typically connected to CC pin of Type C power connector
95PI_LED_nPWRLow active Output to drive Power On LED. This signal needs to be buffered.
96AnalogIP0Analogue input of the MAX7704. Typically connected to CC pin of Type C power connector
97Camera_GPIOTypically used to Shutdown the camera to reduce power. Reassigning this pin to another
98GNDGround (0V)
99GLOBAL_ENInput. Drive low to power off CM4. Internally pulled up with a 100K to +5V
leave floating. Internally pulled via 10K to +3.3V
function isn’t recommended. CM4_3.3V signalling
100 nEXTRST
101 USB_OTG_IDInput ( 3.3V signal ) USB OTG Pin. Internal pulled up. When grounded the CM4 becomes a
102 PCIe_CLK_nREQInput ( 3.3V signal) PCIe Clock request pin (low to request PCI clock). Internal pulled up
103 USB_NUSB D-
104 ReservedDo not Connect anything to this pin.
105 USB_PUSB D+
106 ReservedDo not Connect anything to this pin.
107 GNDGround (0V)
108 GNDGround (0V)
109 PCIe_nRSTOutput (+3.3V signal) PCIe Reset Low active
110 PCIe_CLK_PPCIe Clock Out Positive (100MHz) NB AC coupling Capacitor Included on CM4
111 VDAC_COMPVideo DAC output (TV OUT)
112 PCIe_CLK_NPCIe Clock Out Negative (100MHz) NB AC coupling Capacitor Included on CM4
113 GNDGround (0V)
114 GNDGround (0V)
Output Driven low during reset Driven high (CM4_3.3V) once CM4 CPU has started to boot
USB host but the correct OS driver also needs to be used
115 CAM1_D0_NInput Camera1 D0 Negative
116 PCIe_RX_PInput PCIe GEN 2 RX Positive NB External AC coupling Capacitor required
117 CAM1_D0_PInput Camera1 D0 Positive
118 PCIe_RX_NInput PCIe GEN 2 RX Negative NB External AC coupling Capacitor required
119 GNDGround (0V)
120 GNDGround (0V)
121 CAM1_D1_NInput Camera1 D1 Negative
122 PCIe_TX_POutput PCIe GEN 2 TX Positive NB AC coupling Capacitor Included on CM4
123 CAM1_D1_PInput Camera1 D1 Positive
124 PCIe_TX_NOutput PCIe GEN 2 TX Positive NB AC coupling Capacitor Included on CM4
125 GNDGround (0V)
126 GNDGround (0V)
127 CAM1_C_NInput Camera1 Clock Negative
Chapter 4. Pin Out17
Raspberry Pi Compute Module 4
128 CAM0_D0_NInput Camera0 D0 Negative
129 CAM1_C_PInput Camera1 Clock Positive
130 CAM0_D0_PInput Camera0 D0 Positive
131 GNDGround (0V)
132 GNDGround (0V)
133 CAM1_D2_NInput Camera1 D2 Negative
134 CAM0_D1_NInput Camera0 D1 Negative
135 CAM1_D2_PInput Camera1 D2 Positive
136 CAM0_D1_PInput Camera0 D1 Positive
137 GNDGround (0V)
138 GNDGround (0V)
139 CAM1_D3_NInput Camera1 D3 Negative
140 CAM0_C_NInput Camera0 Clock Negative
141 CAM1_D3_PInput Camera1 D3 Positive
142 CAM0_C_PInput Camera0 Clock Positive
143 HDMI1_HOTPLUGInput HDMI1 Hotplug Internally pulled down with a 100K. 5V tolerant. (It can be connected
directly to a HDMI connector a small amount of ESD protection is provided on the CM4 by
an on board HDMI05-CL02F3)
144 GNDGround (0V)
145 HDMI1_SDABidir HDMI1 SDA Internally pulled up with a 1.8K. 5V tolerant. (It can be connected directly
to a HDMI connector a small amount of ESD protection is provided on the CM4 by an on
board HDMI05-CL02F3)
146 HDMI1_TX2_POutput HDMI1 TX2 Positive
147 HDMI1_SCLInput HDMI1 SCL Internally pulled up with a 1.8K. 5V tolerant. (It can be connected directly
to a HDMI connector a small amount of ESD protection is provided on the CM4 by an on
board HDMI05-CL02F3)
148 HDMI1_TX2_NOutput HDMI1 TX2 Negative
149 HDMI1_CECInput HDMI1 CEC Internally pulled up with a 27K. 5V tolerant. (It can be connected directly
to a HDMI connector a small amount of ESD protection is provided on the CM4 by an on
board HDMI05-CL02F3)
150 GNDGround (0V)
151 HDMI0_CECInput HDMI0 CEC Internally pulled up with a 27K. 5V tolerant (It can be connected directly
to a HDMI connector a small amount of ESD protection is provided on the CM4 by an on
board HDMI05-CL02F3)
152 HDMI1_TX1_POutput HDMI1 TX1 Positive
153 HDMI0_HOTPLUGInput HDMI0 Hotplug Internally pulled down 100K. 5V tolerant. (It can be connected directly
to a HDMI connector a small amount of ESD protection is provided on the CM4 by an on
board HDMI05-CL02F3)
154 HDMI1_TX1_NOutput HDMI1 TX1 Negative
155 GNDGround (0V)
156 GNDGround (0V)
Chapter 4. Pin Out18
Raspberry Pi Compute Module 4
157 DSI0_D0_NOutput Display0 D0 Negative
158 HDMI1_TX0_POutput HDMI1 TX0 Positive
159 DSI0_D0_POutput Display0 D0 Positive
160 HDMI1_TX0_NOutput HDMI1 TX0 Negative
161 GNDGround (0V)
162 GNDGround (0V)
163 DSI0_D1_NOutput Display0 D1 Negative
164 HDMI1_CLK_POutput HDMI1 Clock Positive
165 DSI0_D1_POutput Display0 D1 Positive
166 HDMI1_CLK_NOutput HDMI1 Clock Negative
167 GNDGround (0V)
168 GNDGround (0V)
169 DSI0_C_NOutput Display0 Clock Negative
170 HDMI0_TX2_POutput HDMI0 TX2 Positive
171 DSI0_C_POutput Display0 Clock Positive
172 HDMI0_TX2_NOutput HDMI0 TX2 Negative
173 GNDGround (0V)
174 GNDGround (0V)
175 DSI1_D0_NOutput Display1 D0 Negative
176 HDMI0_TX1_POutput HDMI0 TX1 Positive
177 DSI1_D0_POutput Display1 D0 Positive
178 HDMI0_TX1_NOutput HDMI0 TX1 Negative
179 GNDGround (0V)
180 GNDGround (0V)
181 DSI1_D1_NOutput Display1 D1 Negative
182 HDMI0_TX0_POutput HDMI0 TX0 Positive
183 DSI1_D1_POutput Display1 D1 Positive
184 HDMI0_TX0_NOutput HDMI0 TX0 Negative
185 GNDGround (0V)
186 GNDGround (0V)
187 DSI1_C_NOutput Display1 Clock Negative
188 HDMI0_CLK_POutput HDMI0 Clock Positive
189 DSI1_C_POutput Display1 Clock Positive
190 HDMI0_CLK_NOutput HDMI0 Clock Negative
191 GNDGround (0V)
192 GNDGround (0V)
193 DSI1_D2_NOutput Display1 D2 Negative
Chapter 4. Pin Out19
Raspberry Pi Compute Module 4
194 DSI1_D3_NOutput Display1 D3 Negative
195 DSI1_D2_POutput Display1 D2 Positive
196 DSI1_D3_POutput Display1 D3 Positive
197 GNDGround (0V)
198 GNDGround (0V)
199 HDMI0_SDABidir HDMI0 SDA Internally pulled up with a 1.8K. 5V tolerant. (It can be connected directly
200 HDMI0_SCLBidir HDMI0 SCL Internally pulled up with a 1.8K. 5V tolerant. (It can be connected directly
All ground pins should be connected. If none of the signals on the second connector pins 101 to 200 are used then you
may not fit the connector to reduce costs, but mechanical stablity needs to be considered.
The voltage on GPIO pins 0-27 must not exceed CM4_3.3V if +3.3V signalling is used or CM4_1.8V if +1.8V signalling is
used. These pins are the same as on the 40-pin connector on the Raspberry Pi 4, Model B.
to a HDMI connector a small amount of ESD protection is provided on the CM4 by an on
board HDMI05-CL02F3)
to a HDMI connector a small amount of ESD protection is provided on the CM4 by an on
board HDMI05-CL02F3)
If the CM4_1.8V rail is use to power other devices other than the GPIO_Vref then you should ensure that in case of surprise
power removal ( e.g.the +5V pin goes below +4.5V ) from the CM4, the load on the CM4_1.8V must go to zero.
Similarly if the CM4_3.3V rail is used to power other devices other than the GPIO_Vref, then you should ensure that in the
case surprise power removal the CM4_3.3V rail never fails below the CM4_1.8V rail. This is the typical case, but you should
check this in your design. In the case where it does fall below the CM4_1.8V rail, then extra circuitry is required to
disconnect the CM4_3.3V load
No reverse voltage must be applied to any pin or power up may be prevented, i.e. during power down/off no pin may have
external voltage applied otherwise this may prevent power up.
4.1. Differential Pairs
It is recommended that P/N signals within a pair are matched to better 0.15mm. Often matching between pairs is not so
critical, e.g. HDMI pair to pair matching should be better than 25mm so on a typical board no extra matching is required.
4.1.1. 100Ω Differential pairs signal lengths
On the CM4 all differential pairs are matched to better than 0.05mm (P/N signals).
NOTE
It is recommended that pairs are also matched on the interface board.
On the CM4 pair to pairs aren’t always matched as many interfaces don’t require very accurate matching between pairs.
Table 4 documents the CM4 track length difference within each group (a non zero value is how much longer in mm that
track is compared to the signal with zero length difference)
Table 4. 100 Ω
Differential paris
signal length
4.1. Differential Pairs20
SignalLength
CAM0_C_N0.02
CAM0_C_P0.02
CAM0_D0_N0.06
Raspberry Pi Compute Module 4
CAM0_D0_P0.07
CAM0_D1_N0
CAM0_D1_P0.01
CAM1_C_N0.78
CAM1_C_P0.78
CAM1_D0_N0.02
CAM1_D0_P0.01
CAM1_D1_N0.4
CAM1_D1_P0.4
CAM1_D2_N0.05
CAM1_D2_P0.04
CAM1_D3_N0.01
CAM1_D3_P0
DSI0_C_N0
DSI0_C_P0
DSI0_D0_N0
DSI0_D0_P0
DSI0_D1_N0.01
DSI0_D1_P0.01
DSI1_C_N1.28
DSI1_C_P1.28
DSI1_D0_N0
DSI1_D0_P0.01
DSI1_D1_N1.06
DSI1_D1_P1.06
DSI1_D2_N0.83
DSI1_D2_P0.84
DSI1_D3_N3.78
DSI1_D3_P3.79
HDMI0_CLK_N3.25
HDMI0_CLK_P3.24
HDMI0_TX0_N1.76
HDMI0_TX0_P1.76
HDMI0_TX1_N0.62
4.1. Differential Pairs21
Raspberry Pi Compute Module 4
HDMI0_TX1_P0.62
HDMI0_TX2_N0
HDMI0_TX2_P0
HDMI1_CLK_N2.47
HDMI1_CLK_P2.46
HDMI1_TX0_N1.51
HDMI1_TX0_P1.51
HDMI1_TX1_N1
HDMI1_TX1_P1
HDMI1_TX2_N0
HDMI1_TX2_P0.01
Ethernet_Pair0_P5.23
Table 5. 90 Ω
Differential paris
signal length
Ethernet_Pair0_N5.23
Ethernet_Pair1_P0
Ethernet_Pair1_N0
Ethernet_Pair2_P3.82
Ethernet_Pair2_N3.82
Ethernet_Pair3_P4.29
Ethernet_Pair3_N4.29
4.1.2. 90Ω Differential Pairs signal lengths
On the CM4 all differential pairs are matched to better than 0.05mm (P/N signals).
NOTE
It is recommended that pairs are also matched on the interface board.
However pair to pairs aren’t always matched as many interfaces don’t require very accurate matching between pairs.
Table 5 documents the CM4 track length difference within each group (a non zero value is how much longer in mm that
track is compared to the signal with zero length difference)
SignalLength
PCIe_CLK_P0.65
PCIe_CLK_N0.65
PCIe_TX_P0
PCIe_TX_N0
PCIe_RX_P0.23
PCIe_RX_N0.23
4.1. Differential Pairs22
Raspberry Pi Compute Module 4
USB2_P0
USB2_N0
4.1. Differential Pairs23
Raspberry Pi Compute Module 4
Chapter 5. Power
5.1. Power up sequencing
The CM4 requires a single +5V supply, and can supply up to 600mA at +3.3V and +1.8V to peripherals.
All pins should not have any power applied to them before the +5V rail is applied.
If the EEPROM is to be write protected then the EEPROM_nWP should be low before powerup.
If the CM4 is to be booted using USB then RPI_nBOOT needs to be low within 2ms of +5V rising.
+5V should rise monotonically to 4.75V and stay above 4.75V for the entire operation of the CM4.
The power up sequence will start when both +5V rall is above 4.75V and GLOBAL_EN rises. GLOBAL_EN has internal RC delay
so that it rises after +5V has risen. The order of events is as follows
1. +3.3V rises
2. +1.8V rises
3.
RUN_PG rises
4.
EXT_nRESET rises
5.2. Power down sequencing
The OS should be shut down to ensure that the file system remains consistent, before the power is removed. If this can’t
be achieved, then a filesystem like btrfs, f2fs or overlayfs ( use raspi-config to enable it ) should be considered.
Once the OS has shutdown the +5V rail can be removed or the GLOBAL_EN pin can be taken low to put the CM4 into the low
power mode.
5.1. Power up sequencing24
Raspberry Pi Compute Module 4
Appendix A: Troubleshooting
The CM4 has a number of stages of power up before the CPU starts. If there is an error at any of the stages, power up will
be halted.
Hardware Checklist
1.
Is the +5V supply good? Check this by pulling GLOBAL_EN low apply and apply an external 2A load to the +5V supply.
Does it stay >+4.75V including noise? Ideally it should remain >+4.9V including any noise.
2.
Remove external 2A load, but keep GLOBAL_EN pulled low.
3. Check the CM4 +3.3v rail is <200mV. If this is not the case there is an external power path back-feeding the CM4,
either directly or indirectly. This could also occur via the digital pins, e.g Ethernet.
4.
Still with GLOBAL_EN pulled low check the CM4 +1.8v rail is <200mW. Again if the +1.8v rail is above 200mV then there
is an external path back feeding the 1.8v rail. (If nothing is connected to these pins you can ignore this check.)
5.
Remove the pull down on GLOBAL_EN.
6.
Check GLOBAL_EN now goes high (it internally pulled up on the CM4)
7. Check the +3.3V supply rises to >+3.15V. If it does not, this suggests there is too much load on the +3.3V rail.
8. Check the +1.8V rail gets to >+1.71v. If it does not, this suggests there is much load on the +1.8V rail.
9.
Check RUN_PG goes high
10.
Check ACT_LED starts to oscillate to indicate booting check it isn’t flashing an error code.
Bootloader
1. Connect a HDMI cable to see if the HDMI diagnostics screen appears.
2. Connect a USB serial cable to GPIO pins 14,15.
a. See https://www.raspberrypi.org/documentation/configuration/uart.md for details.
3.
Short the nRPIBOOT pin to ground to force USB boot mode. The CM4IO board has a jumper for nRPIBOOT This can be
used to enable different boot modes (e.g. network) and enable UART logging.
a. See https://www.raspberrypi.org/documentation/hardware/computemodule/cm-emmc-flashing.md
rpi-eeprom-update
1.
CM4 will not run recovery.bin from from the EMMC (or SD Card on CM4Lite). Therefore, the only way to update the
bootloader EEPROM is via usbboot or self-update.
EEPROM Write protect
The on board EEPROM can be write protected by shorting to ground EEPROM_nWP. The CM4IO board has a jumper for
EEPROM_nWP.
1. See https://www.raspberrypi.org/documentation/hardware/raspberrypi/bcm2711_bootloader_config.md
Hardware Checklist25
Raspberry Pi Compute Module 4
Firmware
1. A 5.4 or newer kernel and the latest firmware release is required. These can be updated by using usbboot to mount
the EMMC as a USB MSD device but you must use the updated usbboot binaries in the alpha test folder.
2.
Nightly OS images are now available which contain rpi-update master firmware + kernel. Bug fixes for CM4 will
normally be provided via these images except where a test/patch binary is required.
a. See http://downloads.raspberrypi.org/nightlies/
Kernel
1. The updated OS images use the new Raspberry Pi Compute Module 4 device tree file. If that is not found then the
Raspberry Pi 4, Model B device tree file will be used.
a. See https://github.com/raspberrypi/linux/blob/rpi-5.4.y/arch/arm/boot/dts/bcm2711-rpi-cm4.dts
Firmware26
Raspberry Pi Compute Module 4
Appendix B: Availability
Raspberry Pi guarantees availability of the CM4 until at least January 2028.
Support
For support please see the hardware documentation section of the Raspberry Pi website and post questions to the
RRP was correct at time of publication and excludes taxes.
Some options have minimum ordering qualities (MOQ), please check with your supplier.
For prototyping often a higher LPDDR RAM capacity option will exist, without an MOQ. You can use the higher LPDDR
RAM option, but limit it to the lower capacity by changing config.txt.
Packaging
Small quantities are supplied in individual cardboard boxes. These have an internal ESD coating so that a separate ESD
bag isn’t required. This packaging is recyclable and reduces waste.
Packaging28
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.