Instant Interrupts - Revisited

[Darrel Taylor]

What do you have in the main program?

Error [113] c:\pbp\pbppic14.lib 1141: Symbol not previously defined (INT_ENTRY)
Usually means there isn't an INT_LIST macro.

The files won't compile without it.

[DJEE]

As of yet I have not put your code into my main program. I was just trying to compile each on their own. If I understand you correctly, your code needs to be put of another program or it will not compile. Is that correct?

[Darrel Taylor]

That's correct!

[Darrel Taylor]

Alain,

Well, you may have noticed I didn't get the "GLOBAL" for INT_ENABLE/DISABLE put in the last version of DT_INTS-18.
It turns out that GLOBAL is a reserved word for MPASM. It's used with relocatable code.

I could have used GLBL or GLBAL I suppose, but somehow

@ INT_DISABLE GLBL

Seems even more cryptic than

GIE = 0

I still think it should be in there, as should PERIPHERAL, HIPRIORITY and LOWPRIORITY.

But I'm not sure what the best way is, AKA less confusing.

Any thoughts?
<br>

[Acetronics2]

Alain,

Well, you may have noticed I didn't get the "GLOBAL" for INT_ENABLE/DISABLE put in the last version of DT_INTS-18.
It turns out that GLOBAL is a reserved word for MPASM. It's used with relocatable code.

I could have used GLBL or GLBAL I suppose, but somehow

@ INT_DISABLE GLBL

Seems even more cryptic than

GIE = 0

I still think it should be in there, as should PERIPHERAL, HIPRIORITY and LOWPRIORITY.

But I'm not sure what the best way is, AKA less confusing.

Any thoughts?
<br>

Hi, Darrel

What about

@ G_INT_DISABLE and @ G_INT_ENABLE ??? ... would be simple enough. ... and it's just "ordinary" macros !!!

Remember the goal was only to use something simple to remind ( in other words: to use for datasheet non-lovers !!! )

To me, GIE = 0 is also the simpler ... But, as you've seen, nowadays nobody dares to read the datasheets !!!




The Tractor computer soft is just finished (!)... I had some precedence headaches ( particularly with // !!! ), and it was really difficult to see what was wrong ...

despite result was good for setting a flag, operation was wrong !!! ... and was no way to cancel that flag ...

Now, I must translate my comments to English ...

Regards
Alain

[srspinho]

Hello Darrel !

I´m using your Instat interrupts to work with TIMER1, TIMER2 and CCP1 with a 16F877 @ 4Mhz, like this :

ASM
;T0IF = TMR0IF
;T0IE = TMR0IE
INT_LIST macro ; IntSource, Label, Type, ResetFlag?
INT_Handler CCP1_INT, _Capture, PBP, yes
INT_Handler TMR1_INT, _Timer1, PBP, yes
INT_Handler TMR2_INT, _tick, PBP, yes
endm
INT_CREATE ; Cria a interrupção
ENDASM

Everything is working very, very well.

I´m doing a On-board computer for my small Opel Corsa, and this interrupts are just great !
Me and Sirvo (remember him ?) are doing almost the same on-board computer.

But now, I would like to implement 4 Buttons to my application (Start, Stop, Pause, Funcition Keys).

I´m trying to do that with the button statement without success / good results.

I read your sample (hello word for instant interrupts) but the INT_INT read just the RB0/INT right ?

Is that possible to use the Instant Interrupts to create/read, let´s say, 4 different buttons on PORTC ?

Tahank You very much !

bye


Sérgio Pinheiro

[Darrel Taylor]

Is that possible to use the Instant Interrupts to create/read, let´s say, 4 different buttons on PORTC ?

Yes, that's possible. But it would be a lot easier if you used RBC_INT "Port B change interrupts". It uses PORTB.4 thru PORTB.7

But if those pins aren't available, you could do something like this, which uses only 1 interrupt (INT_INT on Falling Edge), then the interrupt handler can read PORTC to figure out which one was pressed.


<br>