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 -- Access to Interrupts https://bugs.launchpad.net/bugs/579360 You received this bug notification because you are a member of GNUSim8085 developers, which is subscribed to gnusim8085. Status in gnusim8085: New 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! _______________________________________________ Mailing list: https://launchpad.net/~gnusim8085-devel Post to : [email protected] Unsubscribe : https://launchpad.net/~gnusim8085-devel More help : https://help.launchpad.net/ListHelp
