Published configuration: confirm against controlled documents
The AS-RK3588-GOV-CUS carrier board is a 6-layer PCB in a 3.5-inch SBC form factor, industrial-grade components throughout, with conformal coating optional. The specifications below are the OEM/ODM default; every line is re-specable on request.
| Block | Specification |
|---|---|
| SoC | Rockchip RK3588 octa-core Cortex-A76/A55 up to 2.4GHz; RK3568 / RK3566 quad Cortex-A55; RK3399; RK3288; Allwinner A133 on the value tiers |
| NPU | RK3588 6 TOPS INT8; RK3568 1 TOPS; value tiers without NPU |
| GPU | RK3588 Mali-G610 MP4; RK3568 Mali-G52 2EE; A133 PowerVR GE8300 |
| Memory | LPDDR4 / LPDDR4X / LPDDR5, 2GB to 16GB depending on tier |
| Storage | eMMC 5.1 8GB / 16GB / 32GB / 64GB / 128GB; UFS 2.1 option; TF card; M.2 NVMe on the RK3588 carrier |
| Display | Single, dual or triple independent outputs: LVDS / eDP / MIPI DSI / HDMI; 1920x1080, 3840x2160 or 7680x4320 decode; independent or mirrored; portrait or landscape per output |
| Touch | Capacitive 10-point / 20-point; dual touch controllers on request; IR touch on request |
| Identity and biometrics | ID card reader, passport reader, face recognition with liveness, fingerprint, iris, palm print, RFID and NFC; signature pad; electronic signature capture |
| Print and scan | Thermal receipt printer, A4 laser or inkjet printer, document feeder, document scanner, card dispenser, barcode imager, QR reader |
| Camera | MIPI CSI 2-lane / 4-lane, ISP, 30 fps capture for liveness checks, document capture and people counting |
| I/O | 4x USB 2.0, 2x USB 3.0, RS232 / RS485, up to 6 isolated serial ports, GPIO island up to 32 channels, relay, PWM, I2C, SPI, CAN bus |
| Security | Secure boot chain, trusted execution environment, trusted platform module option, national cryptography module option, hardware key storage, signed audit trail |
| Network | Dual Gigabit Ethernet, PoE+ option, WiFi 5 / WiFi 6, Bluetooth 5.0, 4G LTE / 5G module, SIM slot, GPS option |
| OS | Android 11 / 12 / 13 / 14 / 15; Linux; Ubuntu; Debian; Kylin OS; UOS; OpenHarmony; AOSP; GMS or GMS-free; kiosk mode |
| Power | 12V DC standard; wide-voltage 9-36V on request; PoE+ on request; hold-up capacitor for brownout ride-through; scheduled power profile with RTC wake |
| Thermal and reliability | Fanless 6-layer carrier; 0C to 50C standard, -20C to 70C wide temp; 46C glazed-hall rating; 24/7 duty; hardware watchdog; RTC backup; ESD and EMC design |
| Form factor | 3.5-inch SBC, Pico-ITX, Mini-ITX, or core board plus custom carrier; counter-top, floor-standing and wall-mounted enclosures |
Application matrix: 8 customization scenarios for the AS-RK3588-GOV-CUS
The AS-RK3588-GOV-CUS is one carrier platform across eight different government kiosk deployments. The matrix below shows the most common OEM/ODM customization angles a procurement director in Europe walks through in the first scoping call.
| Scenario | Catalog board limit | AS-RK3588-GOV-CUS customization |
|---|---|---|
| Service hall self-service kiosk | 3.4 s category load, cloud-only forms | Under 400 ms local index, 30-day offline forms |
| ID and biometric verification | 4.6 s check, no secure element | Under 900 ms on-device check, discrete secure element |
| Tax and social security counter | One serial port, 40 s session timeout | Multi-port serial, 20-minute offline hold |
| Immigration and real estate desk | Two-device lane budget, 200 dpi scan | Three-device submission, 300 dpi single pass |
| Certificate and document issuing | Printer brownout, no paper-low sensor | Budgeted printer rail, GPIO sensor island |
| Dual-screen service plus notice | Mirrored output, 430 ms drift | Two framebuffers, per-screen proof-of-play |
| Queue, check-in and evaluation | One serial port, lost survey writes | Three-function serial map, 10-year write budget |
| Multi-platform government family | Four carriers, two contracts | One enclosure, one BSP train, one MOQ |
OEM/ODM workflow: 8 steps from kickoff to first article
Below is the actual OEM/ODM workflow a procurement director in Madrid walks through when commissioning a custom government service kiosk Android motherboard from AndroidSBC. No step is a placeholder.
- Day 0-2 — Requirements intake. A 90-minute call captures the counter format, the I/O map, the locale list, the OS choice, the security and certification scope and the volume profile. Output: a one-page requirements sheet.
- Day 3-6 — Feasibility study. AndroidSBC engineers validate the SoC choice (RK3588, RK3568, RK3566, RK3288, RK3399 or A133), the carrier I/O map, the BSP availability, the certification gap and the thermal envelope. Output: a feasibility report with go / no-go on each customization.
- Day 7-10 — Schematic and PCB layout. The AS-RK3588-GOV-CUS carrier board is laid out on a 6-layer stack-up with the customer's I/O map. Output: schematic and PCB review package.
- Day 11-14 — BSP porting. Android, Linux, Ubuntu, Debian, Kylin OS, UOS or OpenHarmony BSP is ported to the customer's OS choice, with PREEMPT_RT patches, kiosk-mode locking, secure boot and runtime locale packs where needed. Output: a BSP build for the customer's evaluation team.
- Day 15-18 — Sample fabrication. Five to ten engineering samples are fabricated at the Shenzhen source factory, with conformal coating and stencil rework as required. Output: samples shipped to the customer by air.
- Day 19-21 — Customer evaluation. The customer's evaluation team runs thermal, EMC, display, identity and field-replication tests. Output: an evaluation report with sign-off or change requests.
- Day 22-23 — Design freeze and mass-production tooling. Any change requests are absorbed, the design is frozen, and mass-production tooling is opened at the source factory. Output: a frozen Gerber and a frozen BOM.
Twenty-five days from kickoff to first article. Ninety days from kickoff to mass production. This is the OEM/ODM rhythm that the procurement director in Europe learns to expect from a Shenzhen source factory that does this work for a living.
Frequently asked questions
What is the MOQ for a custom government service kiosk Android motherboard?
Answer: 150 units for OEM (a re-spin of an existing carrier board), 500 units for ODM (a from-scratch PCB layout). Sample orders of five units are accepted with an engineering report.
How long does OEM/ODM customization take from kickoff to first article?
Answer: 25 days on the workflow described above, including schematic, PCB layout, BSP porting, sample fabrication and customer evaluation. Mass production starts around day 90.
Should I choose RK3588 or RK3568 for a government kiosk?
Answer: RK3588 for identity verification terminals with on-device liveness, 6 TOPS NPU workloads, triple independent display and 8K decode; RK3568 for service hall kiosks, tax and social security counters, certificate issuing kiosks and dual-screen notice terminals where 1 TOPS and 4K dual display are sufficient; A133 or RK3566 for cost-driven queue and notice tiers. AndroidSBC builds all of them on the same enclosure cut-out.
Can the kiosk run twelve languages including right-to-left scripts?
Answer: Yes. Runtime locale packs with full right-to-left layout for Arabic and Hebrew are standard, with sub-300 ms switching and no per-locale re-spin of the firmware image.
Can identity checks run on-device instead of in the cloud?
Answer: Yes. The 6 TOPS NPU toolchain runs the customer's own liveness and match model on-device, key material stays in a discrete secure element, and no face frame leaves the terminal.
Do you support a verified boot chain and signed audit records?
Answer: Yes. Secure boot with a hardware root of trust, a trusted execution environment, an optional trusted platform module and an optional national cryptography module, with power-fail-safe signed audit logs on an on-board FRAM path.
Can the board drive two screens with independent content?
Answer: Yes. Up to three independent outputs on the RK3588 carrier with per-screen resolution, refresh and rotation, independent LVDS and eDP clock domains, sub-16 ms frame sync, dual touch controllers and per-screen proof-of-play logs.
How do you handle an interrupted firmware update on a live estate?
Answer: The OTA path is atomic with A/B redundancy and a bootloader-level rollback, so a kiosk that loses power mid-update boots the previous known-good image instead of a dead screen at the counter.
What certifications can you pre-scope for our market?
Answer: CE / FCC / RoHS standard. UL / UKCA / KC / PSE / SAA, GMS / Google EDLA, EMVCo L2 and PCI PTS are all pre-scoped on request. EMC pre-scanning is done in-house before third-party testing.
Do you accept sample and small-batch orders?
Answer: Yes. Samples ship in 1-3 days from stock where available; custom samples ship inside the 15-18 day window. Small-batch and large-volume pricing is available on request.
