Note: Path may vary based on SDK version (e.g., linux-4.9.84/drivers/ or project/release/.../source/kernel/ ).
To get started with the SigmaStar SDK, developers typically follow these steps: Environment setup - SigmaStarDocs
Modern SigmaStar chips feature embedded IPUs/NPUs (Neural Processing Units). The SDK facilitates machine learning deployment through a separate toolchain layer, often referred to as the toolchain. The AI Deployment Workflow
This technical article provides an architectural deep dive into the SigmaStar SDK, exploring its core components, development workflow, and best practices for building robust embedded applications. 1. Architectural Overview of the SigmaStar SDK sigmastar sdk
Navigate to: Press Y to include it in the kernel image, or M to build it as a loadable module ( .ko ).
public class TouchExample public static void main(String[] args) // Initialize the touchscreen device Touchscreen touchscreen = new Touchscreen(); touchscreen.init();
// Pseudocode for configuring VIF Dev and Channel MI_VIF_DevAttr_t stDevAttr; stDevAttr.eIntfMode = E_MI_VIF_MODE_MIPI; stDevAttr.eWorkMode = E_MI_VIF_WORK_MODE_1MULTIPLEX; // Set resolution attributes... MI_VIF_SetDevAttr(vifDevId, &stDevAttr); MI_VIF_EnableDev(vifDevId); MI_VIF_ChnAttr_t stChnAttr; stChnAttr.stCapRect.u32Width = 1920; stChnAttr.stCapRect.u32Height = 1080; MI_VIF_SetChnAttr(vifChnId, &stChnAttr); MI_VIF_EnableChn(vifChnId); Use code with caution. Step 3: Setting Up the Encoder (VENC) Note: Path may vary based on SDK version (e
The BSP provides the Linux kernel, U-Boot, and driver source code. SDK Structure: The SDK is typically divided into: Customer Layer: Where application-level code is developed.
SigmaStar provides modules to debug SDK components and check driver status (e.g., VPE/DIVP debugging).
By leveraging the full capabilities of the SigmaStar SDK, developers can accelerate time-to-market and build high-performance products in the competitive IoT and imaging sectors. The AI Deployment Workflow This technical article provides
: SigmaStar MPI functions explicitly return status indicators. Missing a failure code at pipeline creation can result in silent failures or segmentation faults downstream.
SigmaStar Technology has established itself as a major player in the high-performance imaging, video processing, and AIoT (Artificial Intelligence of Things) markets. Whether it’s IP cameras, vehicle electronics (DVRs), or smart display HMI systems, SigmaStar chips provide the hardware foundation, while the serves as the critical bridge for developers to unlock that potential.
The SigmaStar SDK is a comprehensive software development kit that provides the drivers, middleware, and sample code necessary to build applications on SigmaStar processors (like the MSC313E, SSC335, or SSD202).
#include "mi_venc.h" void* stream_processing_thread(void* arg) MI_VENC_CHN vencChn = 0; MI_VENC_Stream_t stStream; MI_VENC_Pack_t stPack; stStream.pstPack = &stPack; while (g_bRunning) // Read the compressed block from hardware with a timeout (e.g., 200ms) if (MI_SUCCESS == MI_VENC_GetStream(vencChn, &stStream, 200)) // Loop through packets inside the stream frame block for (MI_U32 i = 0; i < stStream.u32PackCount; i++) // stStream.pstPack[i].pu8Addr contains the pointer to compressed H.264/H.265 payload // stStream.pstPack[i].u32Len contains the payload size in bytes fwrite(stStream.pstPack[i].pu8Addr, 1, stStream.pstPack[i].u32Len, fpOutputFile); // Release the stream buffer back to the SDK pool immediately! MI_VENC_ReleaseStream(vencChn, &stStream); return NULL; Use code with caution. 6. Best Practices for Developing with SigmaStar SDK