| ??? 06/22/01 07:43 Read: times |
#12712 - RE: Return vector for interrupts |
Sorry Erik, but I disagree with you on the interrupt disable issue.
It is no problem that the code is interrupted by another interrupt routine. The stack won't be damaged by it. As an interrupt occurs it pushes the return address on the stack among with some other things. When it finishes all these changes are POPed from the stack again, leaving the stack as it was before the code was interrupted. So everything that WAS on the stack before, will BE on the stack unchanged afterwards. You only have to disable interrupts if you use the POP POP PUSH PUSH sequence, that physically changes the stack pointer. The other methods don't change it. Happy programming |
| Topic | Author | Date |
| Return vector for interrupts | 01/01/70 00:00 | |
| RE: Return vector for interrupts | 01/01/70 00:00 | |
| RE: Return vector for interrupts | 01/01/70 00:00 | |
| RE: Return vector for interrupts | 01/01/70 00:00 | |
| RE: Return vector for interrupts | 01/01/70 00:00 | |
| RE: Return vector for interrupts | 01/01/70 00:00 | |
| RE: Return vector for interrupts | 01/01/70 00:00 | |
| RE: Return vector for interrupts | 01/01/70 00:00 | |
| RE: Return vector for interrupts | 01/01/70 00:00 | |
| RE: Return vector for interrupts | 01/01/70 00:00 | |
| RE: Return vector for interrupts | 01/01/70 00:00 | |
| RE: Return vector for interrupts | 01/01/70 00:00 | |
| RE: Return vector for interrupts | 01/01/70 00:00 | |
RE: Return vector for interrupts | 01/01/70 00:00 |



