Events

Brain hurt.

Selectable Events

Each cog can track up to four selectable Pin, LUT, or Lock(TODO link?) events, SE1 through SE4. The event to be monitored is selected by using the SETSEx instruction(s).

Setup Instructions

SETSEx selects the event to be monitored by the corrosponding SEx event flag according to Destination. TODO words

Pin Events

• %001_PPPPPP = IN bit of pin %PPPPPP rises
• %010_PPPPPP = IN bit of pin %PPPPPP falls
• %011_PPPPPP = IN bit of pin %PPPPPP changes
• %10x_PPPPPP = IN bit of pin %PPPPPP is low
• %11x_PPPPPP = IN bit of pin %PPPPPP is high

LUT Events

You can select $1FC..$1FF for the LUT read or write address event sensitivity with bits AA. (TODO less confusing wording)

• %000_00_00AA = this cog reads LUT address %1_1111_11AA
• %000_00_01AA = this cog writes LUT address %1_1111_11AA
• %000_00_10AA = odd/even companion cog reads LUT address %1_1111_11AA
• %000_00_11AA = odd/even companion cog writes LUT address %1_1111_11AA

Lock Events

• %000_01_LLLL = hub lock %LLLL rises
• %000_10_LLLL = hub lock %LLLL falls
• %000_11_LLLL = hub lock %LLLL changes

ADDCT1, ADDCT2, or ADDCT3 set the hidden CT1, CT2, or CT3 event trigger register (respectively) to the value of Destination + Source. The result is also written to Destination.

The respective CTx event flag is set when the trigger register matches the bottom 32 bits of the global CT counter. ADDCTx clears this flag again.

TODO: More detail

Set pin pattern for 'Pattern match/mismatch' event. C flag selects INA/INB, Z flag selects match/mismatch, Destination provides mask value, Source provides match value.

TODO: More detail

Attention

COGATN strobes the attention signal for one or more cogs. Destination bit positions 7:0 represent cogs 7 through 0; high (1) bits indicate the cog(s) to signal. The receiving cog(s) will have their ATN event flag set, and can use any of the attention monitor instructions (JATN, JNATN, POLLATN, WAITATN) or interrupts to respond and clear the flag.

        COGATN #%00100010

In the intended use case, the cog receiving an attention request knows which other cog is strobing it and how to respond. In cases where multiple cogs may request the attention of a single cog, some messaging structure may need to be implemented in Hub RAM to differentiate requests. (TODO: Perhaps mention lock SEs?)

Poll Instructions

Wait Instructions