Since raspberry 5 has been released, CM5 is not far away.
1 Like
I just wanted to point out that this is an impossible to answer question. The CM5 hasn’t even been announced yet – if it ever will. The RPi5 has only been announced – we are still a few weeks from shipping.
So there is absolutely no way to know if this is even possible and no way to answer this question other than 
2 Likes
I personally believe if there’s CM5, the raspberry foundation will maintain the interface compatibility. Normally compute module will come out a year after the pi. Anyway, I’ve already ordered Pi5 and can’t wait to play around.
3 Likes
From a leyman perspective
Imho
I don’t think it will be a drop in replacement.
It has a new I/o controller and double the pci connections… the gpio on the current connector is already strained…
Their info that it’s 2-3 times faster I think includes peripheral # and speeds … so in the console I dunno if it will be an “impressive improvement” passive cooling and all…
1 Like
Probably in the future. Remember, clockwork is a small team, someone on here said less than 10 people working at Clockwork Pi. So the community would have to come together to make it possible. And that’s a big ask. But I think down the line, if Clockwork Pi is still around, they will add more compatible cores for their products.
2 Likes
Considering a Compute Module based on the Raspberry Pi 5 hasn’t been announced, we have no idea if the board will be compatible, if a new adapter board will be viable, or if there even will be a CM5.
I’d wait for it to exist before anyone can make declarations about where it will or won’t be compatible. The Raspberry Pi foundation tends to wait a year after introducing the Model B board to announce a Compute Module.
The Raspberry Pi 5 has different power requirements than its predecessors, so it’s hard to say what it would look like as a Compute Module. The Raspberry Pi Foundation has radically changed the form factor of the Compute Module in the CM4 and that board currently works in the DevTerm and uConsole through an adapter board.
I’d imagine that Clockwork Pi would want to maintain compatibility with Raspberry Pi boards, but a lot can change in a year and they might decide to focus on their own boards instead. There are just a lot of unknowns.
1 Like
I guess it is a little bit late to join this converstaion.
I am not an expert so I could be wrong. But I do think it is not gonna be a drop in replacement either.
I think the main board needs to be redesigned, not just the adapter. Because RBP 5 is more power hungry thant RBP 4B and some says it would draw 15w if you overclock it (which I don’t know if is true).
I am not sure if the mainboard is going to be able to supply that amount of power to make full use of the new chip’s processing power.
And the heat is going to cause some thermal throttling if not properly address, so I don’t know if it is going to perform that much better than the CM4. Better than CM4 is for sure, but just by how much and is it worthy of upgrading.
But I could be wrong. I am not professional.
There will have uConsole with 5G or 6G, Plus high GPU similar to A-06 or better?
CM5 is now out! can’t wait to see a CM5 compatible uConsole and how it harnesses CM5 power.
I am also super excited, looks like extremely minimal changes to the pinout of the cm5. I’ll go ahead and pick one up when I can!
1 Like
Now that the CM5 is out, what I would really love to see and I fully acknowledge it is a big undertaking that would take time, is a full redesign on the main board for this option.
The reasons I think it might be worth doing this is as follows:
- You can add USB3 to the board.
- You can take advantage of the USB C Power Delivery for charging.
- It is an opportunity to do away with the CM3 adapter board.
- You can make a provision for better cooling, perhaps heat pipes to better get from the chips to the back of the case instead of a outrageously thick thermal pad.
- You could take advantage of the newer generation PCIe and additional lane.
- You might consider an NVMe slot.
- Clockwork could sell the new board as an upgrade for those who already own a uConsole, providing another profit generating product to add to their lineup. It doesn’t even need to include the CM5, since supply chain now makes it easier for us to get a CM5 than it was for a long time to get a CM4.
That is just my 2 cents. I know I am just dreaming here, but it would be nice.
7 Likes
Hello,
I read an article saying that the new module is physically compatible with the CM4, so I did a quick comparison of the pinouts and listed the differences I’ve spotted.
Some pins on the CM5 have a similar name & description, but I’m not sure if they provide the same feature via a different interface type, so they’re in the list as well.
I guess that the compatibility depends on what is connected on the current adapter board.
CM5 → CM4
16 Fan_Tacho → Ethernet_SYNC_IN
19 Fan_PWM → Ethernet_nLED1
76 VBAT → Reserved (Do not connect anything to this pin.)
92 PWR_Button → RUN_PG (Reset CPU // Power ON status)
100 CAM_GPIO1 → nEXTRST (Output. Driven low during reset; Driven high (CM4_3.3V) once CM4 CPU has started to boot)
104 PCIE_nWAKE → Reserved
106 PCIE_PWR_EN → Reserved
111 VBUS_EN → VDAC_COMP (Video DAC output (TV OUT))
115 MIPI0_D0_N → CAM1_D0_N (Input Camera1 D0 negative)
117 MIPI0_D0_P → CAM1_D0_P (Input Camera1 D0 positive)
121 MIPI0_D1_N → CAM1_D1_N (Input Camera1 D1 negative)
123 MIPI0_D1_P → CAM1_D1_P (Input Camera1 D1 positive)
127 MIPI0_C_N → CAM1_C_N (Input Camera1 clock negative)
128 USB3-0-RX_N → CAM0_D0_N (Input Camera0 D0 negative)
129 MIPI0_C_P → CAM1_C_P (Input Camera1 clock positive)
130 USB3-0-RX_P → CAM0_D0_P (Input Camera0 D0 positive)
133 MIPI0_D2_N → CAM1_D2_N (Input Camera1 D2 negative)
134 USB3-0-DP → CAM0_D1_N (Input Camera0 D1 negative)
135 MIPI0_D2_P → CAM1_D2_P (Input Camera1 D2 positive)
136 USB3-0-DM → CAM0_D1_P (Input Camera0 D1 positive)
139 MIPI0_D3_N → CAM1_D3_N (Input Camera1 D3 negative)
140 USB3-0-TX_N → CAM0_C_N (Input Camera0 clock negative)
141 MIPI0_D3_P → CAM1_D3_P (Input Camera1 D3 positive)
142 USB3-0-TX_P → CAM0_C_P (Input Camera0 clock positive)
157 USB3-1-RX_N → DSI0_D0_N (Output Display0 D0 negative)
159 USB3-1-RX_P → DSI0_D0_P (Output Display0 D0 positive)
163 USB3-1-DP → DSI0_D1_N (Output Display0 D1 negative)
165 USB3-1-DM → DSI0_D1_P (Output Display0 D1 positive)
169 USB3-1-TX_N → DSI0_C_N (Output Display0 clock negative)
171 USB3-1-TX_P → DSI0_C_P (Output Display0 clock positive)
175 MIPI1_D0_N → DSI1_D0_N (Output Display1 D0 negative)
177 MIPI1_D0_P → DSI1_D0_P (Output Display1 D0 positive)
181 MIPI1_D1_N → DSI1_D1_N (Output Display1 D1 negative)
183 MIPI1_D1_P → DSI1_D1_P (Output Display1 D1 positive)
187 MIPI1_C_N → DSI1_C_N (Output Display1 clock negative)
189 MIPI1_C_P → DSI1_C_P (Output Display1 clock positive)
193 MIPI1_D2_N → DSI1_D2_N (Output Display1 D2 negative)
194 MIPI1_D3_N → DSI1_D3_N (Output Display1 D3 negative)
195 MIPI1_D2_P → DSI1_D2_P (Output Display1 D2 positive)
196 MIPI1_D3_P → DSI1_D3_P (Output Display1 D3 positive)
Datasheets
1 Like