TL;DR: RK3588 4x Cortex-A76 2.4GHz
AndroidSBC opens regional OEM partner slots on the WF-RK3588 NPU computing family serving Houston, United States. The WF-RK3588 is a nine-variant line rather than a single part number, and the shape is deliberate. Edge AI inference, machine vision, robotics, AI NVR, cockpit, 8K signage, kiosk, ARM PC and SMARC all want the same silicon: 4x Cortex-A76 + 4x Cortex-A55 + triple-core NPU at 6 TOPS + 8K decode, with one variant-specific connector and thermal profile each. A Houston buyer can hold one supplier file, one documentation format and one MOQ structure across every variant.
WF-RK3588-C4 Technical Specifications
| Parameter | AndroidSBC WF-RK3588-C4 (Smart Cockpit and In-Vehicle AI) |
|---|---|
| Processor | Rockchip RK3588 octa-core 4x Cortex-A76 + 4x Cortex-A55 (8nm) + 6 TOPS NPU |
| Process node | 8nm automotive grade |
| GPU / AI | Arm Mali-G610 MP4 + 6 TOPS NPU for DMS / AVM / BSD inference |
| Display output | HDMI 2.1 8K plus DP 1.4 plus LVDS plus MIPI-DSI for seven-screen cockpit |
| Video decode | 8K@60fps H.265 plus four independent display streams |
| In-vehicle bus | Automotive CAN FD plus automotive Ethernet plus RS485 |
| Camera input | 6x MIPI CSI plus 2x AVM camera plus 1x DMS IR camera |
| Wireless | 5G / 4G module plus WiFi 6 plus Bluetooth 5.3 plus GNSS |
| Memory | 8GB / 16GB LPDDR4X or 16GB LPDDR5 |
| Storage | 64GB / 128GB eMMC plus M.2 NVMe for route and event logs |
| Thermal range | Automotive grade -40C to 85C, fanless passive cooling |
| OS support | Android Automotive 12 / 13 plus Linux Yocto plus ROS2 |
All parameters in the table above are measured at 25C ambient. The AndroidSBC WF-RK3588-C4 (Smart Cockpit and In-Vehicle AI) holds its display output and its decoder load at the same time through the burn-in loop, a combination that the legacy boards in the comparison column cannot sustain. For United States importers sourcing the WF-Series, the 8GB + 64GB automotive (WF-RK3588-C4-A) variant is the typical configuration for the smart cockpit, IVI, and in-vehicle AI use case, with a sustained weekly capacity of 5,000 pcs/wk on the Longgang line.
Global Smart Cockpit and In-Vehicle AI Market Trends
- Smart cockpit: WF-RK3588-C4 drives the cluster plus the centre stack plus the passenger display from one board.
- Display and signage refresh cycles: a longer content loop and a higher panel resolution now define the refresh trigger. The WF-RK3588-C4 board carries that headroom without a board change.
- DMS driver monitoring: WF-RK3588-C4 runs the gaze plus distraction model on the NPU against the IR camera feed.
The read across the Smart Cockpit and In-Vehicle AI channel is that buyers are consolidating suppliers: fewer vendors, wider platform coverage per vendor, and a longer contract behind each order.
In all three cases, Houston buyers are converting spot quotes into blanket orders with a monthly lot release, because a programme that has to hold a twelve-month shipping window cannot tolerate a mid-year allocation break.
WF-RK3588-C4 Application Scenarios
The WF-RK3588 line fits nine NPU application lanes, with the WF-RK3588-C4 (Smart Cockpit and In-Vehicle AI) as the lead SKU for Houston and United States programmes:
- Smart cockpit: WF-RK3588-C4 drives the cluster plus the centre stack plus the passenger display from one board.
- AVM surround view: WF-RK3588-C4 stitches the four AVM cameras on the NPU while the centre display shows the result.
- DMS driver monitoring: WF-RK3588-C4 runs the gaze plus distraction model on the NPU against the IR camera feed.
- BSD blind spot detection: WF-RK3588-C4 ingests the side camera feeds plus the radar targets on the NPU.
- Rear seat entertainment: WF-RK3588-C4 drives the rear displays while the front stack holds the cluster plus the centre display.
- Digital instrument cluster: WF-RK3588-C4 holds the cluster refresh at frame rate against the turn-by-turn map overlay.
- Fleet management terminal: WF-RK3588-C4 logs route plus event plus driver state onto the M.2 NVMe over 5G.
- One-chip seven-screen cockpit: WF-RK3588-C4 distributes seven independent display streams across HDMI, DP, LVDS, and MIPI-DSI.
Partnership Models for Houston Buyers
For Houston importers and brand owners, the WF-RK3588-C4 and the rest of the WF-RK3588 NPU variants are available under three contract shapes:
- OEM (your brand on our hardware): custom logo silk-print, custom packaging, custom boot animation, custom SKU label, and a private-label certification file.
- ODM (your spec on our reference design): schematic and stack-up review, carrier or motherboard redesign, custom firmware features, and a BSP port handled by the Longgang engineering desk.
- Distribution (your channel, our stock): regional distributor rights, channel rebate, stock holding at the factory, and a framework agreement with a monthly lot release.
Does the WF-RK3588 line run Android or Linux, and what NPU framework stack is supported?
Answer: Both. AndroidSBC prebuilt Android 12 and Android 13 firmware images that boot on every WF-RK3588 variant, with Android 14 builds available on request. Linux distributions (Ubuntu 22.04 LTS, Debian 12, Yocto Kirkstone, Buildroot) load the Rockchip RKNN-Toolkit2 runtime so the 6 TOPS NPU is usable from day one. The same silicon carries the Android build on the WF-RK3588-D5 signage player and the Yocto build on the WF-RK3588-V1 industrial vision processor, which is a deployment breadth that United States importers rarely get from one supplier.
What is the 6 TOPS triple-core NPU on the WF-RK3588 actually used for in production?
Answer: Three workloads that have already shipped at scale. On the WF-RK3588-E0 the NPU drives retail analytics (people counting, dwell time, demographic classification) at 25fps per stream. On the WF-RK3588-V1 the same silicon runs machine-vision defect classification at line speed on a factory floor. On the WF-RK3588-N3 it carries 16-channel AI surveillance analytics (person, vehicle, behaviour) on a fanless board. Each variant is tuned for its workload, but the silicon is the same, and that is what makes one supplier file cover nine deployment categories for United States buyers.
Can AndroidSBC handle CE, FCC, UKCA, RoHS, REACH and IEC 62368-1 paperwork for United States?
Answer: Yes. AndroidSBC ships a Declaration of Conformity plus a Technical File with every lot. The file contains the CE test reports (EN 55032 plus EN 55035 EMC, EN IEC 62368-1 safety), the FCC Part 15 report, the UKCA dossier where relevant, the RoHS 2.0 report, and the REACH declaration, all dated within the prior twelve months. Where a United States market needs an additional national mark, the export desk will confirm coverage before the order is confirmed rather than after.
What are the MOQ and lead time for a first order on the WF-RK3588?
Answer: 5,000 units per shipment on standard configurations, four weeks to sample and six weeks to mass produce. Where a United States partner signs a twelve-month blanket order, the MOQ per release becomes negotiable and the line will accept variant-mixed purchase orders.
Does AndroidSBC support custom Android ROM, custom Linux, or custom NPU model porting?
Answer: Custom ROM, custom Linux, and custom NPU model porting are all part of the ODM tier. That covers proprietary Android services, a locked-down launcher, Ubuntu, Debian, Yocto or Buildroot images, BSP ports for custom carriers, and RKNN-Toolkit2 model quantization from PyTorch, ONNX, TensorFlow or Caffe. Source access is released under NDA, and the Longgang engineering desk carries the port so the partner is not left with an unmodified vendor BSP.
What about software updates and long-term support on the WF-RK3588?
Answer: Wanlin commits to a minimum seven-year supply window across the WF-RK3588 line. Security patches are back-ported across the Android, Ubuntu LTS, Debian LTS and Yocto tracks for as long as the board is in production, and AndroidSBC provides OTA update infrastructure for partners who need to push firmware to field-deployed units. NPU model builds are versioned on the Wanlin side so a partner that re-trains a model can push the new RKNN file through the same OTA channel without a board swap.
Can AndroidSBC ship to Amazon FBA warehouses or 3PL consolidation points?
Answer: That is routine. AndroidSBC delivers DDP into Amazon FBA in the US, EU and Japan and into 3PL consolidation points at Hong Kong, Singapore, Rotterdam, Los Angeles and Shenzhen. Carton and pallet configuration follows FBA inbound rules, and the place of origin on the declaration is the Wanlin Longgang source factory.
How does AndroidSBC handle RMA or DOA replacements on the WF-RK3588?
Answer: The DOA target is 0.3 percent over twelve months. For RMA, partners send the WF-RK3588-C4 unit back to Longgang with the burn-in barcode attached, and replacements go out within ten business days. The per-unit burn-in record means the failure report usually carries a root cause alongside the replacement, which is what a United States integrator running a production line actually needs.
Contact AndroidSBC: Start Your WF-RK3588-C4 Sourcing Conversation
The AndroidSBC export desk handles all WF-RK3588 enquiries from Houston and United States. Direct factory contact for the smart cockpit and in-vehicle ai is available through:
- Email: Androidsbc@163.com
- Export service hotline: +8613261677119
- Website: https://www.androidsbc.com
- Destination market file: FCC Part 15 authorisation with an FCC ID for radio modules and a UL or ETL listing for United States, administered by FCC / UL, entering at Port of Los Angeles on the Los Angeles to Yantian lane
- Source factory address: Wanlin Group, Building B, Building 1, Beisida Medical Device Building, 28 Nantong Avenue, Baolong Community, Baolong Sub-district, Longgang District, Shenzhen, Guangdong, China
To start an OEM or ODM review, send the target volume, the certification scope you need, and your preferred Incoterm. The export desk replies with a per-lot quotation and the MOQ matrix across the nine WF-RK3588 variants within two business days.
