Upon successful compilation, the output images are usually located in the images or output folder.

Typical files generated:

These files are ready to be flashed to the device using Sigmastar flashing tools (usually located in tools/flash_tool).

Typical SDK filenames look like:

Installation steps:

# Create work directory
mkdir -p ~/sigmastar/sdk
cd ~/sigmastar/sdk

To modify kernel settings or driver inclusion:


make menuconfig
# or specifically for kernel
make kernel_menuconfig



# Write a simple C file
echo '#include <stdio.h>
int main()  printf("SigmaStar SDK OK\n"); return 0; ' > test.c

export SIGMASTAR_MAKE_JOBS=$(nproc)
EOF



Source it:


source setup.env



Pro tip: Create an alias in .bashrc:


alias sdk_start='cd ~/sigmastar/infinity6/SigmaStar-SDK-* && source setup.env'

Sigmastar Sdk Install 90%

Upon successful compilation, the output images are usually located in the images or output folder.

Typical files generated:

These files are ready to be flashed to the device using Sigmastar flashing tools (usually located in tools/flash_tool). sigmastar sdk install

Typical SDK filenames look like:

Installation steps:

# Create work directory
mkdir -p ~/sigmastar/sdk
cd ~/sigmastar/sdk

To modify kernel settings or driver inclusion:


make menuconfig
# or specifically for kernel
make kernel_menuconfig



# Write a simple C file
echo '#include <stdio.h>
int main()  printf("SigmaStar SDK OK\n"); return 0; ' > test.c

export SIGMASTAR_MAKE_JOBS=$(nproc)
EOF
 Upon successful compilation, the output images are usually


Source it:


source setup.env



Pro tip: Create an alias in .bashrc:


alias sdk_start='cd ~/sigmastar/infinity6/SigmaStar-SDK-* && source setup.env'