This page (revision-2) was last changed on 03-Feb-2023 15:21 by Florian Dingler 

This page was created on 02-Apr-2019 13:41 by Florian Dingler

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
2 03-Feb-2023 15:21 1 KB Florian Dingler to previous
1 02-Apr-2019 13:41 1 KB Florian Dingler to last

Page References

Incoming links Outgoing links
VVBLKD
VVBLKD

Version management

Difference between version and

At line 6 changed one line
These two VBLANK vectors point to interrupt routines that occur at the beginning of the VBLANK time interval. The stage one VBLANK routine is executed; then location [CRITIC] 66/$42 is tested for the time-critical nature of the interrupt and, if a critical code section has been interrupted, the stage two VBLANK routine is not executed with a JMP made through the immediate vector [VVBLKI]. If not critical, the deferred interrupt VVBLKD is used. Normally the VBLANK interrupt bits are enabled (BIT 6 at location [NMIEN] 54286/$D40E is set to one). To disable them, clear BIT 6 (set to zero).
These two VBLANK vectors point to interrupt routines that occur at the beginning of the VBLANK time interval. The stage one VBLANK routine is executed; then location 66 ($42) is tested for the time-critical nature of the interrupt and, if a critical code section has been interrupted, the stage two VBLANK routine is not executed with a JMP made through the immediate vector [VVBLKI]. If not critical, the deferred interrupt VVBLKD is used. Normally the VBLANK interrupt bits are enabled (BIT 6 at location 54286/$D40E is set to one). To disable them, clear BIT 6 (set to zero).
At line 8 changed one line
The normal seguence for VBLANK interrupt events is: after the OS test, JMP to the user immediate VBLANK interrupt routine through the vector [VVBLKI] at 546,547, then through [SYSVBV] at 58463/$E45F. This is directed by the OS through the VBLANK interrupt service routine at 59345/$E7D1 and then on to the user-deferred VBLANK interrupt routine vectored at 548,549. it then exits the VBLANK interrupt routine through [XITVBV] 58466/$E462 and an RTI instruction.
The normal seguence for VBLANK interrupt events is: after the OS test, JMP to the user immediate VBLANK interrupt routine through the vector [VVBKLI] at 546, 547, then through [SYSVBV] at 58463/$E45F. This is directed by the OS through the VBLANK interrupt service routine at 59345/$E7D1 and then on to the user-deferred VBLANK interrupt routine vectored at 548, 549. it then exits the VBLANK interrupt routine through 58466/$E462 and an RTI instruction.
At line 10 changed one line
If you are changing the VBLANK vectors during the interrupt routine, use the [SETVBV] routine at 58460/$E45C. An immediate VBI has about 3.800 machine cycles of time to use, a deferred VBI has about 20.000 cycles. Since many of these cycles are executed while the electron beam is being drawn, it is suggested that you do not execute graphics routines in deferred VBI's.
If you are changing the VBLANK vectors during the interrupt routine, use the SETVBV routine at 58460/$E45C. An immediate VBI has about 3800 macine cycles of time to use a deferred VBI has about 20,000 cycles. Since many of these cycles are executed while the electron beam is being drawn, it is suggested that you do not execute graphics routines in deferred VBI's. See the table of VBLANK processes at the end of the map area.
If you create your own VBI's, terminate an immediate VBI with a JMP to 58463/$E45F and a deferred VBI with a JMP to 58466/$E462. To bypass the OS VBI routine at 59345/$E7D1 entirely, terminate your immediate VBI with a JMP to 58466/$E462.
At line 12 removed 2 lines
If you create your own VBI's, terminate an immediate VBI with a JMP to [SYSVBV] 58463/$E45F and a deferred VBI with a JMP to [XITVBV] 58466/$E462. To bypass the OS VBI routine [SYSVBL] at 59345/$E7D1 entirely, terminate your immediate VBI with a JMP to [XITVBV] 58466/$E462.
This page (revision-2) was last changed on 03-Feb-2023 15:21 by Florian Dingler  Top