HN Simulatornew | past | comments | lists | submit | enough_ahnaf's commentslogin

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.


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, 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.


Amazing to learn on this thread. Does anyone know what they would use to simulate ECU problems like this? Im a firmware engineer in the industry and kind of seeing a problem like this and this thread really opened up my eye to what it looks like under the layers of Media in F1


I looked it up yesterday and they have the ECU in the loop for the driving simulators (the ones the drivers practice with and that are used for checking mechanical changes). But these use empirical models, they can't simulate everything. You would have to get a lot right in the models and top of that know where to test edge cases and then simulate all inputs correctly for those. You can surely input yesterday's weather conditions but whatever model is there might not predict an output that goes to the next model and so on..

I'm sure there's also all kinds of other HIL testing but it comes down to thinking about all conditions and having models and tests that are realistic enough for those conditions. It's impossible to have perfect coverage.

It's probably kind of lucky that enough cars were impacted so that the issue was revealed instead of having a just a few cars knocked out of the race.


With something safety-critical like an ECU, I'd be surprised if they left formal proof out of their software design and testing. This would make unexpected hardware behaviour much more likely imo. I guess I'd get around it by setting up automated hardware-in-the-loop simulators for testing every possible environment and input. Surely the cost would be worth it for F1 as a whole.

At a startup I worked at, we jerry-rigged Pi 5's with commercial of-the-shelf environmental sim software to achieve this. Very cost effective, lol.


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

Search: