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

Back to Subject List

Old thread has been locked -- no new posts accepted in this thread
???
08/13/05 15:51
Read: times


 		 #99348 - tried but gives error
Responding to: ???'s previous message
Jan Waclawek said:
After you did the "housekeeping" with ports, LCD, whatever; do: clr ea ;disable all interrupt
call RetiSub ;release internal interrupt-in-progress flag
jmp 0 ;restart
;restart contains explicit reset of stack pointer,
;so no other stack housekeeping is needed
RetiSub:
reti


Thanks for the suggestion Jan, I have just tried your technique but when I run simulation, my assembler is coming up with following error message.
""A RET/RETI occured. This means your program attemped to return from an interrupt with a RET instruction or attempted to return from a subroutine with a RETI. Verify your subroutine and interrupt returns""
and above error does not come up straight away, infact it comes when i trigger external interrupt. I think it is not accepting when I ask the program to call RETISUB, which inturn contains RETI commmand. any suggestion?? any assistance here would be much appreciated.

Regards
James



List of 31 messages in thread
TopicAuthorDate
Interrupt question            01/01/70 00:00      
   Interrupt            01/01/70 00:00      
      then how?            01/01/70 00:00      
         One way is to            01/01/70 00:00      
            Little more description            01/01/70 00:00      
               Routine            01/01/70 00:00      
   interrupt exit            01/01/70 00:00      
      tried but gives error            01/01/70 00:00      
         assembler???            01/01/70 00:00      
            Assembler is Pinnacle            01/01/70 00:00      
               go to Pinnacle support            01/01/70 00:00      
               Asking for solutions            01/01/70 00:00      
      Now THAT was elegant!            01/01/70 00:00      
   use WDT to RESET the micro            01/01/70 00:00      
   some comments            01/01/70 00:00      
      Its like this            01/01/70 00:00      
         Emergency stop            01/01/70 00:00      
            I understand            01/01/70 00:00      
               If you REALLY want to do it            01/01/70 00:00      
                  optimizing            01/01/70 00:00      
                  possible troubles            01/01/70 00:00      
                     excellent point!            01/01/70 00:00      
                        This is not a solution            01/01/70 00:00      
                           Do it as you wish            01/01/70 00:00      
                              Makes sense            01/01/70 00:00      
                              the consensus last time was that the onl            01/01/70 00:00      
                                 WD reset - yes, why not            01/01/70 00:00      
                                    You say "no" and agree            01/01/70 00:00      
                                       no no = yes            01/01/70 00:00      
                                    Watchdog output            01/01/70 00:00      
                              Thanks, Done            01/01/70 00:00      

Back to Subject List