This section collects practical notes for embedded single-board computer development. The content focuses on Rockchip-based Android and Linux SBCs, display integration, board bring-up, ADB usage, network setup, OTA update testing, and related engineering workflows.
The goal is to provide reusable references for engineers who work with custom SBC hardware, Android/Linux BSPs, TFT LCD modules, touch panels, and embedded HMI products.
A practical overview of RK3566 Android SBCs for embedded HMI panels, smart terminals, display products, IoT devices, and custom Android/Linux board development.
Main information:
SoC: Rockchip RK3566
Platform: ARM Cortex-A55 embedded SBC
Operating system: Android / Linux
Main interfaces: MIPI DSI, LVDS, HDMI, Ethernet, USB, UART, I2C, SPI, GPIO
A practical guide to Rockchip Android SBC development, covering BSP customization, display and touch integration, ADB debugging, OTA updates, peripheral drivers, production testing, and embedded product deployment.
Main information:
SoC: Rockchip RK3566 / RK3568 / RK3576 / RK3588 / PX30
Platform: Rockchip ARM Android SBC
Operating system: Android
Main interfaces: MIPI DSI, LVDS, HDMI, eDP, USB, Ethernet, UART, I2C, SPI, GPIO, PWM
Embedded SBC development usually requires both hardware and software work. A board may boot successfully, but display, touch, Wi-Fi, Ethernet, UART, GPIO, backlight, audio, camera, or OTA update functions still need to be configured and tested.
This section is designed to collect practical guides related to:
These guides are not intended to replace the official BSP documentation. Instead, they provide practical engineering notes that are easier to reference during real board development.
Board bring-up is the first stage of custom SBC development. Engineers need to confirm that the CPU, DDR, storage, PMIC, bootloader, kernel, display, and basic peripherals are working correctly.
Typical bring-up checks include:
A stable bring-up process helps identify whether an issue is caused by hardware design, bootloader configuration, kernel drivers, or user-space software.
Android SBCs are commonly used in smart control panels, HMI devices, access control terminals, kiosks, digital signage players, medical devices, and smart appliance interfaces.
Android development on an SBC may involve:
For Android-based products, display and touch stability are especially important because the screen is usually the main user interface.
Linux SBCs are often used in gateways, control terminals, data collection devices, industrial automation systems, laboratory instruments, and custom embedded computers.
Linux SBC development may involve:
Compared with Android, Linux usually gives developers more direct access to system services and hardware interfaces. This makes it suitable for industrial and hardware-oriented products.
Rockchip SoCs are widely used in Android and Linux SBC products because they provide a practical balance of performance, display support, multimedia capability, software ecosystem, and cost.
Common Rockchip platforms used in embedded SBCs include:
These platforms can support different product levels, from small HMI panels to high-performance edge devices.
For Rockchip SBC development, engineers often need to work with:
Display integration is one of the most common tasks in embedded SBC projects. A product may use a 5-inch, 7-inch, 10.1-inch, 12.1-inch, or 15.6-inch TFT LCD depending on the application.
Common display interfaces include:
A display configuration usually requires:
Display issues may appear as a black screen, white screen, flickering image, wrong colors, incorrect resolution, unstable backlight, reversed touch coordinates, or failed initialization. These problems often require checking both the hardware schematic and the software configuration.
ADB is an important tool for Android SBC development. It allows engineers to connect to the device, check logs, install applications, push files, pull files, reboot the system, and test OTA updates.
Common ADB operations include:
adb devices
adb shell
adb logcat
adb push localfile /sdcard/
adb pull /sdcard/file .
adb install app.apk
adb reboot
adb reboot recovery
For production projects, ADB may be disabled or restricted for security reasons. During development, however, it is one of the most useful debugging tools.
Network access is important for both Android and Linux SBCs. Engineers often need to find the board IP address, test Ethernet, connect Wi-Fi, configure static IP, or access the board remotely.
Useful checks include:
ip addr
ifconfig
ping 8.8.8.8
ping google.com
route -n
cat /etc/resolv.conf
On Android systems, network status can also be checked through ADB shell or system settings.
Network problems may be caused by missing drivers, wrong MAC address, DHCP failure, DNS failure, incorrect gateway, cable problems, or switch configuration.
Firmware update support is important for embedded products after deployment. Android products may use OTA packages, recovery mode, or vendor upgrade tools. Linux products may use A/B partitions, SWUpdate, RAUC, Mender, or custom update scripts.
An update strategy should consider:
For commercial products, update reliability is as important as the original firmware image.
The related TFT display configuration files are maintained in the GitHub repository:
This repository includes example Device Tree configuration files, panel notes, and display integration references for Rockchip-based embedded SBC projects.
The information in this section is based on practical embedded SBC development workflows. Actual implementation may vary depending on the SoC, board design, BSP version, kernel version, Android version, Linux distribution, display panel, touch controller, and hardware revision.
Before applying any configuration to a production device, always compare it with:
A stable embedded SBC product depends on the complete system design, including hardware, software, enclosure, power, thermal behavior, display integration, and long-term maintenance.