Hacker Newsnew | past | comments | ask | show | jobs | submit | enough_ahnaf's commentslogin

We actually catch DMA, interrupt ordering, peripheral config mistakes the most! Because all instructions and relative timing is preserved, pre-emption and other bugs that live in the driver level can be caught with Pyrite. We are cycle approximate, not accurate. Our simulation is from the reverse engineered data we collect from our labs.

haha you just reminded me of a time when AI forgot about the python GIL when doing pytest wrapped around my custom USB endpoint C++ code to talk to my firmware and it completely broke all my host USB because I didn't know how locks would affect my code. this was opus 4.6 though so I forgive em.


haha, now wouldnt want the world to have yet another PLC simulation software would we...


Yes I totally agree claude can write some damn good firmware! but at an enterprise development team scale for testing needs simulation. It has and always will for any critical embedded system. I think its the other way around that the viability will only get greater. Only this year did people start trusting LLMs with firmware so the bet based on what we saw at industry, the better the AI the better you want the simulation it can use for your development.

The other contributing cause is the actual lack of silicon in supply and we are seeing it especially for the automotive industry, which is only spiking demand for better simulations to unblock teams.

If you want to ship with agents at scale you need a good testing pipeline now more than ever. We don't replace the bench setup test, we look to enhance what you bring to it.

But that doesn't take away from the fact that, yes you could just let your LLM continuously loop on some hardware setup, rinse and repeat for weeks. If you have the hardware and the time to spare.


But what if (due to the availability of AI) it becomes more common that hardware vendors provide simulation models with their hardware? That's the direction I'm hoping we will move in. And if it doesn't happen, perhaps FOSS enthusiasts will provide these models ...


I would say that is true, that hardware vendors should and can provide simulation models with their hardware. We know they can because they rely entirely on simulation to test their chips before tapeout.

We even tried to work with chip vendors (won't name here but they are 2 out of the 10 biggest microcontroller designers), but in reality, them providing their own simulation is a little bit counterintuitive for them.

They make their money on selling chips, and their thought is that providing a simulator would make it so that people buy less chips. If they do provide a simulator, it would be hella expensive, like through the Synopsys Virtualizer, which costs $500k per seat.

For RISC-V and open-source MCUs, they are easy to simulate. Just run the RTL through something like Verilator, and you have a fully working simulation.

We do hope that chip companies eventually do exactly that. We are also firmware engineers, and our goal is to make the simulation software we needed while working in the field. Either we make it, or they make it. Win-win in my opinion.


Certainly a win if someone makes it, but I think that with the help of AI, soon anyone with a datasheet can make those simulation models. And even if it's not that simple, open source folks will do it.


dare I say it has already advanced!


Unfortunately yes, we are limited in the mixed signal domain right now, that is by design. you would need to interact with ICs at a data level or pin level transactions. This would be digital levels nothing analog.

This was kind of part of our original offerings to have a firmware mixed signal co-simulation. Run firmware--> see Spice level simulations happen. But this was a case where the speed to fidelity trade off really didnt make sense... yet. We were spreading ourselves thin on a long horizon project with nothing to show for it during the YC term.

We will come to revisit this problem for sure as we have heard many of our customers ask similiar question for analog IC purposes. Just have to take it one step at a time.


one spot where pin-level leaks is the ADC. tons of "firmware bugs" are really a big divider that can't recharge the sample cap in time, so readings come out low or depend on the previous channel. even just modeling source resistance vs sampling time would catch a lot of that


The simulation itself is deterministic. inputs in, same outputs out. But our data collection for the hardware behaviour does naturally have a few things that are probalistic, we don't do any ML based modelling. No really fast LLM under the hood unfortunately


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


Having the same issue. I have stopped Googling it, since i just start to wonder if its better to just rebrand.


we have thought about it, but its a name we came up ourselves, fits the bill and we have the domain for it. Can't ask for much more. its pretty rare for google to be our inbound and when we get to that point we would probably overtake that in SEO anyway


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!


Thank you, and for sure market is very fragmented. Which is exactly why we are starting small and modelling deep with stm32 as our workhorse here. The quirks we are finding them everyday! I have seen mcu controller behaviour from neither errata nor datasheet and thats the beauty of field testing.

I think our biggest difference to renode is the silicon validation and our commitment to keeping our simulation honest. I have struggled to find simulators that people actually put the measured differences and that is the direction we will go. We haven’t put our silicon validation benchmarks public yet but we will in the coming months!

As for legacy players, they don’t fill the niche enough. Thats why we exist and as a startup can fill this niche for the people that need it, whether its china, or anywhere else.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: