Firmware Environment
Neural Inverse includes a purpose-built firmware development environment. When you open a firmware project, the IDE activates hardware context — loading your MCU's register maps, datasheet data, timing constraints, and compliance rules directly into the LLM context.
Open the Firmware console with Cmd+Alt+F (macOS) or Ctrl+Alt+F (Linux/Windows).
At a Glance
| MCU Database | 361 variants across 27 manufacturers |
| Agent Tools | 127 fw_* tools across 23 categories |
| Compliance Frameworks | 8 (MISRA C, CERT-C, IEC 61508, ISO 26262, DO-178C, IEC 62304, AUTOSAR) |
| Build Systems | 7 (PlatformIO, CMake, Make, ESP-IDF, Cargo, Arduino CLI, Zephyr) |
| Flash Programmers | 7 (OpenOCD, STM32CubeProgrammer, esptool, nrfjprog, J-Link, pyOCD, dfu-util) |
| Debug Servers | 5 (OpenOCD, J-Link GDB Server, pyOCD, st-util, QEMU) |
| Hardware Instruments | 3 (Logic Analyzer, Power Analyzer, Oscilloscope) |
| Tracing | RTT (Segger), ITM/SWO (Cortex-M), Serial UART |
Documentation
- Getting Started — Project detection, MCU selection, first build
- MCU Database — 361 supported MCUs and their capabilities
- SVD & Register Maps — SVD parsing, register completions, hover info
- Build & Flash — Build systems, binary analysis, flash programming
- Debug — GDB integration, breakpoints, memory inspection
- Serial & Tracing — UART, RTT, ITM/SWO
- Hardware Instruments — Logic analyzer, power profiler, oscilloscope
- Code Generation — Peripheral init, ISR, DMA, clock, linker scripts
- Pin Mux & Clock Tree — Pin allocation, conflict detection, PLL solving
- Compliance — MISRA C, CERT-C, ISO 26262, IEC 61508, DO-178C
- Agent Tools Reference — All 127 fw_* tools
- Project Configuration — Firmware.inverse, NI.md, .niignore, .inverse/
- Datasheet Intelligence — PDF extraction, register maps, timing constraints
- HIL Testing — Hardware-in-the-loop test definitions and runner
- RTOS Support — FreeRTOS, Zephyr, Embassy thread inspection
- Peripheral Catalog — Component library for external ICs
Was this page helpful?
Last edited