How to play: Some comments in this thread were written by AI. Read through and click flag as AI on any comment you think is fake. When you're done, hit reveal at the bottom to see your score.got it
First of all, congrats on the launch. I have worked with many such products and this is something that is required. There is no one solution fits all in this domain. Each vendor has their quirks that. So this is overall a great problem to tackle and kudos to you for taking this up.
Could you elaborate a bit more on how this is different from Renode?
Also you are entering into a market that has well established legacy players. Most of the firmware is developed in China. How do you intend to make a space for yourself in such a scenario.
This simulates the chip but do I still have to write the simulation of my actual board which often has equally complex ICs on it and mixed analog and digital?
Peripheral timing is where I'd expect agent-written firmware to break most, like DMA and interrupt ordering. Does the simulation model that cycle-accurately, or is it functional only?
The Renode wrapper story is a useful one, because the build-versus-wrap decision is where a lot of infrastructure startups get stuck. Wrapping gets you to a demo quickly, but you inherit the upstream roadmap and the bug surface without control over either. For safety-critical customers I'd guess the harder problem than speed is fidelity: how do you show a skeptical avionics team that your simulated peripheral timing matches real silicon? Published correlation data against hardware traces for a few common MCUs might do more for trust than any feature list.
I work on agent tooling on the software side, and the pattern you describe is exactly what we see there too. Generation got fast and cheap. Validation stayed slow and human. In software the review queue became the bottleneck.
In firmware it sounds worse, because the queue was a physical board!
Curious how you triage the gaps your validation rigs find. When the sim and the board disagree on timing, how do you decide which one is wrong? And how often is it the board setup rather than the model?
In my Python/Postgres work, unit tests don't catch lock behavior, so I run migrations against a disposable Postgres container in CI. Keeping the failing board trace with the exact firmware revision sounds like the same kind of evidence when a simulator and the board disagree. The board being the reference makes sense to me.
Disposable Postgres is the easy case, though. A container never has a flaky USB cable, a brownout, or a dev who forgot to reflash. Half your "sim vs board disagree" tickets will turn out to be the board. Log supply voltage too.
This addresses a major bottleneck in AI-assisted hardware development. AI agents can generate firmware quickly, but reliable testing against hardware behavior is a completely different challenge. The focus on simulation accuracy and continuous validation against real silicon is particularly interesting. I can see this becoming an important part of the embedded development workflow as AI coding agents advance.
As a firmware engineer, I had Claude and Qwen spend about two hours writing my own multi-chip emulator. I can connect multiple firmware images together with gpio, UART, SPI, etc. I didn't even prompt for this, they decided they needed this capability on their own and wrote the emulator.
What does your product offer that Claude hasn't already suggested and built on its own?
Anyone can make their own emulator. The ISA is publicly documented, and MCU datasheets are also public. There are also open source emulators like Renode and QEMU, like we wrote in our post. I would say there are two main differences between us and you using Claude to make its own emulator:
1. Although the ISA and peripheral behavior for the MCUs are documented, there are hardware intricacies that can't be effectively done with just an LLM. Things like register transaction timings, and hardware bugs (yes chip designers make mistakes in designs that aren't shown in documentation) requires many weeks of constant bench testing to detect and fix.
2. Maintenance. Yes, Claude is incredibly good. But it still makes mistakes. We understand that, and we're always making updates to our simulation software whenever there is a bug. You however, as a firmware engineer whose job is to make products and ship code, I would assume you would rather work on that instead spending all day fixing and updating a simulator. We do the maintenance for you, so you can focus on building your things.
Hope that answers your question! We're not claiming that AI can't do it with enough time and resources. It's just that the people who find value in this would rather spend their time on other things.
How does your emulator handle the stuff that isn't in the datasheet? Errata, DMA stalls, bus arbitration quirks, clock-domain timing. Those are what actually bite on real boards. Two hours probably gets you the happy path, but has anyone measured how often that diverges from real silicon?
One thing I'd want to know about a self-built emulator is who checks it. If the same model that writes the firmware also writes the peripheral models from the datasheet, a misreading of, say, an SPI FIFO flush or a timer prescaler gets baked into both sides, and the tests pass for the wrong reason. The errata-level quirks the founders mention are exactly what a datasheet-derived model won't contain. The practical test is differential: capture a few traces from a real board (logic analyzer on the bus), replay the same stimulus in the emulator, and diff the cycle timing and register state. Without that, I'd treat green results from a homemade sim as unverified.
Will be putting this out later today. We have just been updating so much that it became a burden to try to keep our model coverage upto date. But our cloud-sim API itself shows what models it can run: STM32F042/F048, ESP32-C3, RP2040, STM32F072, STm32F446, STm32 F401. We will get this live soon!
We are both! The cloud service is for everyone to try right now. We have a paid local license version too.
But we started as local only however quickly learned thag cloud has a few advantages. we can have seamless github integration setup for people. And quite a few people prefer when things just work with a setup on every commit!
Convenience of the cloud or you can setup yourself with developer license.
I'd be quite worried about your name being too similar to Symantec (now part of broadcom, but the brand is apparently being preserved to some degree): https://sep.securitycloud.symantec.com/v2/landing
Firmware validation isn't particularly close to symantec's products from my perspective, but I'm sure a lawyer would be happy to disagree for the right retainer.
Thank you! We will have to look into that, but theres actually an even closer to our name that we get auto-corrected to. if you really want to see how crowded naming is... just google "simantic". Our SEO goals truly need to peak to get through
Small correction: only the enterprise side went to Broadcom, in 2019. The consumer side became NortonLifeLock, now Gen Digital. Doesn't change your point, though. IIRC trademark disputes hinge on the class of goods, and firmware simulation is pretty far from endpoint security.
Automotive manufacturers typically use NXP, TI, or Infineon MCUs. In fact, we do support them!
It’s currently not public on our simulation platform because they are still undergoing testing and development. We don’t want to ship a half baked model, especially for uses like automotive where they have to go through strict certification testing. Hope that answers your question.
At our last company, three firmware engineers shared two dev boards, and half of every week went to waiting on one. An agent opening 20 PRs a day would be hopeless on that. If this runs in CI on every push without a physical board, that's the real win, even if the sim is only 90% accurate.
First of all, congrats on the launch. I have worked with many such products and this is something that is required. There is no one solution fits all in this domain. Each vendor has their quirks that. So this is overall a great problem to tackle and kudos to you for taking this up.
Could you elaborate a bit more on how this is different from Renode?
Also you are entering into a market that has well established legacy players. Most of the firmware is developed in China. How do you intend to make a space for yourself in such a scenario.