# For 32-bit SSD201/SSD202 export PATH=/project/sigmastar/toolchain/gcc-sigmastar-linux-uclibc-4.8.5/bin:$PATH
List the available configuration files to find your specific chip and storage profile (SPI NOR flash vs. SPI NAND flash): ls configs/ Use code with caution. Load your target board configuration: make configs/ipc_ssc335_nor_br_defconfig Use code with caution. Step 2: Compile the Image Stack
of free space for storing code, SDK, toolchain, and compiling output. + recommended for faster compilation. 2. Install Required Dependencies sigmastar sdk install
You need the compressed SDK file, typically named:
: Toolchain not in PATH or not installed Solution : Verify toolchain path, add to ~/.bashrc , and re-source Step 2: Compile the Image Stack of free
The SDK is generally split into four main components that must be compiled in order: comake.online Boot Compilation : Navigate to the directory, select the appropriate configuration (e.g., make infinity2m_defconfig for NOR flash), and run to generate u-boot.xz.img.bin Kernel Compilation directory, export the architecture ( export ARCH="arm" ) and toolchain, choose your model's config, and run to produce Project Compilation : Navigate to the directory and run the configuration script ( ./setup_config.sh ) followed by make image to package everything into flash-ready binaries. Root File System
Many SigmaStar build scripts rely on standard bash syntax. Ubuntu defaults to dash , which causes compilation scripts to fail. Reconfigure it by running: sudo dpkg-reconfigure dash Use code with caution. Install Required Dependencies You need the compressed SDK
The SDK relies heavily on symbolic links and specific directory structures (e.g., placing SGS_IPU_SDK in the home directory). Errors frequently occur if these are not strictly followed or if sudo permissions are misconfigured in /etc/sudoers . Recommended Best Practices