Common questions, direct answers.

The E1M open standard fixes the carrier-board pinout, mechanical envelope, and electrical interface of two form factors — 35 × 35 mm (312 pads) and 45 × 65 mm (496 pads). The two footprints are not interchangeable with each other; any module that conforms to a footprint fits every carrier built for that footprint. Swap an E1M-X V2N for a V2H or V2N-M1 without changing the PCB. Today the E1M footprint carries Alif modules and the E1M-X footprint carries Renesas modules, some with a DeepX accelerator; because the footprints are published, other silicon vendors and module makers can build conforming modules too.

Yes. The spec is published under CC BY-SA 4.0 at github.com/alplabai/e1m-spec — no NDA, no email gate. The pinout JSON files are machine-readable so you can validate your carrier-board design programmatically.

The ambient operating range is per module: E1M-X V2N and V2N-M1 are rated −40 °C to +85 °C, and E1M-AEN is rated −40 °C to +75 °C (the limit is set by the Alif Ensemble SoC). We choose silicon and passives for long-term availability so you can ship the same design for 5–10 years.

Both. Single modules are available through our distributors (Astute, Endrich, NISKO) for development quantities. For production volumes, contact sales — we work directly on EAU and forecast-driven pricing.

Yes. The SDK is at github.com/alplabai/alp-sdk under a permissive license. Our VS Code extension and tooling are also open. We wrap each vendor's proprietary runtime under one C/C++ API on top of Arm CMSIS.

Bare-metal, Zephyr RTOS, and Yocto Linux — declared per-core in a single board.yaml. Heterogeneous topologies (e.g. Yocto + Zephyr on different cores of the same SoM) are supported on the E1M-X family.

Change one line: som.sku in your board.yaml. The SDK re-runs the pin allocator for the new module, regenerates the per-OS configuration (Zephyr conf, DTS overlays, CMake args), and rebuilds. The application code itself uses pinout-named pads (ALP_E1M_I2C0, ALP_E1M_PWM3, ALP_E1M_GPIO_IO15…) that stay constant across modules.

Either path is first-class. Write firmware against <alp/...> headers by hand, or use the alp-studio code generator with a visual configurator. The hand-written path is not a studio escape hatch — anything studio emits, you can write by hand.

Click "Request a Dev Kit" anywhere on the site, tell us which module you're evaluating, and we'll ship one. Direct from Sweden for development quantities; through Astute / Endrich / NISKO for region-local fulfilment.

Shipping modules (E1M-AEN, E1M-X V2N, E1M-X V2N-M1): dev quantities ship within 1–2 weeks. Production volumes 8–22 weeks depending on the SoC. E1M-X V2H and V2H-M1 are in development; register on their product pages for updates.

Yes. We support custom RAM / Flash / connectivity options for production volumes above 1k units. Contact sales with your requirements and we'll come back with a quote.

Engineering questions and bring-up support: within one business day, by email at contact@alplab.ai. We also respond to GitHub issues on alp-sdk and e1m-spec.