Working close to hardware is cool and all, but frequently, it is necessary to simulate/test some code intended for hardware while offline/without hardware/etc. A common way to do this is to rig the code with multiple interfaces/abstractions/mocks etc, that can substitute the hardware at the last possible step. But of course, no matter how low you insert your new test classes, there is always the chance that a problem happens in hardware and not during testing.
Continue reading "sparsediff: diff tool for linux sparse files(great for simulating embedded hardware!)"sparsediff: diff tool for linux sparse files(great for simulating embedded hardware!)
I shortly describe a testing mechanism I use to simulate memory mapped IO, and then talk about a cool tool I made