System-aware AI for embedded development
Stop vibe coding your firmware
A complete IDE — not a plugin pile. One install gives you editor, GCC toolchain, OpenOCD, SDK path, and AI assistant.
AI tools don’t understand your system — that’s why they break. IOcomposer works with your real SDK, build system, and hardware so firmware actually compiles, flashes, and runs.
AI coding works… until it doesn’t
- Wrong APIs that don’t exist in your SDK
- Code that compiles but fails on hardware
- Endless prompt → run → debug loops
- Lost context between iterations
- Hours wasted fixing “almost correct” code
👉 The problem isn’t AI — it’s missing system context
Embedded development isn’t just code — it’s a system
LLMs fail when they don’t understand your SDK, your project state, your build flow, and your hardware constraints.
IOcomposer gives AI the context it needs to work inside a real embedded workflow.
board.h
Demo: generate a bare-metal nRF54L15 BLE project, build it, and launch debug in under 3 minutes.
Deterministic project creation, grounded AI, and a direct build → flash → debug path. Start on a supported DevKit, then move to your custom board by updating a few pin assignments in board.h and rebuilding.
#define UART_TX_PIN 6
#define UART_RX_PIN 8
#define SPI_SCK_PIN 25
#define SPI_MOSI_PIN 24
#define SPI_MISO_PIN 23
#define LED1_PIN 13
Supported preview workflows today include Nordic nRF52832, nRF52840, and nRF54L15 with SoftDevice BLE. Preview support for STM32, Renesas, and Microchip is in progress.
Prompt or use the wizard
Create a managed project for a real MCU target, with the right template and build settings from the start.
Build with grounded AI
The AI reads your installed SDK headers and project files before proposing code, so output matches the APIs on your machine.
Flash and debug
Go from clean workspace to hardware bring-up, breakpoints, and SWD/JTAG debug from one window.
Watch the Workflow
AI-assisted build fix: resolve errors and regenerate clean project
Creating a BLE Peripheral project with the IOcomposer wizard
One-click: flash + launch debugger from the chat panel
One script full install in 10 min.
Features in Detail
AI detects a subtle SPI configuration error and suggests the fix
AI prompt opens Nordic nRF54L15 baremetal code sample file
AI shows Nordic nRF54L15 baremetal code sample
Why IOcomposer
Why engineers switch
Most AI tools guess. IOcomposer gives AI real embedded context: your installed SDK, your project files, and a deterministic build → flash → debug workflow.
System-aware project setup
Start from a managed firmware project that already understands the target, build settings, and debug path instead of stitching tools together by hand.
AI with real system context
IOcomposer reads your installed SDK headers, project files, and local environment so suggestions match actual APIs and fit the workflow you are using.
One embedded workflow
Generate code, build it, flash hardware, and launch SWD/JTAG debug from one place so each iteration stays grounded in the real system.
From DevKit to real hardware
Move from supported DevKits to custom boards without restarting from scratch, while keeping the project structure and bring-up path intact.
* IOcomposer is built to reduce the prompt → run → debug loop by grounding AI in your installed SDK, project context, and embedded workflow.
Free preview
Install IOcomposer
No credit card. Free preview available now.
One command sets up the IDE, GCC ARM toolchain, OpenOCD, SDK path, and AI plugin. Typical setup time: about 15 minutes.
curl -fsSL https://iocomposer.io/install_ioc_macos.sh -o /tmp/install_ioc_macos.sh && bash /tmp/install_ioc_macos.sh
curl -fsSL https://iocomposer.io/install_ioc_linux.sh -o /tmp/install_ioc_linux.sh && bash /tmp/install_ioc_linux.sh
powershell -NoProfile -ExecutionPolicy Bypass -Command "irm https://iocomposer.io/install_ioc_windows.ps1 | iex"
By installing IOcomposer, you agree to the Terms of Service and Privacy Policy.
The installer may download third-party SDKs (for example Nordic) subject to their own license terms.
What you are evaluating
One proof path, not ten disconnected claims
IOcomposer works best when judged on one complete embedded outcome: create a correct project, generate code against the local SDK, build it, flash hardware, and debug it from the same IDE.
The IDE is built around deterministic managed project creation rather than a loose pile of editor extensions. That means the project wizard, target settings, and build configuration are aligned from the start. In the current preview, the strongest demonstrated workflows today are nRF52832, nRF52840, and nRF54L15 with SoftDevice-aware bring-up.
The AI layer is grounded on your installed SDK headers and your current project context before it proposes code. Instead of treating IOcomposer like a generic AI code editor, evaluate whether it reduces the common embedded setup tax: wrong API guesses, broken launch configs, missing linker details, and slow board bring-up.
The portability story is equally bounded: start on a DevKit, then move to a custom board with a controlled pin-map update in code. That is a much clearer promise than a broad claim about every possible vendor, board package, or plugin combination.
Supported today
Current supported workflows
Current highlighted targets: nRF52832, nRF52840, and nRF54L15. BLE workflows use SoftDevice S132/S140 on nRF52 and S145 on nRF54L15.
Custom boards: IOcomposer targets the MCU directly, so moving from a supported DevKit to your own PCB is a bounded firmware configuration task instead of a full board-package exercise.
Preview roadmap: STM32, Renesas, and Microchip preview support is in progress.
Enable AI chat after install
The account step comes after the installer, not before. Keep the first commitment simple.
- Install IOcomposer using one of the commands above, then launch the IDE.
- Open Preferences → IOcomposer → Account.
- Click Create free account or Sign in to enable AI chat during preview.
Tip: if AI chat is disabled, the Chat panel shows a sign-in prompt and a shortcut to the Preferences page.
Best fit
Who should try this first
Beyond Arduino
You want a real debugger, vendor SDK access, and a more professional path forward without jumping straight into a fragmented toolchain stack.
Bare-metal firmware developers
You need to bring up firmware quickly, especially current nRF52 or nRF54 preview workflows, and you care about direct hardware control and repeatable setup.
RTOS firmware developers
You're building with FreeRTOS, RTX, or a similar RTOS and need AI that understands your task model and peripheral constraints — not generic C suggestions detached from your actual SDK.
Custom board teams
You need a shorter path from DevKit prototype to your own PCB, with bounded porting work and less board-support churn.
FAQ
Need more detail? Product comparisons and deeper technical notes can live on separate pages.
What is IOcomposer?
IOcomposer is an embedded C/C++ IDE for MCU firmware development. It combines deterministic managed project creation, AI grounded on your local SDK headers, and integrated build, flash, and debug workflows in one environment.
Which targets work today?
Current supported workflows highlight Nordic nRF52832, nRF52840, and nRF54L15. Preview support for STM32, Renesas, and Microchip is in progress.
Does IOcomposer require Zephyr or nRF Connect SDK?
No. IOcomposer uses the Nordic bare-metal SDK with direct hardware access and SoftDevice integration — not the nRF Connect SDK, which requires Zephyr. You get full control without the Zephyr stack.
Does the AI use my real SDK headers?
Yes. The AI indexes your locally installed SDK and project files before generating code, so it can align with the actual headers and APIs available on your machine.
Does IOcomposer work on custom boards?
Yes. IOcomposer targets the MCU directly, so moving from a DevKit to a custom PCB is typically a pin-map update in your code rather than a board-package rewrite.
Is IOcomposer free to try?
Yes. IOcomposer is in free preview. Install the IDE, create a free account from Preferences → IOcomposer → Account, and use AI chat during preview with no credit card required.
Start with the demo, then install the preview.
The fastest way to evaluate IOcomposer is to watch one complete workflow, then run the installer and create your first project.