Interrupt block with different exit?

[PaulMaker]

Hi all,

I'm troubleshooting an issue with an interrupt routine using RBC and Instant Interrupts where it's only detecting the first trigger and not any other following that.
In my interrupt routine, when the interrupt is detected, the flag is cleared and there's a choice (IF...Then) that can lead the code to one of 2 options using GOTO.
This means that after the interrupt, the code will not return to the point where the trigger was detected but somewhere else.
That being said, I replaced the @ INT_RETURN with a couple of GOTOs.

I found that replacing the @ INT_RETURN with GOTOs was causing the following triggers not being detected.
If i replace the GOTOs with the @ INT_RETURN, the interrupts will work always.

My question is...Is there a way i can do the jumps to where i want on the code and not being forced to return to where i was when the interrupt was triggered?

Thanks

[richard]

My question is...Is there a way i can do the jumps to where i want on the code and not being forced to return to where i was when the interrupt was triggered?

no , the isr must return to the point it was triggered from. if you try manipulating the stack to alter the return address without the proper skillset and understanding it will always result in unpredictable behavior.
if you structure your code to check frequently for a flag set from the isr that causes different processes to be invoked its possible to simulate the sort of result you are looking for

[PaulMaker]

Greetings Richard,

thanks for the reply.
I thought that the interrupt would still work (at least the detection part) even if we didn't want to go back to the code.
In that case i will need to do what you are suggesting and add periodic checks (in the normal code sequence) for a flag change done by the interrupts.

[Acetronics2]

Hi,

you can return wherever you want at the end of an interrupt stubb ...

I did it some years ago ... but Darrel did not like it at all !!! ( )

just have a look to the asm code generated and you will understand why and how !

the trick lies on the DEFINE INTHAND + RESUME _Label use ...

RESUME _Label gives

- bsf Intcon.7
- GOTO _Label

and _ Label is a PBP stubb ... where you want to jump to ...

for the moment, I have to dig out the program I wrote ...

Alain

[Ioannis]

Yes, if you really, really know what you are doing and spend hours on the asm code to double and triple check the code flow.

Ioannis

[richard]

it only works for and with ON INTERRUPT, and that's not a real interrupt

[Acetronics2]

it only works for and with ON INTERRUPT, and that's not a real interrupt

Hi, Richard

just open your Holy Manual @ asm interrupts page ...

as Ioannis states ... It's better to know what you are doing here ...

Our friend Paul was just asking if it was possible

Alain

[PaulMaker]

Hi guys,

dos this makes any sense to you?
I added a debugin line with timeout and jump label inside my interrupt block and this is causing the code not work as expected as well!

RBCinterrupts:

@ INT_DISABLE RBC_INT

debug "trigger detected...", 13,10

DEBUGIN 2000,JUMPOUT,[WAIT("MCU-"), DEC MOODCAP]

debug "debugin passed...", 13,10


RBIF=0
INTFLAG=1


DEBUG "returning...",13,10


@ INT_RETURN

Debugin jump block:

JUMPOUT:


DEBUG "fail debugin...",13,10

@ INT_RETURN