Engineering FAQ · Wanlin
How Should an RK3588 Desktop Board Be Verified?
Check the exact RK3588 board configuration, firmware, interfaces, test conditions and current documents before accepting a desktop-board sample.
Direct answer
Check the exact RK3588 board configuration, firmware, interfaces, test conditions and current documents before accepting a desktop-board sample.
What can be confirmed from this page?
This page provides procurement and sample-verification questions for the published RK3588 desktop-board reference. It does not certify a manufacturing process or declare that every board has completed a fixed-duration test. Earlier blanket manufacturing and test statements have been removed pending supporting records.
How should the hardware and firmware be identified?
Request the exact board model and revision, memory and storage configuration, supported firmware build and included accessories. Match the intended display, storage and network peripherals to connector drawings and demonstrated driver support. Confirm application compatibility with the proposed operating system.
What is a useful sample test record?
Record the supply voltage, workload, connected peripherals, ambient conditions, test duration and acceptance criteria. Include startup, display output, storage access, network reconnection, application operation and power-loss recovery as relevant to the project. Ask whether a record applies to a design sample, selected units or a production batch; do not infer coverage from a generic test description.
How should compliance and support be checked?
Match any offered compliance document to its issuing body, reference, model and configuration scope. Agree the responsible supply and support contacts, update delivery, warranty coverage and commercial terms. A webpage table does not establish a certificate or an approved production configuration.
Published configuration items to reconcile
This table preserves earlier published values as a checklist. It is not a controlled specification, approved build, test result or quotation.
| Parameter | AndroidSBC Specification |
|---|---|
| SoC | Rockchip RK3588 octa-core 64-bit, 8nm process |
| CPU | 4x Cortex-A76 up to 2.4GHz + 4x Cortex-A55 up to 1.8GHz |
| GPU | ARM Mali-G610 MP4 |
| NPU | 6 TOPS INT8 with RKNN toolkit |
| Memory | 8GB LPDDR4X |
| Storage | 64GB eMMC 5.1 |
| Operating system | Android 13 |
| Video decode | 8K@60fps H.265 / VP9 hardware decoder |
| Video output | 2x HDMI 2.1, DisplayPort option |
| Storage IO | M.2 Key M NVMe, SATA 3.0 |
| Network | 2x Gigabit Ethernet, WiFi 6, Bluetooth 5.2 |
| USB | 2x USB 3.0, 2x USB 2.0, USB Type-C |
| Expansion | M.2 Key E for WiFi, M.2 Key B for 4G |
| Power input | 12V DC |
| Operating temperature | -20 to 70 Celsius |
| Form factor | Mini-ITX compatible layout |
| Reliability | Watchdog, RTC, fanless thermal design |
Application fit
Confirm the operating environment, workload, display, network and peripheral requirements.
Documents to confirm
Check the exact board revision, interfaces, firmware build and certification scope.
Commercial confirmation
Verify quantity, sample plan, lead time, warranty and delivery terms in writing.

