Skip to content
DuolixDuolix
HomeAll RobotsKits & partsEvents

My

Saved itemsOrders

Explore

Developer docsCommunity
AboutSupportPrivacy

© 2026 Duolix

Duolix
Developer documentationQCS6490 hardware
All documentation
Start hereDevelopment overviewQuick startConnect to the device
QCS6490 hardwareQCS6490 hardware overviewQCS6490 interfacesQCS6490 bring-up
AidLux systemAidLux workspaceNetwork and remote accessDevelopment environmentStart an application at boot
AI developmentInference workflowAidLite SDKROS 2 integration
SDK referenceAidLite Python APIAidLite C++ APIAidCV Python APIAidConnect C++ APIAidConnect Android APIAidStream C++ APIAidVoice C++ API
TroubleshootingTroubleshooting
QCS6490 hardware

QCS6490 hardware overview

Understand the compute platform and documented configuration.

Qmini's compute environment is built around QCS6490 and runs AidLux, which combines an Android-facing system with a Linux development workspace. Use this page to identify the documented compute configuration; use the specification for your shipped Qmini revision before designing a wiring harness or power system.

QCS6490 compute and development interfaces

Documented compute configuration

ComponentConfiguration described in the supplied hardware material
Compute platformQCS6490
CPUOne Cortex-A78 core at up to 2.7 GHz, three Cortex-A78 cores at up to 2.4 GHz, and four Cortex-A55 cores at up to 1.9 GHz
GPUAdreno 642
AI processingApproximately 12 TOPS at INT8 precision; actual throughput depends on the model and runtime
Memory8 GB LPDDR4
Storage128 GB UFS 3.1
System imageAidLux with Android 14 and Ubuntu 22.04 environments

The table describes the documented configuration, not a promise that every Qmini production revision or system image has identical memory, storage, clock limits, or exposed connectors. Check the device label, installed image, and order specification when reproducibility matters.

Software and hardware boundaries

AidLux provides the application environment. AI workloads may use AidLite and other installed SDK components; available accelerators and package versions depend on the image. Robot motion, emergency stop, and high-current devices belong to a separately validated control path. Do not connect a motor directly to a compute-board signal pin.

Continue with QCS6490 interfaces to choose a connection, or QCS6490 bring-up to check a newly powered device.

PreviousConnect to the deviceNextQCS6490 interfaces