Access to Interrupts

Bug #579360 reported by Onkar Shinde
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnusim8085
New
Wishlist
Unassigned

Bug Description

the simulator already provides access to memory, I/O ports and the stack, however for programming with interrupts, it would also be useful to be able to easily access interrupts - so that interrupts can be easily triggered manually, or possibly be configured to occur regularly, using a configurable timeout/delay.

This would help emulating a basic timer for example, where we can configure gnusim8085 to trigger a certain interrupt every couple of milliseconds (or at a rate of x hz/khz), which in turn could be used by a corresponding interrupt handler to implement a timing routine.

Having an option to dynamically trigger/modify interrupts at runtime would also be very useful, too!

Revision history for this message
Bug Importer (bug-importer) wrote :

also, we have to keep in mind that there's a distinction between software/hardware interrupts and interrupt priority.

Revision history for this message
Bug Importer (bug-importer) wrote :
Revision history for this message
Bug Importer (bug-importer) wrote :

you cannot really do much interrupt programming without the ORG directive being supported in the first place

Revision history for this message
Bug Importer (bug-importer) wrote :

Implementing support for the ORG directive is already considered with pretty high priority (7/10), see: http://sourceforge.net/tracker/?func=detail&aid=1799444&group_id=86462&atid=579702

Revision history for this message
The Escapist (wisd00m) wrote :

having this would be very useful for prototyping purposes.
I would in fact suggest supporting optional interrupt routines that can handle I/O, for example triggering a custom GNUSim8085 interrupt could be used for writing strings to the log window or doing other simple output tasks. This could be tremendously useful for troubleshooting purposes. Similarly, having a way to ask the user for input data just by triggering an IRQ would be powerful. For example, this would make it to execute an interrupt for getting or showing data from the user.

This could be a good workaround to emulate features that are currently provided by an EEPROM or BIOS

Revision history for this message
The Escapist (wisd00m) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.