From datasheet working firmware

Sricharan Srikrishna — Wed, 26 Aug 2026 10:18:23 +0000

I’m building HardcoreAI because I kept seeing the same problem in embedded development:

You have the board.
You have a 300–1000 page datasheet.
You know what you want the firmware to do.

But actually translating those registers, peripherals, timing requirements and errata into working firmware can take days — and debugging the wrong assumption can cost weeks.

So we built HardcoreAI — an agentic firmware intelligence platform that researches the hardware before generating firmware.

The workflow:

→ Upload/select your hardware
→ Research Mode — AI analyzes the datasheet and hardware documentation
→ Ask questions about registers, peripherals and configuration
→ Generate firmware
→ Build, test and iterate

We’re opening it up for developers to try.

If you work with STM32, ESP32, Arduino, PlatformIO or embedded systems, I’d genuinely love your feedback.

Try it here: https://www.hardcoreai.in/

What’s the most annoying

I lost 4 days to a firmware bug that cost twelve rupees to fix. So I built HardcoreAI.

Sricharan Srikrishna — Thu, 20 Aug 2026 17:47:11 +0000

Four days debugging a hard fault on an STM32F4.

Root cause: UART clock not enabled before peripheral init. Documented on page 247 of the reference manual. Fix took 30 seconds once I found it.

That same week, the software engineer next to me shipped three features with Copilot. Same hours. His tools understood his code. Mine understood nothing about my chip.

I tried every AI tool available. All of them hallucinated register addresses. In embedded systems, a wrong address does not produce a catchable exception — it produces a hard fault, a silent reset, or a bricked board.

The problem is not AI capability. No AI tool has actually read your datasheet.

So I built HardcoreAI

The workflow is different from asking an AI to write embedded C:

Research first. Generate second. Flash last.

Select your board — STM32F1/F4/H7, ESP32, 1,500+ via PlatformIO
Feed it your reference manual and errata before generating anything
Get firmware where every line cites the exact page and register it came from
Build, flash via OpenOCD, test
On fault — reads CFSR, HFSR, BFAR, MMFAR, identifies the violation, corrects, reflashes automatically

The fault decoder is fully deterministic — 500+ hand-written rules, zero LLM in that path. We caught a clock tree conflict on STM32H7 where the grounding layer returned correct output but the fault decoder flagged it as physically impossible on that silicon revision. Grounding alone would not have caught it.

Try it free

First complete project is free. No signup. No credit card. No waitlist.

👉 https://www.hardcoreai.in/

DEV Community: Sricharan Srikrishna

From datasheet working firmware

I lost 4 days to a firmware bug that cost twelve rupees to fix. So I built HardcoreAI.