Download and Extract the Source Package

Download the archive here: recamera-pro-sdk-v1.0.10.tar.gz. This is the full BSP source package described in this guide.

Package Information

Item	Value
File name	recamera-pro-sdk-v1.0.10.tar.gz
Archive size	About 3.7 GB (3,928,456,385 bytes)
Extracted size	About 12 GB
Top-level directory	recamera-pro-sdk-v1.0.10/
SHA-256	0c171f7a65ed87a7112f07eb0408b91b934f456af32d91608f961a4a21bced8a

The SHA-256 value was calculated from the actual distribution archive when this Wiki was written. Repacked archives or bundles created with ./build.sh save may have a different checksum; in that case, use the checksum from the release record.

Host Requirements

Item	Requirement
Operating system	64-bit Ubuntu, 20.04 or later recommended
CPU architecture	x86_64 or aarch64
Disk space	At least 20 GB free on the SDK partition; 100 GB or more is recommended if you keep multiple build outputs
Memory	16 GB or more recommended; parallel media and kernel builds can use substantial memory
Network	Required on the first setup_build_env.sh run to download tools and dependencies

Measured reference: on a host with a 937 GB SDK partition (242 GB used), extracting the 3.7 GB archive to 12 GB took about 20 seconds with 24-core parallel pigz. The system's single-threaded gzip can take several times longer.

Verify the Archive

sha256sum recamera-pro-sdk-v1.0.10.tar.gz

Compare the output with the checksum above. If it does not match, the download may be truncated or repackaged. Do not continue.

Extract the Archive

Parallel extraction with pigz is recommended:

sudo apt install -y pigz
tar -I "pigz -d -p 16" -xf recamera-pro-sdk-v1.0.10.tar.gz

Or use the standard command:

tar -xzf recamera-pro-sdk-v1.0.10.tar.gz

After extraction, confirm that the main entry points exist. These are symbolic links into project/:

cd recamera-pro-sdk-v1.0.10
ls -l build.sh rkflash.sh readme_cn.txt setup_build_env.sh

Expected output includes:

build.sh -> project/build.sh
rkflash.sh -> project/rkflash.sh
readme_cn.txt -> project/readme_cn.txt

Important Precautions

• Do not extract or copy this package on Windows. The SDK relies heavily on symbolic links (build.sh, .BoardConfig.mk, and PDF shortcuts under docs/) and executable permissions (build.sh, rkflash.sh, and binaries under tools/). Windows filesystems may lose these, causing build failures or missing commands. The bundled readme_en.txt also calls this out.
• If you need to transfer the package between Windows and Linux, keep it as a tar archive and extract it on Linux, or use git / repo to check it out.
• Avoid spaces and non-ASCII characters in the installation path. Buildroot and some Makefiles do not handle spaces reliably.
• Do not build on a noexec-mounted partition; binaries such as tools/linux/Linux_Upgrade_Tool/upgrade_tool need execute permission.
• The extracted SDK does not contain .repo/; this is a source snapshot. Ignore the repo sync instructions in readme_en.txt because they do not apply to this package.

Repair Lost Executable Permissions (Recovery)

If the package was transferred through an environment that did not preserve permissions, try:

cd recamera-pro-sdk-v1.0.10
chmod +x build.sh rkflash.sh setup_build_env.sh project/build.sh project/rkflash.sh
chmod +x tools/linux/Linux_Upgrade_Tool/upgrade_tool
find . -name "*.sh" -exec chmod +x {} \;

Once symbolic links are lost, chmod cannot restore them; re-extract the original tar archive.

First Step After Extraction

./setup_build_env.sh --check     # Check only; report missing tools without changing anything

See Set Up the Build Environment for details.

Upgrade or Switch to a New SDK Version

• Each SDK release is a separate tar archive. Extract a new version into a different directory; do not mix versions.
• Board-configuration numbers in the lunch menu are generated by sorting filenames under project/cfg/ and can change between releases. Record the full configuration filename in documentation and scripts; do not rely on the menu number.
• To migrate your application, copy the entire project/app/<your-directory>/ directory into the same location in the new SDK, then enable the corresponding RK_APP_xxx=y option in the new board configuration.

Tech Support & Product Discussion

Thank you for choosing our products! We are here to provide you with different support to ensure that your experience with our products is as smooth as possible. We offer several communication channels to cater to different preferences and needs.