ADB is one of the most useful tools when debugging Android SBC products. If adb devices does not show the board, the problem is usually USB wiring, Windows driver installation, USB debugging settings, ADB authorization, firmware configuration, or a stale ADB server.
Check the simple items first:
Some SBCs have multiple USB ports. Only one may support ADB device mode.
On Windows, a missing or wrong driver is common. Install the correct Android USB or Rockchip driver, then check Device Manager. If the device appears as unknown, reinstall the driver and reconnect the board.
For setup steps, see Set up ADB on Windows.
On development firmware, USB debugging must be enabled. Some production firmware disables ADB for security. If the display is available, enable developer options and USB debugging. If there is no display, ask the BSP provider whether ADB is enabled by default.
When the driver is correct but the device still does not appear, restart ADB:
adb kill-server
adb start-server
adb devices
If the device is listed as unauthorized, confirm the authorization prompt on the device screen.
If USB ADB is not available but the device is on the network, use the device IP address and connect over Wi-Fi ADB if the firmware supports it.
Related guide: How to Get the IP Address of Your SBC or Smart Device.
If the board appears in adb devices as unauthorized, the USB link and driver are already working. The problem is authorization. On a normal Android product, a prompt appears on the device asking whether to allow USB debugging from the connected computer. Accept the prompt and optionally select always allow.
For embedded products without a visible launcher or with a custom kiosk app, the prompt may be hidden behind the application. Temporarily boot to a development launcher or enable a debug build that pre-authorizes the development computer. Do not ship production firmware with open ADB unless the product security model allows it.
Some Android SBCs have a USB OTG port that can work as host or device. ADB requires device mode. If the board is in host mode, the PC will not see it as an Android device.
Review:
If the same port can power USB peripherals, that does not guarantee it can expose ADB to a PC. Check the board manual for the correct debug port.
On Linux hosts, ADB may fail because the user does not have permission to access the USB device. Add the correct vendor ID to udev rules, reload rules, and reconnect the board. Rockchip and other vendors may use different IDs depending on boot mode and firmware state.
Basic checks:
lsusb
adb kill-server
adb start-server
adb devices
If lsusb sees the board but ADB does not, the issue is usually permissions, vendor ID, or ADB interface exposure.
In production firmware, ADB may be intentionally disabled. This can happen through system properties, build type, init scripts, USB configuration, or security policy. A board may expose ADB in engineering firmware and hide it in user firmware.
Ask these questions:
user, userdebug, or eng?adb or only mtp?Use this order:
lsusb.This prevents wasting time on firmware changes when the real cause is a charge-only cable or missing Windows driver.