Instant Interrupts - Revisited

[Acetronics2]

Hi, Dave and Ioannis

YES ...

I really think it's URGENT to wait a little !!!

BUT it seems the problem only Occurs with DT 18 Instant Interrupts ...

Alain

[mackrackit]

So other includes with ASM work properly?
That would be strange...

[Ioannis]

Thanks Alain.

But with MCS does it compile OK?

Ioannis

[Acetronics2]

Thanks Alain.

But with MCS does it compile OK?

Ioannis

Hi, Ioannis

I've verified in real life ... my old programs Work fine, compiled With MCS.

Was not so evident due to little changes in the resulting HEX ...

Alain

[Terry]

Darrel,
In my PBP code the only assembly routine would be your code for the interrupt and I have no branch routines. My interrupt routine is in PBP, not assembly, but if is was, could this then be a possible issue. Also in searching this thread, I did see the possibly of inserting "@ errorlevel -306 " to suppress the warning, if this is a OK, where does it makes sense to insert it, such as right after the includes.
Thanks for your help,
Terry

[Darrel Taylor]

The ASM that declares Interrupts, will be OK because all the GOTO's and GOSUB's/CALLs in DT_INTS already use Paging code.

If the ISR is assembly language, there would be a possibility of page problems.
But if you use L?GOTO or L?CALL instead of goto or call, then it won't be a problem either.
They are macro's that are part of PBP and automatically set PCLATH to the correct page before jumping. They also reset to BANK0, so anywhere they jump to should assume the bank is currently 0.

The -306 line can technically be put anywhere in the program before the first Page Crossing. But it's usually found at the very top, right up there with your __CONFIG lines.
<br>

[Terry]

Many Thanks Darrel,
For your help now and for a GREAT easy to use approach for interrupts using PBP.
Terry

[Darrel Taylor]

BUT it seems the problem only Occurs with DT 18 Instant Interrupts ...

NOT TRUE!

As explained in the previous posts, the problem will happen with ANY program that uses PBP statements inside of macro's, when using MPLAB<hr>

Ioannis,
PBP 2.60 is really nice. And it works really well with Microcode Studio.

MPLAB is the problem. But trying to make PBP work with the new MPLAB, meLabs made a mistake, and now it causes new problems.

Don't wait, go ahead and get the upgrade, but forget about MPLAB.
<br>

[Acetronics2]

NOT TRUE!

As explained in the previous posts, the problem will happen with ANY program that uses PBP statements inside of macro's, when using MPLAB<hr>

<br>

Hi, Darrel

You should have understood :

It works with "DT_INTS-14.bas" ... but not with "DT_INTS-18.bas"

Its a pity to have also lost the PBP label NAMES ...

Alain

[Terry]

Darrel,
Quick question, off topic from the most recent posts. I am using a PIC16F876A part with the DT_INTS-14.bas and using a timer0 interrupt, everything works wonderful, many many thanks! but when my program size goes past the 2k size I get the message when compiling "Message[306] ... Crossing page boundary -- ensure page bits are set." while I know this is only a warning, my program seems to work fine, but I would like to double check, whether this is a concern or not.
Thanks,
Terry

[Darrel Taylor]

Hi Terry,

DT_INTS won't have any problems when it crosses page boundaries, and most normal PBP programs won't either.

But if the program uses the BRANCH command or has assembly language routines, it can be a problem.


Crossing Page Boundary - Solution
http://www.picbasic.co.uk/forum/showthread.php?t=40

Warning (and other Compilation Error) Messages (Melanie)
http://www.picbasic.co.uk/forum/showthread.php?t=555