andnxor / sao-reference-designs Goto Github PK

The Readme.md file states:

DC Year: Use 0x1B for DC27

...however Defcon is occurring more than once per year (for example Defcon 1.0 is in Beijing in the year 2019.)

The flawed EPROM identification design seems to assume that all Defcon occurrences outside of Las Vegas are invalid? Let's fix this, but how?

Implementation

I'm about to implement your AT24C32 based design for DC 1.0 (Beijing), so it would be great to help me avoid hundreds of loss or a flawed identification config.

I propose that bytes 3 and 4 of the data section be used to signal the direction of the GPIO expander pins, so that badges with LED flashing code will not set inputs as outputs, and potentially short the badge via a button. Something simple where each bit represents an IO pin, and 1 represents output, 0 represents input.

Additionally, byte 5 could be used to signal the "advanced functionality" of the GPIO pins (namely, their input/output/NC status, if they are set as UART, or if they are part of SPI.

I apologize if this is the wrong place to submit suggestions for SAO1.69BIS.