Y-Box has several operational and error states that are worth indicating. It has two LEDs, a red one attached to the CC2543 (RF) and a green one attached to the KL26 (USB), to do this.
How about the following scheme ? http://downloads.qi-hardware.com/people/werner/anelok/tmp/ybox-leds.pdf The normal use sequence would be: - unplugged: no lights - plug into PC: red LED goes on - after about 1 second USB enumeration finishes and the green LED goes on as well - Y-Box waits 1-2 seconds for DFU (firmware updates). If it doesn't see any requests, it turns off both LEDs and starts RF dongle operation. - on RF activity, the red LED briefly flashes. If the rfkill switch is set, i.e., if the Y-Box is used only to connect Anelok to some USB device, the CC2543 is completely shut down and the KL26 cannot communicate over USB (because it needs the CC2543 as clock source. Of course, even if it could talk on USB, it wouldn't have much to say ...) In this case, the green LED would stay on until rfkill is disabled (if ever). If we're plugged into a power-only USB outlet, the PC is dead, or if it simply doesn't want to speak with the Y-Box, then the red LED would stay on to indicate that enumeration hasn't happened (yet). Last but not least, there are a number of abnormal conditions. All the panics are anomalies detected by software. "Firmware not responding" may indicate a hardware issue or simply missing/broken firmware in one of the two MCUs (but not in both). If the CC2543 doesn't even respond to debug commands (and rfkill is off), then there's something wrong with the hardware. Does this sounds reasonable ? In Anelok, I don't plan to give the CC2543 its own LED but the KL25/26 can simply indicate things on the display. - Werner _______________________________________________ Qi Hardware Discussion List Mail to list (members only): [email protected] Subscribe or Unsubscribe: http://lists.en.qi-hardware.com/mailman/listinfo/discussion
