Instant Interrupts - Revisited

[Darrel Taylor]

No wonder I don't like MPLAB.

The problem seems to have something to do with the -k# command line option. (new option for pbp2.60)
If I use the same batch file that MPLAB uses ... PBPMPLAB.BAT
Then this command gives me the same errors you reported.

c:\PIC\PBP260\PBPMPLAB.BAT -ampasmwin -k# -p18F452 "Tracteur.bas"

If I remove the -k# option it compiles fine.

I haven't found a way to remove it from within MPLAB.
And I think if you did, you wouldn't be able to debug in MPLAB.

Added: In the PBP manual it only shows -k- and -k+. -k# doesn't even seem to be a valid option.
Not that it matters much, because it fails with either -k- or -k+ too.

[Darrel Taylor]

I see exactly what's happening now.
This is one for meLabs to solve.

In an attempt to produce the COFF information for debugging with MPLAB, ... PBP with the -k option places Z????? Labels on every line of code ... including the "ASM" or @ lines.

If the program has any ASM macros in it (like DT_INTS), you can normally jump in and out of ASM anytime you need to within that macro.

But with it putting labels at the "ASM" statements, ... when those macros get used (more than once) it duplicates labels that were not in the original program.

For instance with this macro ...

ASM
MyMacro  macro
   ; asm statements here
  ENDASM
   ; PBP statements here
  ASM  ; This statement creates a label in the middle of a macro.
  endm
ENDASM

@ MyMacro  ; The first time it's used is OK
@ MyMacro  ; the second time or more duplicates that label

I'll send a report to support at melabs.com

[Darrel Taylor]

OMG!

If it's making a label for every PBP statement.
Then ANY PBP statements in a macro will cause the same error.

Apparently, every program I've ever written is now useless.
Well, (with MPLAB).
<br>

[Acetronics2]

If I remove the -k# option it compiles fine.

.

Hi darrel ...

YES ... but BUILD fails ... no HEX generated, halas.

Bouhouuuuu ...

Alain

[Ioannis]

I am still at 2.50c and although I have an itch to upgrade to 2.60 I do no think I'll do it now.

Darrel, If one uses MCS to edit and complile (with MPASM assembler) is there a problem?

Ioannis

[mackrackit]

Am I following this correctly?
The problem is not with the new PBP it is with the new MPLAB?
Does it work with the MPLAB that we used with PBP 2.5?

[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

[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