I tried this a while back and found it ended up being easier to just give the firmware agent a dedicated machine, there’s so much low-level stuff you want access to for iterating on firmware, and the docker layers kept confusing the agents when they were debugging faults, crashes, brownouts etc.<p>Combining a dedicated small machine with a USB hub that supports per-port power cycling lets the agent iterate and un-wedge stuff with no human intervention for very long (days) periods. Obviously any <i>software</i> produced that way is unusable, but it’s <i>incredible</i> for debugging. Agent gets a programmable oscilloscope, power-cycling, and peripherals (also power-cycleable) emulating the various things our product talks to in the wild.<p>TL;DR I found the docker layers just caused confusion for the agent and giving her an old laptop was way simpler and much more powerful
This seems the natural evolution of what used to be:<p>1. A laptop with the development environment (DOS or Windows) kept in a box to use for updates / fixes<p>2. A VM on a NAS to use when a firmware in maintenance needs a fix<p>With more embedded tooling available on Linux, a docker image becames a natural choice.
Now we need a full virtual chip in docker to simulate it. That would be incredible.
Is this what you want? <a href="https://docs.espressif.com/projects/esp-idf/en/stable/esp32/api-guides/tools/qemu.html" rel="nofollow">https://docs.espressif.com/projects/esp-idf/en/stable/esp32/...</a><p>Also:<p>- <a href="https://wokwi.com/" rel="nofollow">https://wokwi.com/</a><p>- <a href="https://github.com/davidmonterocrespo24/velxio" rel="nofollow">https://github.com/davidmonterocrespo24/velxio</a>
Like this?
<a href="https://renode.io/" rel="nofollow">https://renode.io/</a>
It's annoying enough if "small" projects can't refuse to use LLMs to write their documentation, but large companies? There's really no excuse to use LLM garbage to write stuff intended for human consumption.<p>Do better.
[dead]