§ Silicon comparison
Alif vs Renesas vs DeepX — pick per project, not per company.
The usual edge AI question is which silicon vendor to standardise on. On E1M that's the wrong question: every one of these chips is programmed through the same SDK, and each footprint is an open standard any vendor can build to, so you choose per project instead of standardising on one vendor.
| Silicon | E1M family | Cores | NPU | AI compute | Best for |
|---|---|---|---|---|---|
| Alif Ensemble | E1M-AEN | Cortex-M55 (+ optional A32) | Ethos-U | 250–454 GOPS | Always-on, sub-1 mW perception and keyword spotting |
| Renesas RZ/V2N · V2H | E1M-X | Cortex-A55 (+ Cortex-R8) | DRP-AI3 | 4–8 TOPS | Real-time vision with hard-real-time control on one module |
| DeepX DX-M1 | E1M-X +M1 | Companion NPU on E1M-X | DX-M1 | up to 33 TOPS | High-throughput multi-stream inference |
Why one SDK across all of them wins
Standardising on a single silicon vendor is a bet: that their roadmap, pricing, and supply stay aligned with your product for its whole life. E1M removes the bet. Because theAlp SDKwraps each vendor SDK behind one<alp/*.h> API, and each footprint is a publishedopen standard, you can match silicon to each project and keep your application code when you change modules. Within a footprint family the carrier board stays too; today Alif modules use E1M and Renesas modules (with or without DeepX) use E1M-X, so moving between those vendors is a carrier change, not a firmware rewrite.
See the modules these run on in theE1M lineup, or readwhy open beats locked-in.
Frequently asked questions
- Which edge AI silicon should I choose: Alif, Renesas, or DeepX?
- It depends on the workload. Alif Ensemble suits sub-milliwatt always-on perception; Renesas RZ/V2N/V2H suits real-time vision with hard-real-time control; DeepX DX-M1 adds high-throughput multi-stream inference up to 33 TOPS. With E1M you don’t have to commit company-wide — each project can pick its silicon and still share one SDK. Carrier boards are shared per footprint: Alif modules use the 35 × 35 mm E1M footprint, Renesas modules (with or without DeepX) use the 45 × 65 mm E1M-X footprint.
- Do I have to rewrite firmware to switch silicon?
- No. The Alp SDK exposes one C/C++ API across all three vendors. Changing the module is a one-line som.sku edit in board.yaml; the SDK rebuilds against the same <alp/*.h> API, so application code written against that API carries over. Within a footprint family (for example E1M-X V2N to V2N+M1) the carrier board stays the same; moving between Alif on E1M and Renesas on E1M-X also needs a carrier for the other footprint.