AI-ASSISTED · MULTI-VENDOR · WINDOWS

AI-assisted firmware.
You stay in control.

MCU Pilot is a Windows workbench for STC 8051 and STM32. AI reads your project, edits the code, triggers the build, and reports the real compiler output. Configuration, source, flashing and serial debug live in one place.

Download for Windows Request trial

✓ Local Keil C51 build✓ Project files stay local✓ STC + STM32 workspaces

MCU Pilot / STC workspace

STC15F2K60S2Keil C51 · connected

8 LEDs on P1.0–P1.7, active low, 200 ms per step

Generated from your config
Pins: P1.0–P1.7
Mode: push-pull
main.c written, build started…

✓ Build passed · 0 error · 0 warning

Windows portable build · Free downloadUnzip and run. JRE, workbench, chip library included. STC build uses your local Keil C51.

Download ZIP

2Production workspaces
STC / STM32

12Vendor entries
more planned

6+Debug tools
UART / Modbus / CRC

100%Project source
stays on your PC

WHY MCU PILOT

Embedded work should not be split across five tools

Part selection, Keil, CubeMX, flashing, serial and datasheets all live in different windows. MCU Pilot puts them in one project context.

AI suggests code, but cannot touch the project

You still find files, match pins and fix headers. Here AI reads and writes the current project, then verifies with a real build.

A new chip means a new toolchain

STC runs Keil C51; STM32 runs CubeMX and GCC. Vendor workspaces keep the same UI but isolate their rules.

Knowledge lives in PDFs and people

Upload official manuals and peripheral notes. AI retrieves them before writing code instead of guessing registers.

CAPABILITIES

One platform from source to flashing

Not a page of links — a shared project context across every step.

AI assists and edits code

Uses your pins, clock and workflow; on a failed build the compiler log goes back to AI for a fix.

C51

Local STC build

Calls your installed Keil C51, writes HEX into the project folder, syncs the chip header by part number.

Cloud STM32 build

Uploads a complete CubeMX project to a Worker, runs make with arm-none-eabi-gcc, returns log and firmware.

Knowledge retrieval

PDF, Word, Excel and Markdown are converted to text. Search is vendor-aware, with peripheral and full-library fallback.

UART

Serial & protocol tools

Serial monitor, RS485, Modbus RTU, CRC, HEX utilities and WebSocket debug — without leaving the platform.

Full project lifecycle

New, open, save, rename, delete, source editor with line numbers and a persistent project sidebar.

WORKFLOW

From idea to firmware in four steps

Every step shares the same project context, so nothing is exported and re-imported.

1
Configure
Pick vendor, part, package and clock. Fill the pin table and workflow.
2
Generate / edit
AI reads config and source, writes complete files, then triggers a build.
3
Build & locate
Line-by-line compiler log; jump back to source; let AI fix from the log.
4
Flash & run
STC serial downloader or STM32 ST-LINK, with progress and results in the UI.

SUPPORTED VENDORS

Multiple vendors, isolated workspaces

STC and STM32 are production-ready. More vendors are added as separate plugins, not shared rules.

STC / 8051STC15 · STC8 · local Keil

STM32CubeMX · cloud GCC

ESP32planned

GD32planned

Nuvotonplanned

Geehyplanned

HKplanned

HCplanned

MMplanned

CMSplanned

Renesas RAplanned

RP2040planned

Currently supported: STC8 / STC15 and STM32 Cortex-M. STC32 requires Keil C251 and is not available yet. Vendor logos are used for identification only.

DEBUG TOOLBOX

Debug the hardware without another install

Common protocol and data tools are built in.

Serial monitortext / HEX, timestamps, loop send

RS485half-duplex bus, A/B wiring notes

Modbus RTU03/04/06/16, automatic CRC16

Debug toolboxHEX, base, CRC, JSON, timestamp, bit ops

WebSocketconnect, send, receive, ping

CalculatorsLED, divider, RC, 555, resistor color code, SMD

FAQ

Common questions

What is MCU Pilot?

MCU Pilot is an AI-assisted Windows workbench for MCU development. It combines project configuration, AI code editing, building, flashing and serial debugging in one desktop application. STC 8051 and STM32 are supported today.

Does AI modify my project automatically?

Only when you allow it and give a clear instruction. It reads the configuration and source first, writes complete files, then runs a build. On failure, the compiler log is sent back for a fix.

Is STC built locally or in the cloud?

STC uses your local Keil C51 installation. STM32 uses a cloud Worker with arm-none-eabi-gcc for complete CubeMX projects.

Which chips are supported?

STC8 / STC15 and STM32 Cortex-M. STC32 needs Keil C251 and is not open yet. ESP32, GD32 and others are planned.

Do project files leave my PC?

STC project files stay local. Code or documents are sent only when you use AI, knowledge retrieval or STM32 cloud build.

How do I try it?

Download the Windows portable build from this page, or email 396870725@qq.com with your chip and use case.

GET STARTED

Try it on your next board

Free portable download. AI and cloud build require an account.