Two chips, one architecture. NP-1 is the full neural engine; NP-C1 is the same compute scaled into a camera-sized package. Everything below is what we publish in the datasheet.
The full-size part, built for robotics, multi-camera systems, and any platform that needs headroom for modern models.
| Process node | 6 nm-class |
|---|---|
| Peak compute | Up to 40 TOPS INT8 · 20 TOPS FP16 (sparse-aware) |
| On-chip memory | 18 MB SRAM (L2) |
| External memory | LPDDR4X / LPDDR5 · up to 68 GB/s |
| Typical power | 8 W (sustained inference) · 12 W peak |
| Idle power | < 0.8 W |
| Package | 14 × 14 mm BGA, 0.5 mm pitch |
| Operating temp | -40 °C to 105 °C junction |
| Host interfaces | PCIe Gen3 ×4 · 2× 10G Ethernet · 4× MIPI CSI-2 (4-lane) |
| Memory subsystem | 18 MB L2 SRAM (banked, dual-port) · per-tile scratchpad · LPDDR4X / LPDDR5 |
| Memory protection | Inline ECC on SRAM and LPDDR data paths |
| Instruction set | NP-ISA v2 — tensor, vector, and DMA instructions |
| Security | Secure boot · inline memory-encryption engine · hardware key store |
| Formats | INT8, INT4, FP16, BF16 |
For smart cameras, doorbells, and sensor nodes where the whole compute budget has to fit inside a few square centimeters.
| Process node | 6 nm-class |
|---|---|
| Peak compute | Up to 8 TOPS INT8 · 4 TOPS FP16 |
| On-chip memory | 4 MB SRAM |
| External memory | LPDDR4X · up to 12 GB/s |
| Typical power | 1.5 W (sustained) · 2.5 W peak |
| Idle power | < 0.15 W |
| Package | 4 × 4 mm wafer-level, 0.4 mm pitch |
| Operating temp | -20 °C to 85 °C ambient |
| Host interfaces | 1× MIPI CSI-2 (4-lane) · USB 2.0 · SPI |
| Memory subsystem | 4 MB SRAM (banked) · LPDDR4X |
| Memory protection | Inline ECC on SRAM |
| Instruction set | NP-ISA v2 — same toolchain as NP-1 |
| Security | Secure boot · hardware key store |
| Formats | INT8, INT4, FP16 |
The memory hierarchy is sized so a model's hot weights live in SRAM, not in DRAM. That's the difference between deterministic latency and "usually fast."
The instruction set is fixed-width and deliberately compact. It has just the operations a neural engine needs — nothing general-purpose — which is how the control plane stays out of the data path. You won't hand-write it; the compiler will.
| Tensor | Tiled GEMM, convolution, and attention primitives over the systolic array |
|---|---|
| Vector | Elementwise activation, normalization, and reduction on the vector engine |
| Memory | DMA and descriptor-based movement between scratchpad, L2, and DRAM |
| Control | Synchronization barriers, zero-skip predicates, and precision-cast hints |
| Sparse | Compressed-weight and sparse-activation dispatch, decoded in hardware |
Mixed-precision inference lets a single model keep its sensitive layers in FP16 while running the bulk in INT8 — accuracy and throughput at once.
The toolchain is a compiler, not a runtime puzzle. Export from PyTorch or ONNX, run one calibration pass, and flash. No hand-writing kernels, no per-platform rewrites.