cd ~/sigmastar_workspace tar --exclude='build/.ccache' --exclude='kernel/.git' \ -cjf Sigmastar_SDK_ready_to_use.tar.bz2 Sigmastar_SSD222_SDK/ Include a README with environment setup instructions. Pitfall 1: Hardcoded Absolute Paths Some SigmaStar build scripts hardcode paths like /home/user/sdk . If your username differs, you must:
cd $SIGMASTAR_SDK_PATH/buildroot make menuconfig # Select packages make Then point the SDK to use the new rootfs: sigmastar sdk install
find . -type f -name "*.mk" -o -name "*.sh" | xargs sed -i 's|/old_user|/new_user|g' Legacy SDKs (pre-2021) require Python 2.7. On modern Ubuntu: cd ~/sigmastar_workspace tar --exclude='build/
wine ISPTool.exe -f ssd222_firmware.bin Copy ssd222_firmware.bin to a FAT32 SD card as auto_update.bin . Insert into the board and power on. -type f -name "*
cat $SIGMASTAR_SDK_PATH/build/config | grep -E "BOARD_NAME|CHIP|UBOOT_CONFIG" 4.1 Clean Any Previous Builds cd $SIGMASTAR_SDK_PATH make clean # or ./build/clean_all.sh 4.2 Full SDK Build The most common entry point is the top-level Makefile:
#!/bin/bash export SIGMASTAR_SDK_PATH=~/sigmastar_workspace/Sigmastar_SSD222_SDK export PATH=$SIGMASTAR_SDK_PATH/toolchain/arm-linux-gnueabihf/bin:$PATH export CROSS_COMPILE=arm-linux-gnueabihf- export ARCH=arm Source it:
sudo apt install python2.7 sudo ln -s /usr/bin/python2.7 /usr/local/bin/python Even on x86_64, some SigmaStar tools are 32-bit executables:
