Handling failure-to-boot

[ryan-summers]

When booster is at the manufacturing stage, there may be a number of reasons why booting may fail, such as manufacturing defects or loose connections.

In these cases, the firmware will enter a cyclic boot state, constantly failing over when trying to communicate with a component that may not be connected. In these cases, it's difficult for the operator to understand why the boot process is not successful.

We should assess changes to the boot process to aid in debugging why the device may be failing to boot.

Discussion

At this phase in the boot processes, the USB interface is not initialized, so we cannot print information over the console. It was proposed that we can somehow use the channel LEDs to indicate information to the user as well, such as setting them all on and not entering a cycling boot process if the failure occurs during setup.

[ryan-summers]

One example of this issue is somewhat described in #242, although that is not specifically related to failure-to-boot.