Skip to main content

Engineering news & application insight

WF-RK3588-N3 — RK3588 6 TOPS NPU: Integration Notes

Published: Category: News and TrendsSource: WanlinContent updated:

Direct answer

Review WF-RK3588-N3 — RK3588 6 TOPS NPU requirements, interfaces, software and acceptance scope. Confirm the exact model configuration against current controlled project documents.

TL;DR: RK3588 6 TOPS NPU

AndroidSBC WF-RK3588-N3 Rockchip RK3588 Board for Houston, United States

WF-RK3588-N3 Technical Specifications

ParameterAndroidSBC WF-RK3588-N3 (AI NVR and Surveillance Analytics)
ProcessorRockchip RK3588 octa-core 4x Cortex-A76 + 4x Cortex-A55 (8nm) + 6 TOPS NPU
Process node8nm
GPU / AIArm Mali-G610 MP4 + 6 TOPS NPU + INT8 multi-model pipeline
Video decode8K@60fps H.265 / H.264 plus 16-channel 1080p decode
Video encode8K@30fps plus simultaneous 16-channel sub-stream encode
Storage64GB / 128GB eMMC plus dual SATA 3.0 plus M.2 NVMe for RAID
Camera input16 PoE+ channels via carrier plus 2x 4-lane MIPI CSI direct attach
NetworkDual Gigabit Ethernet with hardware QoS plus WiFi 6
AI modelsFace recognition, license plate recognition, behaviour analysis, perimeter detection, crowd density
Memory8GB / 16GB LPDDR4X or 16GB LPDDR5
OS supportLinux Debian 12 plus Android 12 / 13 plus OpenHarmony
Functional safetyHardware watchdog plus RTC plus auto reboot on kernel panic

All parameters in the table above are measured at 25C ambient. The AndroidSBC WF-RK3588-N3 (AI NVR and Surveillance Analytics) 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 + 128GB (WF-RK3588-N3-A) variant is the typical configuration for the AI NVR and multi-camera surveillance analytics use case, with a sustained weekly capacity of 5,000 pcs/wk on the Longgang line.

Global AI NVR and Surveillance Analytics Market Trends

  • Smart NVR: WF-RK3588-N3 records 16 PoE+ channels while the NPU tags every frame for downstream search.
  • Display and signage refresh cycles: a longer content loop and a higher panel resolution now define the refresh trigger. The WF-RK3588-N3 board carries that headroom without a board change.
  • Face recognition terminal: WF-RK3588-N3 runs face recognition plus anti-spoofing on the NPU against the in-store camera feed.

Channel research on the AI NVR and Surveillance Analytics segment keeps landing on the same point: the constraint is allocation, and allocation is held by factories rather than traders.

The common thread in United States is that single orders are being replaced by blanket agreements with a monthly release, because a programme that has to survive a twelve-month window cannot absorb an allocation gap in the middle of it.

WF-RK3588-N3 Application Scenarios

The WF-RK3588 line fits nine NPU application lanes, with the WF-RK3588-N3 (AI NVR and Surveillance Analytics) as the lead SKU for Houston and United States programmes:

  • Smart NVR: WF-RK3588-N3 records 16 PoE+ channels while the NPU tags every frame for downstream search.
  • AI video analytics: WF-RK3588-N3 holds multi-model inference on the NPU while the encoder pipeline records at full rate.
  • Face recognition terminal: WF-RK3588-N3 runs face recognition plus anti-spoofing on the NPU against the in-store camera feed.
  • License plate recognition: WF-RK3588-N3 reads the plate at the gate plus the gate controller on the same board.
  • Behaviour analysis: WF-RK3588-N3 flags fall detection and crowd density on the NPU at frame rate.
  • Perimeter security: WF-RK3588-N3 watches the fence line plus the night-time low-light feed on the NPU.
  • Smart city surveillance: WF-RK3588-N3 aggregates street camera feeds plus the analytics dashboard on one board.
  • Traffic monitoring: WF-RK3588-N3 runs plate recognition plus vehicle classification at the intersection cabinet.

Partnership Models for Houston Buyers

The WF-RK3588 line is available to United States partners through three routes, and they can be mixed inside one agreement:

  • 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, and the file travels with the goods rather than behind them. The pack covers CE, FCC Part 15, UKCA, RoHS 2.0, REACH and IEC 62368-1 with test reports dated within the prior year. AndroidSBC will also advise on any United States-specific addition during quotation, which is the point at which the answer is still useful.

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-N3 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-N3 Sourcing Conversation

Wanlin Manufacturing Group sells the WF-RK3588 NPU computing line overseas through AndroidSBC. Houston and United States importers, brand owners and channel distributors who want to source the ai nvr and surveillance analytics direct from the Longgang plant can reach the export desk 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 speed up an OEM or ODM review, include the target volume, the certification scope you need, and your preferred Incoterm. With those three in hand, AndroidSBC returns a per-lot quotation and the MOQ matrix across the nine WF-RK3588 variants 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. Technical claims are reviewed against available product documentation and project requirements.