mos_8502 :verified: on Nostr: The keyboard protocol I envision, from the perspective of the Sentinel 65X CPU, is as ...

The keyboard protocol I envision, from the perspective of the Sentinel 65X CPU, is as follows:<li>Each time the latch line activates, reload the two-byte output buffer</li><li>Shift bits out MSB&nbsp;first</li><li>Bits shifted after 16 but without another latch will all be 1</li><li>The keyboard reports two bytes, which are always as follows, shfted low byte, high bit first.</li><code>; <br>; 76543210 First byte<br>; |+++++++- Keyboard scan code<br>; +-------- Ctrl key state (1: up; 0: down)<br>; <br>; 76543210 Second byte<br>; ||||++++- Signature: always 0011<br>; |||+----- Shift key state (1: up; 0: down)<br>; |+------- Option key state (1: up; 0: down)<br>; +-------- Command key state (1: up; 0: down)<br></code>

The modifier key state is captured at the time the latch activates.

Does this seem sane to you?