Email: Password: Remember Me | Create Account (Free)

Back to Subject List

Old thread has been locked -- no new posts accepted in this thread
???
02/12/03 21:43
Read: times


 
#38924 - RE: SPACE MEMORY OVERLAP
Responding to: ???'s previous message
For those interested in an answer here.....this problem looks like Kobi had set up his program to start from an address at or below 0x25. At the same time he must have given the "interrupt" attribute to some subroutine that was intended as an interrupt service routine. The interrupt number given for that routine specified a correspoding interrupt vector at 0x23. The compiler/linker automatically made the interrupt vector at 0x23 which of course conflicted with other code already located at that same address.

The Fix: Arrange to start the program at an address slightly higher than the last interrupt vector location.

Note that this problem may also have been caused by having two source file subroutines both tagged with the same interrupt numbers thus causing the compiler/linker to produce two interrupt vectors at the same locations. Once again a conflict of who gets to live at 0x23.

The Fix: Make sure to only declare one interrupt service routine for a given interrupt number within a given project.

Michael Karas


List of 3 messages in thread
TopicAuthorDate
SPACE MEMORY OVERLAP            01/01/70 00:00      
   RE: SPACE MEMORY OVERLAP            01/01/70 00:00      
   RE: SPACE MEMORY OVERLAP            01/01/70 00:00      

Back to Subject List