Here are a few things we need in a SBC.
- On board NVMe m2 connector and mounting along with PCIe 4 or faster so the full potential of NVMe can be used.
- Dual independent 10 Gb/s ethernet connectors, not shared
- 8 Gb ram
- A SoC manufacture that has open door policy and access to TRM (techincal resource manual) and other stuff.
- BSP that can be used in Yocto
- Rock solid running Ubuntu server
- Barrel connector for power
- Thru holes on the board for easier mounting in custom enclosures
- RTC with battery connector or onboard battery would be better
- Linux debug port with 3 pin connector on board
- Don’t need the big GPIO header, use a ribbon cable to a “breakout” style board.
- More space between the connectors or different locations.
- Wifi antenna connectors
- Cooling system like the VIM4
- Only need USB 3+
Thanks for you suggestions.
Maybe next generation SBC/ARM PC we will consider about these suggestions.
it’s a good idea to write what each maker would appreciate in his ideal board,
i’d like khadas to adress multimedia player usage, but also server usage,
for which the board shall cost less than 70USD,
have onboard emmc (16G+),
I agree with the un necessity of 2x20 pins to look like the rpis
separate power socket is a must, but a small factor one, like what we have on modern laptops;
no need of tiny JST, no mipi, no csi socket, more than 2 usb sockets : at least one usb-A and two usb-c, no huge hdmi port, just a mini one,
the idea behing rpi compute module is good, consider to be compatible with their pinouts to benefit from existing “motherboards/carrier boards” and focus only on CPU boards that can evolve often,
propose a least one risc-V based SOC;
consider replacing the wifi-BT module w/ an ESP32 as a coprocessor and expose its GPIOs;
the embedded 8bit mcu is not so useful for us, remove it.
feel free to comment
for illustration, check this webpage A list of Raspberry Pi Compute Module carrier boards and devices – after hours coding where they listed a few members of that carrier baord ecosystem