§ FAQ
Common questions, direct answers.
Engineering questions about E1M modules, the Alp SDK, ordering, and support. Can't find what you're looking for? Email contact@alplab.ai — we read every message.
§ Hardware
What does "pin-compatible across silicon vendors" actually mean?
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). Any module that conforms to E1M fits the same carrier board. Swap an Alif AEN for an i.MX93-based N93 without changing the PCB.
Can I read the E1M specification before buying?
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.
What is the operating temperature range?
All shipping modules are rated −40 °C to +85 °C industrial grade. We choose silicon and passives for long-term availability so you can ship the same design for 5–10 years.
Do you sell single modules or only kits?
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.
§ Software & SDK
Is the Alp SDK open source?
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.
Which OS targets are supported?
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.
How do I move firmware from one module to another?
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 (E1M_I2C0, E1M_GPIO0…) that stay constant across modules.
Can I write firmware by hand or do I have to use a code generator?
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.
§ Buying & support
How do I order an Evaluation Kit?
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.
What is your lead time?
Shipping modules (E1M-AEN, E1M-X V2N, E1M-X V2N+M1, Smart Eye Camera): dev quantities ship within 1–2 weeks. Production volumes 8–22 weeks depending on the SoC. Coming-soon modules (V2H, V2H+M1, N93) sample Q3–Q4 2026.
Do you offer custom SoM configurations?
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.
What's your support response time?
Engineering questions and bring-up support: within one business day, by email. We also run an open community forum at community.alplab.ai and respond to GitHub issues on alp-sdk and e1m-spec.
§ Still have questions?
Engineering, sales, or partnership — pick the path that fits and we'll come back within one business day.