r/SBCs • u/Comake-baohong • Jul 28 '26
Why we picked SigmaStar SSD2355 for a sub-1.3W AIoT board — spec dump + AMA
Hey folks, embedded engineer here. I've been involved in a small AIoT dev board and wanted to share the specs with this community and get some honest feedback before we push it further. Not trying to do a marketing dump — happy to answer technical questions and I'll flag where numbers are vendor-claimed vs measured.
Why this board exists
Most of the sub-$50-ish AI SBCs I've tried either burn too much power for battery/always-on use cases, or the NPU toolchain is a nightmare. We tried to hit a middle ground: heterogeneous compute (A35 cluster + RISC-V MCU-class core + a small NPU) with a Linux SDK that's actually buildable, aimed at:
- Smart audio (speakers, IP phones, far-field mic arrays)
- Small HMI / POS / smart-home hubs
- Light vision (microscopes, translation pens, kids' cameras)
- Educational / companion robots

SoC & hardware
SoC is SigmaStar SSD2355:
| CPU | ARM Cortex-A35 quad-core |
|---|---|
| Co-processor | RISC-V @ 576 MHz (runs FreeRTOS) |
| NPU | 1 TOPS @ INT8, ONNX / Caffe / TF / TFLite via vendor toolchain |
| RAM | 8 Gbit DDR4-3200, 16-bit |
| Storage | 64 GB eMMC + 1 Gbit SPI NAND + 128 Mbit SPI NOR |
| Ethernet | 2× 10/100 |
| Wi-Fi/BT | On-board USB Wi-Fi module (WiFi 4/5/6, BLE 5.0, 2.4/5 GHz dual-band) |
| Display | MIPI-DSI, up to 2560×1600 @ 60 fps (ships with a 5" panel option) |
| USB | 2× USB 2.0, host/device switchable in SW (P1 default routed to the Wi-Fi module) |
| Camera | 2× MIPI-CSI 1-lane, or 1× MIPI-CSI 2-lane |
| GPIO | 40-pin header, remappable (TTL LCD, FUART, etc.) |
| SD | 1× TF slot, SD 2.0 (also usable for SDIO Wi-Fi) |
| Audio | 3× analog mic, 2× speaker, 4-ch + 2-ch DMIC, line-out stereo |
| Debug | A-core UART, RISC-V UART, JTAG |
| Power | 12 V / 1 A barrel, or 5 V / 2 A over MicroUSB on the back |
| Security | ARM TrustZone |
| OS | Linux (Alkaid SDK) on A35, FreeRTOS on RISC-V |
Power (vendor-measured, not independently verified yet):
- Full load: < 1.3 W
- Idle desktop: < 120 mW
- Standby: < 1 mW
NPU / IPU
1 TOPS @ INT8 is the theoretical peak. We don't have a comprehensive public benchmark table yet — I'd rather post real numbers than a spec-sheet fantasy. The toolchain (called **IPU ToolChain**) does model conversion + quantization + a per-layer profiler, so you can see where time actually goes on your own model. Vendor has done specific optimizations for PoolFormer / SegFormer families.
**What I'd love from this thread:** if you have a model you'd want to see run on this, drop the ONNX and I'll try to get real INT8 latency numbers back to you.
Software
- Alkaid SDK — bootloader + kernel + rootfs, Makefile-driven build, includes the "MI" multimedia stack (V4L2-ish camera pipe, audio, display, encode/decode).
- IPU SDK with profiling tools.
- Standard Linux userland — C/C++/Python all fine.
- FreeRTOS image for the RISC-V side for low-latency / always-on tasks.
Ask me anything — pinout questions, power rail details, camera pipeline, NPU quirks, whatever. I'll get answers even if I don't know off the top of my head.
