Skip to main content

Engineering news & application insight

RK3588 RTC Real-Time Clock, WF-RK3588-C4, AndroidSBC, Los Angeles

Published: Category: News and TrendsSource: Wanlin GroupContent updated:

Direct answer

RK3588 RTC real-time clock - AndroidSBC, a Chinese Rockchip RK3588 NPU computing board manufacturer and exporter under Wanlin Manufacturing Group, supplies the nine-variant WF-RK3588 line covering edge AI inference, industrial machine vision, robotics and AMR, AI NVR with analytics, smart cockpit, 8K digital signage, kiosk and POS, ARM PC and mini-PC, plus a SMARC 2.2 SOM. Direct sourcing for Los Angeles and overseas brand importers.

TL;DR: RK3588 RTC Real-Time Clock

SHENZHEN, China, September 11, 2026 - Wanlin Longgang released a 11,670-unit WF-RK3588-C4 lot for Los Angeles, United States this week, the 361st run booked against the Rockchip RK3588 allocation.

AndroidSBC production statement on Rockchip RK3588 NPU board output serving Los Angeles, United States. AndroidSBC is opening the full WF-RK3588 to United States: nine variants on the Rockchip RK3588 platform with 6 TOPS NPU, 8K H.265 decode, dual Gigabit Ethernet and up to 32GB of LPDDR5. Every variant ships from the Wanlin Longgang facility with OEM branding available, ODM carrier design handled in-house, and per-lot CE, FCC, UKCA, RoHS and IEC 62368-1 documentation.

AndroidSBC WF-RK3588-C4 Rockchip RK3588 Board for Los Angeles, United States

WF-RK3588-C4 Technical Specifications

ParameterAndroidSBC WF-RK3588-C4 (Smart Cockpit and In-Vehicle AI)Industry Average
ProcessorRockchip RK3588 octa-core 4x Cortex-A76 + 4x Cortex-A55 (8nm) + 6 TOPS NPUQuad-core Cortex-A55 1.8GHz without NPU
Process node8nm automotive grade22nm-28nm
GPU / AIArm Mali-G610 MP4 + 6 TOPS NPU for DMS / AVM / BSD inferenceMali-G52 with 1 TOPS
Display outputHDMI 2.1 8K plus DP 1.4 plus LVDS plus MIPI-DSI for seven-screen cockpitHDMI 2.0 dual output
Video decode8K@60fps H.265 plus four independent display streams4K@60fps hard limit
In-vehicle busAutomotive CAN FD plus automotive Ethernet plus RS485CAN 2.0 only
Camera input6x MIPI CSI plus 2x AVM camera plus 1x DMS IR camera2x MIPI CSI only
Wireless5G / 4G module plus WiFi 6 plus Bluetooth 5.3 plus GNSSWiFi 5 only
Memory8GB / 16GB LPDDR4X or 16GB LPDDR5LPDDR4 4GB
Storage64GB / 128GB eMMC plus M.2 NVMe for route and event logseMMC 32GB only
Thermal rangeAutomotive grade -40C to 85C, fanless passive cooling0C to 60C commercial
OS supportAndroid Automotive 12 / 13 plus Linux Yocto plus ROS2Android 9 or vendor BSP only

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.

Challenges in Sourcing Smart Cockpit and In-Vehicle AI for United States Buyers

What breaks United States sourcing plans on the smart cockpit and in-vehicle ai line is not price negotiation, it is the second shipment. The Rockchip RK3588 has to be allocated at wafer level, and the brokers quoting fastest are usually the ones with the least control over that allocation. The software side is the second exposure. A board that boots on the bench is not the same as a board that carries the certified stack a United States channel will accept, and the difference usually shows up during inbound inspection rather than at the factory gate.

