Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
hardware:interrupts [2016/06/05 15:12] ex_writer [Example: VERBL and HORCB] |
hardware:interrupts [2016/06/11 21:50] ex_writer [Screen Interrupts] |
||
|---|---|---|---|
| Line 39: | Line 39: | ||
| ===== User-Defined Interrupts ===== | ===== User-Defined Interrupts ===== | ||
| - | The Bally Arcade also allows the user to enable and respond to two software-controlled interrupts: screen interrupts at designated scanlines and interrupts for tracking [[glossary#l|light pen]] input. | + | The Bally Arcade also allows the user to enable and respond to two software-controlled interrupts: screen interrupts at designated scanlines and interrupts for tracking [[:glossary#l|light pen]] input. |
| ==== Screen Interrupts ==== | ==== Screen Interrupts ==== | ||
| Line 48: | Line 48: | ||
| * Enable screen interrupts and set its mode in INMOD ($E) | * Enable screen interrupts and set its mode in INMOD ($E) | ||
| - | * Designate the target interrupt scanline in INLIN ($F) | + | * Designate the target interrupt scanline in INLIN ($F)+++ |
| * Set the interrupt handler address... | * Set the interrupt handler address... | ||
| * low byte in INFBK ($D) | * low byte in INFBK ($D) | ||
| Line 55: | Line 55: | ||
| * Enable interrupts with the EI opcode | * Enable interrupts with the EI opcode | ||
| + | +++<wrap alert>necessary only with multiple interrupts? screen interrupts seem to function fine when INLIN isn't set </wrap> | ||
| === Interrupt Enable and Mode (INMOD) === | === Interrupt Enable and Mode (INMOD) === | ||
| Line 113: | Line 114: | ||
| ===== Automatic Interrupts (ACTINT) ===== | ===== Automatic Interrupts (ACTINT) ===== | ||
| - | <WRAP alert>To be written...</WRAP> | + | <WRAP todo>To be written...</WRAP> |
| ===== Screen Interrupt Examples ===== | ===== Screen Interrupt Examples ===== | ||
