2015-12-22 19:11:27 UTC
Based on some reading here
it appears that "bus-centric" peek-poke utilities like the I2C Tool violate the functional partition of the OS, but they are, of course, an essential tool when bringing up new hardware. First rule of every design: start simple, and work upward from there. For example, my goal right now is to simply validate the hardware design by reading and writing data to specific registers. Next step would be to actually write the proper device drivers.
The apps/system/i2c tool should work for the initial testing of the I2C bus, but there doesn't happen to be anything similar for SPI (correct me if I'm wrong).
Assuming I can build something that will mimic the I2C Tool, would you consider accepting it into the apps repository? I just want to know whether I should attempt to polish the code or just treat it as a one-off.