Then there is the certification file. A stamp is cheap; a Technical File with notified-body reports dated inside twelve months is not, and the difference only matters when a United States customs officer asks for it. AndroidSBC closes the loop at the source factory: certified image burned, burn-in barcode attached per unit, Technical File issued with the lot. The nine WF-RK3588 variants cover smart cockpit, in-vehicle infotainment, AVM surround view, DMS driver monitoring, BSD blind spot detection, rear seat entertainment, digital instrument cluster, fleet management terminal, commercial vehicle telematics, and one-chip seven-screen cockpit and each ships in three memory configurations, so most Los Angeles requirements can be met from standard stock rather than a custom production run.

United States importers usually raise compliance first. In the United States FCC Part 15 authorisation is required and an FCC ID applies to radio modules, while UL or ETL listing is usually demanded by the retail channel. AndroidSBC answers it by preparing the FCC Part 15 authorisation with an FCC ID for radio modules and a UL or ETL listing documentation for FCC / UL before the lot is packed, issuing it with the standard multi-market pack (CE, FCC, UKCA, RoHS, REACH), and routing the lot through Port of Los Angeles on the Los Angeles to Yantian lane.

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 Los Angeles 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 Los Angeles Buyers

AndroidSBC runs three engagement tiers for United States importers and brand owners sourcing a smart cockpit and in-vehicle ai on the WF-RK3588 line:

  • 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: Android 12 and Android 13 are prebuilt and signed at the factory for every WF-RK3588 variant; Android 14 is on the validation roadmap. On the Linux side the partner can choose Ubuntu 22.04 LTS, Debian 12, Yocto Kirkstone or Buildroot, all with the Rockchip RKNN-Toolkit2 NPU runtime and the rknn-cross-compiler pre-validated. The implication for a United States integrator is one silicon across both a certified Android stack on the WF-RK3588-K6 and a Linux NPU inference stack on the WF-RK3588-V1, drawn from the same supplier file.

What is the 6 TOPS triple-core NPU on the WF-RK3588 actually used for in production?

Answer: Three workload families, same silicon. Retail analytics on the WF-RK3588-E0, machine-vision defect classification on the WF-RK3588-V1, and 16-channel AI surveillance analytics on the WF-RK3588-N3. The same 6 TOPS triple-core NPU handles all three from a per-lot certified image burned at Longgang. Los Angeles integrators typically pick one workload per variant and let AndroidSBC tune the firmware profile before shipment.

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: Yes. AndroidSBC ships DDP to Amazon FBA warehouses in the US, EU and Japan, and to nominated 3PL consolidation points in Hong Kong, Singapore, Rotterdam, Los Angeles and Shenzhen. Carton labelling and pallet configuration are set up for FBA inbound requirements, the export declaration names the Wanlin Longgang source factory as the place of origin, and each pallet carries a per-unit barcode that traces back to the burn-in record for downstream RMAs.

How does AndroidSBC handle RMA or DOA replacements on the WF-RK3588?

Answer: Target DOA is 0.3 percent across twelve months. RMA works by returning the WF-RK3588-C4 unit to Longgang with its burn-in barcode; replacements ship inside ten business days. Since each unit is traceable to its burn-in record, partners typically receive a root-cause note with the replacement rather than a silent credit.

Contact AndroidSBC: Start Your WF-RK3588-C4 Sourcing Conversation

AndroidSBC is the export channel for the Wanlin WF-RK3588. Los Angeles and United States importers, brand owners and distributors who want the smart cockpit and in-vehicle ai direct from the Longgang plant can reach the export desk at:

  • 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

For an OEM or ODM conversation, it helps to state the target annual volume, the certification scope required (CE, FCC, UKCA, RoHS, REACH, IEC 62368-1, UL 60950-1 or EN 55032 plus EN 55035), and the preferred Incoterm (FOB Yantian, FOB Shekou, CIF, DDP, or DDP-Amazon). The export team returns a per-lot quote plus the variant-by-variant MOQ matrix for the WF-RK3588 line within two business days.

Evidence, accuracy and reuse

This page is maintained as an engineering information resource. Product capabilities and project details should be verified for the exact hardware revision, firmware, target market and deployment environment before procurement or integration.

Editorial source: Wanlin Group. Use current model documents and agreed project requirements to verify technical claims. General guidance is not a product test report.