Stimulus driven interrupts?

[jmaggio14]

In this Oberon-1 paper (http://norayr.am/papers/WirthTasksVersusThreads.pdf) from 1996, Wirth discusses a method of "real-time tasks". (Page 10). In which I believe interrupt handlers installed with Kernel.Instal(Handler, N) are triggered when a device or buffer is updated?

I see that Kernel.Install still exists in the RISC5 source. Can this method still be used for "real-time tasks" in which a procedure is run when an external stimulus changes? So far all the interrupt examples I've seen make use of interrupts triggered periodically by the millisecond timer, but I'm a little out of my depth here so it's very possible I missed something

My end goal is to trigger an interrupt (from firmware or otherwise) without having to wait for the millisecond timer

[cfbsoftware]

Oberon's interrupt capabilities are part of Project Oberon and the RISC5 design - they are not peculiar to Astrobe. Unfortunately we have not had any experience in what you are attempting to do. However, I recommend that you check out this website produced by gray, another Astrobe user and frequent contributor to this forum:

https://oberon-rts.org/basics/on-interrupts/

Alternatively, try asking your question on the ETH Oberon Mailing list.

[cfbsoftware]

For anybody who is interested this discussion was continued on the ETH Oberon Mailing list:

http://lists.inf.ethz.ch/pipermail/oberon/2021/015803.html