While i would be very interested in a Compute Module Board for a Framework 13, there is on big problem in my opinion. Nearly everone has there own connector. The closest to a standard is the CM4s connector but they already announced changes for CM5. Radxa has extended it for more IO. Turing Pi has probably the most Selection if you include the adapter to the CM4 connector, plus its own and Nvidia Jetson. But i don’t know which IO it exposes, and there we have the biggest problem with this, for a framework mainboard you idealy need four USB-C with DisplayPort and one eDP . Other things like GPIO and Network cant be Used. Something like the Rockchip RK3588 has that IO, but which Compute Module exposes it and is not changed with each generation?
Have you ever heard of MNT? Their original Reform and their Pocket Reform are doing this EXACT same thing already. You can upgrade your Reform and Pocket Reform with a RK3588 as well. Already happening.
Honestly, I think the RK3588 is still too niche to be a valid business opportunity for Framework. At least for now.
And currently the are in development of the MNT Reform Next, the IO makes also alot more sense for these SBCs / CMs than the 4x USB C on Framework, even if i prefer the later.
RK1 is documented and indeed, it is Jetson compatible. As for the I/O, I do not expect it to be full replacement of a high-tier mainboard. Obviously it isn’t. But still, the amount of I/O that is routed though the 260-pin SO-DIMM connector is enough to fill nearly all slots.
So something like a SN65DSI86 MIPI® DSI to eDP™ Bridge to get eDP and an HDMI to DP converter and one could have the internal screen and one USB-C with DP on each side.
As for the project, the first thing I thought when reading the article: Byran even used Framework’s hinges in his setup, but still decided to build everything on his own. Whilst this is seriously impressive, I’d rather see him working on a RK3588 mainboard for Framework 13. By this time, it would probably be done already.
So, strategically this project can be a win for makers and a fit for Framework’s niche of geek-oriented upgradeable and repairable hardware.
Since the schematics was already implemented in dozens of adapter boards (including anyon_e) I think it should be quite straightforward to port it to Framework’s form factor.
The only concern is probably the cooling system and board height.
This is fine if Turing Pi will keep using the same interface though and I think they are using the Nvidia connector for that purpose. (Meaning you could buy a better CM and upgrade later on without a new mainboard.)
If I’m not mistaken, it does not expose all interfaces, but since I mostly use those for computing, I would probably buy two Orange Pi’s instead of RK1 for my setup.
The only issue is that Linux support is still in its infancy. Particularly Vulkan compute.
