Hardware failures should be handled to not prevent board functionality

Currently, some hardware failures will cause boards to loop in initialization or when writing/reading in drivers. We currently do some basic hardware status logging, but this should be expanded.

- Create standard interface for representing status of hardware
- Determine which operations currently will loop indefinitely (or at least until the watchdog timer resets the board)
- Create sane status checks for all hardware modules that will report errors but not hinder overall board functionality
- Test hardware failures (possibly simulated) to validate that checks are working and that overall functionality is only reduced in the specific hardware that has failed