Hardware-to-firmware with evidence, not assumptions.
Analyze schematic netlists, generate firmware, build, and verify in a governed workflow.
Offline Technical PreviewSession: a7f3c… | Context: 12,480 tokens
You > What peripherals does my STM32F407 expose on connector J3?
Omera 3.6 > Based on the system map, connector J3 exposes:
• SPI1 (PA5/SCK, PA6/MISO, PA7/MOSI)
• I2C1 (PB6/SCL, PB7/SDA)
• USART2 (PA2/TX, PA3/RX)
You > █
View VS Code Extension Interface
PA5 -> SPI1_SCK PA6 -> SPI1_MISO PA7 -> SPI1_MOSI
How Omera Firmware Works
A unified automation pipeline integrating physical circuits to embedded code.
Understand Hardware
Import EDA netlists (KiCad/Altium), auto-detect target MCUs, and classify board pin configurations.
Assess Safety
Analyze critical signal networks and evaluate peripheral pin constraints before generation.
Resolve Architecture
Map compatible driver packages to hardware components and output structural plans.
Build & Simulate
Compile code via PlatformIO and run deterministic host-side firmware simulation traces.
Verify & Package
Execute static and dynamic validation gates and package artifacts into a ZIP Evidence Pack.
OMERACODE / SYSTEM MAP DETECTOR
Visualizing the Hardware-Firmware Boundary
Every view is generated from versioned project artifacts—not drawn as a decorative architecture diagram.
View Hardware Map
MCU Pin Mappings
Electrical Connectivity Graph
[STM32F407]
├── (SPI1) ──> [SSD1306 OLED]
├── (USART1) <═> [FT232R USB Bridge]
└── (I2C1) ──> [BME280 Sensor]
View Firmware Interaction
FreeRTOS Task Scheduler
Manages core application runtime tasks and execution cycles.
Peripheral Drivers
+------------------+ +------------------+
| stm32f4xx_hal | --> | BME280 Driver |
+------------------+ +------------------+
| SSD1306 Driver | --> | FDCAN Driver |
+------------------+ +------------------+
View Simulation Trace
View Verification Diff
Build, Debug and Recover Loop
Intelligent, automated build diagnostics and patching under human control.
No more tedious manual debugging. When compilation fails, Omera 3.6 analyzes the build log and proposes automated patch drafts.
- Build Explain: AI parses compiler errors and explains root causes in plain language.
- Proposed Changes: Generates isolated code or configuration changes (draft patches).
- Human Review Required: Draft patches are applied only after manual review and human approval.
- Re-Verify: Re-builds automatically to verify compilation passes the safety gate.
Evidence and Governance
Rigorous safety controls and structural boundary validation.
Command Risk & Confirmation Policy
| Command Group | Example Command | Confirmation |
|---|---|---|
| Read-only | `doctor`, summary, inspect | Optional |
| Generate artifact / build | build, generate, draft patch | Policy-based |
| Modify source code | apply patch | Required |
| Hardware interaction | debug, flash | Required |
| Destructive / Admin | revoke, delete, overwrite | Required |
Workspace Sandbox
The AI agent is restricted to files within the active workspace. Choke points block Path Traversal and Symlink Escape.
Evidence Pack Export
Exports secure ZIP Evidence Packs containing logs, checksums, and test runs (not a compliance certification).
One Workflow, Two Ways of Working
Select the interface that fits your engineering workflow.
Omera CLI
Designed for automation, CI/CD pipelines, bulk scripting, hardware flashing, and admin tasks.
- ✓ 55 commands
- ✓ REPL chat & slash commands
- ✓ TUI Dashboard
VS Code Extension
Visual project workspace, interactive system maps, side-by-side diffing, and log visualizer.
- ✓ 3 Panels (Control, Copilot, RUN)
- ✓ Interactive System Map
- ✓ Visual Diff View
Use Cases
How embedded engineers accelerate delivery with Omera Firmware.
IoT Sensor Node Firmware (ESP32-S3)
Initialize ESP32-S3 firmware, read BME280 sensor data over I2C, transmit telemetry via UART, and configure deep sleep cycles.
Build Failure Recovery (STM32)
Diagnose missing HAL driver links from build logs, generate platformio.ini patch drafts, and recover the build.
Board Log Analysis
Import CSV/LOG data from hardware test runs, evaluate cycle times, and suggest optimal register values.
Evidence Packaging for Audit
Collect static analysis logs, Renode simulation reports, and verification states into a signed ZIP artifact.
Security & Deployment Modes
Govern your project data. All AI actions are routed under Omera 3.6.
Local Mode
Run Omera 3.6 on infrastructure you control. Data does not leave your local network when configured with a local inference engine.
BYOK Mode
Provide your own API keys. AI processing data goes directly to the configured AI provider, bypassing the Omera Account Backend.
Omera Account Mode
Backend routes requests, manages usage limits, and entitlement. Users always interact with Omera 3.6.
Credential Protection
Credentials are encrypted in VS Code SecretStorage or protected via OS file permission 0600.
Pricing Plans
Start free, scale as your project demands.
Free
- ✓ 50 AI messages / month
- ✓ 0 Nexus Runs
- ✓ 32K token context window
- ✓ Full System Map visibility
- ✓ Free CLI & Extension access
Pro
- ✓ 5,000 AI messages / month
- ✓ 500 Nexus Runs / month
- ✓ 200K token context window
- ✓ Nexus AI Engine access
- ✓ Swarm Repair capability
- ✓ Priority support
Team
- ✓ 50,000 AI messages / month
- ✓ 5,000 Nexus Runs / month
- ✓ 1M token context window
- ✓ Dedicated support manager
- ✓ Team workspace sync
Preview limits. Final entitlements are confirmed at checkout. Looking for full feature comparisons? View the complete pricing table here.
Frequently Asked Questions
What kinds of tasks can Omera handle?
Omera excels at analyzing EDA netlists, generating peripheral driver code, building firmware via PlatformIO, running host-side simulation traces on Renode, and packaging evidence artifacts. It is purpose-built for the hardware-to-firmware boundary.
How does Omera work with my existing tools?
Omera CLI runs in your terminal alongside any IDE. The VS Code Extension integrates directly into your editor with dedicated panels. Both interfaces work with PlatformIO, KiCad, Altium netlists, and standard Git workflows without requiring changes to your process.
Is my source code secure?
Yes. In Local Mode, data never leaves your machine. In BYOK Mode, requests go directly to your configured AI provider. In all modes, the workspace sandbox enforces strict directory boundaries and only pre-authorized CLI commands are permitted. Credentials are stored using VS Code SecretStorage or OS-level file permissions.
Does Omera replace compliance certification?
No. Omera generates Evidence Packs containing build logs, test reports, and verification results to assist with internal design reviews. OmeraCode is not a certification body and does not replace official CE, FCC, ISO, or IEC compliance testing.
What are the system requirements?
Omera CLI works on macOS, Linux, and Windows. The VS Code Extension requires VS Code 1.80+. PlatformIO Core is required for firmware compilation. An internet connection is needed for Account Mode and BYOK Mode; Local Mode works fully offline.
Start building in minutes
Choose your preferred interface and begin your first hardware analysis.
Terminal
$ npm install -g @omeraeda/cli$ omera doctor$ omera chatRequires Node.js 18+ and PlatformIO Core.
VS Code
Search "Omera" in the Extensions panel,or install from the VS Code Marketplace.Requires VS Code 1.80+ and PlatformIO IDE extension.