Skip to content
DuolixDuolix
HomeAll RobotsKits & partsEvents

My

Saved itemsOrders

Explore

Developer docsCommunity
AboutSupportPrivacy

© 2026 Duolix

Duolix
Developer documentationStart here
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
Start here

Quick start

Power on, find the device, connect, and run a first check.

This guide gets you from an unpowered Qmini device to a working terminal. It assumes that the QCS6490 device has an AidLux image installed and that you have the power supply specified for its exact hardware revision. For the board-specific checks, see QCS6490 bring-up.

1. Prepare the device

  1. Disconnect motors and other high-current peripherals during first boot.
  2. Connect a display and input devices if you plan to use the local desktop, or connect the device to a trusted local network for remote access.
  3. Apply the specified power supply. Wait for the operating system to finish its first-boot setup before disconnecting power.

First boot can take longer than later boots because AidLux initializes its Linux environment. Do not assume a fixed boot time; check the local display or connection state.

2. Find the device

On the device terminal, inspect the active network interfaces:

ip -brief address

Look for an address on the same local network as your workstation. If you are using USB debugging, verify that ADB can see the device:

adb devices

3. Open a shell

For a network connection, use the account configured on your image:

ssh <username>@<device-ip>

For USB debugging, use:

adb shell

If SSH fails, continue with Connect to the device and Troubleshooting.

4. Verify the environment

Run these read-only checks in the device shell:

uname -a
python3 --version
df -h .

Record the image version and board revision alongside your project. SDK package names and accelerator support can vary between releases.

PreviousDevelopment overviewNextConnect to the device