Luckfox Forums

Board/Model: Luckfox Pico Pi A W
Host Environment: Ubuntu 22.04 (via Docker on Windows 11), using the official Luckfox SDK.

Problem 1: Installing Software Without Full Rebuild
I have a functional Luckfox-Pico Pi A W board with a standard buildroot flashed image. I need to install additional software packages such as:

can-utils (for CAN bus utilities)
boto3 (Python SDK for AWS)
aiocoap (Python CoAP library)
I know these can be added via the SDK's Buildroot configuration, but that requires a full rebuild of the rootfs and re-flashing, which is time-consuming for iterative development.

Core Question 1:
What is the recommended method to install such packages directly on the running board without going through a full SDK rebuild cycle?

Is there a package manager (e.g., opkg) configured and a feed available?
If not, what is the supported workflow for cross-compiling and manually installing libraries onto the target filesystem?
For Python packages, is using pip (if available) a supported method?

Problem 2: Extremely Long SDK Build Times
When working in the SDK, any build process (e.g., for rootfs, firmware, or Buildroot) takes several hours. This delay significantly hampers development speed. Furthermore, builds sometimes fail after these long periods, wasting considerable time.

Core Question 2:
Are there recommended configurations or best practices to drastically reduce build times in the Luckfox SDK?

Are there specific build.sh flags or environment variables to enable parallel compilation or caching?
Is it advisable to build on the native Windows filesystem versus within the Docker container?
Are there common pitfalls that cause unnecessary full rebuilds?
Summary Request:
I am looking for sustainable, efficient workflows for both:

Post-flash software installation.
Faster SDK compilation.
Any guidance on the official or community-supported approaches would be immensely helpful.

Thank you for your time and support.[/b][/b][/b][/b][/b][/b]

The Luckfox Pico Pi A has limited system resources, which is why we recommend using Buildroot. Buildroot enables better integration between system software and Rockchip's closed-source libraries, while also reducing the overall system footprint. Other systems with package managers can technically run on the Luckfox Pico Pi, but they tend to suffer from various compatibility issues. This is because most packages downloaded from package manager repositories are built against glibc or musl, whereas the RV1106 uses uClibc. Moreover, the opkg tool primarily maintains packages for musl, so it cannot be used with Buildroot.

When building Buildroot, only the first compilation usually takes a significant amount of time. If you are simply adding software packages, you can proceed with compilation right after running buildrootmenuconfig. As long as no compatibility issues arise, there is generally no need to perform a clean operation. Finally, you can run ./build.sh firmware to package the rootfs.img, which saves time by skipping the rebuild of other partition images. However, if you need to remove software packages, you will have to either perform a clean build or manually delete the relevant files.