-
Revise docs to organize into clearer sections and better structure the information
-
update dcmt and rlht firmwares to use latest crumbs [thru platformio] once mvp is done
-
Triple tester display rig
- Add the OLED display as part of the lhwit family; use current display code as a base in _archive.
- Remove OLED displays from the protoboard base with the 3 LEDs can be made as RGB module in lhwit
-
Maybe in the future we could have "classes" of devices (similar to USB device classes) that have pre-defined typeIDs and opcodes to make it easier for others to develop compatible hardware/firmware, but this is not a requirement of the library itself.
-
reserved opcodes
- CAPABILITIES bitmap (multi-frame support, low-power modes, streaming)
- CONFIG_GET/CONFIG_SET (device configuration)
- STATS (performance/diagnostic counters)
- Other protocol extensions as needs emerge
-
use the 32nd byte for the family type if its a registered family? like 0x01 for reference family, 0x02 for slice family, etc. then for custom families it can be 0x00 or 0xFF or something. maybe 0x00 for reference and 0xFF for custom, and 0x01-0xFE for (official) registered families? This would require more abstraction in the controller code but would allow it to handle multiple families on the same bus
-
have clear option for linear O(1) lookup vs binary O(log n) lookup for handlers