Many embedded product projects begin with a processor family requirement. Some customers already know they want a Rockchip SBC because the product needs Android UI performance, multimedia, display support, or a familiar development direction. Other projects consider an Allwinner SBC because cost, display, control, audio, or connected device requirements are the starting point.
For Rockchip SBC and Allwinner SBC Selection Guide, the final decision should be made with engineering and procurement in the same review. Engineers can judge BSP, interfaces, thermal behavior, and testing; procurement can check lifecycle, substitutions, MOQ, lead time, and whether the chosen direction still makes sense at production quantity.
When Rockchip is a practical direction
Rockchip platforms are often considered for Android terminals, HMI products, smart displays, multimedia devices, industrial tablets, edge control products, and projects that need a wider range of Android or Linux board directions. Avontek currently lists RK3308, PX30, RK3326, RK3288, RK3566, RK3576, and RK3399 directions on the Rockchip SBC hub.
If the product needs Android UI, a larger display, camera, media playback, richer interfaces, or higher application performance, Rockchip is often part of the early discussion. For Linux products, Rockchip can also be used for gateways, control systems, and industrial interfaces depending on I/O and lifecycle requirements.
When Allwinner is a practical direction
Allwinner platforms are often considered for cost-sensitive display products, compact HMI devices, connected terminals, audio/control products, and Linux control or gateway directions. Avontek currently lists A33, A64, R528, and R128 directions on the Allwinner SBC hub. R128 is positioned as an RTOS direction rather than an Android or Linux SBC.
Allwinner can be useful when the product requirements are clear, the interface set is practical, and the customer needs a balanced product path rather than maximum compute performance.
Platform selection questions
Before choosing a platform, confirm display size and resolution, touch requirements, operating system, application workload, multimedia needs, Ethernet and wireless requirements, serial ports, camera, audio, storage, boot behavior, enclosure size, expected quantity, and production timeline.
If the processor family is not fixed, start from the product category instead: Android SBC, Linux SBC, Industrial SBC, Custom SBC, or Smart Control Panels. This helps avoid choosing a SoC before the product workflow is clear.