Launching today
Fauvido Technologies
Hardware emulation for faster testing of your firmware
6 followers
Hardware emulation for faster testing of your firmware
6 followers
Fauvido Technologies builds the testing layer for physical computing. Our product Macrohill lets firmware teams test against a live emulation of their hardware: inject faults, author test cases with AI or by hand, run profilers (Memory, CPU in terms of instructions), and replay recorded sensor data. We also provide a CLI that can intergrate into your CI/CD pipeline and make E2E testing on every commit, on the emulated board, possible.
A CLI integration is great, but how about adding a web dashboard that visualizes profiling results across test runs. Would make it way easier for teams to spot regressions in CPU or memory usage at a glance instead of digging through CI logs.
@kucuksahal10675 Hello! Do you mean profiling report across different firmware iterations? As in, you change the code and you want to see if you are utilizing the CPU better? If so, then yeah, this makes sense, this will get to that stage. Thanks for the input
A CLI that plugs into CI is great, but can you add a way to export test runs as a standardized report like JUnit XML or SARIF. That would make the results drop straight into GitHub Actions or Jenkins without extra glue code and let devs see firmware regressions right next to their other test failures.
@kumsalmnyj Hey! That's actually pretty smart and I didn't think about it. I am not sure what kind of reports do teams make for these things, so I'll do some research. Thanks for the valuable input!
One thing that would really help our team: a way to share and reuse custom fault injection profiles across projects, maybe through a simple registry or versioned config files. Right now we keep recreating the same fault scenarios for each board family, and it gets messy fast.
@rdvantunzwcz1 Hello! That makes sense. I am yet to develop this to a point where teams can share stuff, it's more catered towards individuals right now. In the future however, I will be letting teams handle their testing profiles in collab.
One thing that would really help teams like ours is a built-in diff viewer for regression tests. When a CI run fails, being able to visually compare the new firmware trace against a known-good golden run side by side would save so much debugging time. Even better if it could highlight exactly which memory addresses or instruction paths diverged.
@adurkaya36180 Hey! I wanted to add a golden rule comparision, but I wasn't sure how people exactly wanted that to look like. It'll take some iterations to get right I suppose so thanks for your input!
finally a tool that gets how painful firmware testing really is. the fault injection on a live emulation alone is worth checking out.
@ykselhzrer9n0b Hey, thanks man! Firmware testing indeed is painful.