Another PBP 2.60 Surprise ...

[Acetronics2]

Executing: "C:\Program Files\Microchip\MPLAB IDE\PBP\PBPMPLAB.BAT" -ampasmwin -k# -p16F628 "gasbrain.bas"
Executing: "C:\Program Files\Microchip\MPLAB IDE\PBP\PBPW.EXE" -ampasmwin -k# -p16F628 "gasbrain.bas"
PICBASIC PRO(TM) Compiler 2.60, (c) 1998, 2009 microEngineering Labs, Inc.
All Rights Reserved.
Message[301] C:\PROGRAM FILES\MICROCHIP\MPLAB IDE\PBP\16F628.INC 23 : MESSAGE: ( Pensez à la Bonne Config !!!)
Message[301] C:\PROGRAM FILES\MICROCHIP\MPLAB IDE\PBP\16F628.INC 24 : MESSAGE: ( Pensez à la Bonne Config !!!)
Message[301] C:\PROGRAM FILES\MICROCHIP\MPLAB IDE\PBP\16F628.INC 25 : MESSAGE: ( Pensez à la Bonne Config !!!)
Message[306] C:\PROGRAM FILES\MICROCHIP\MPLAB IDE\PBP\PBPPIC14.LIB 743 : Crossing page boundary -- ensure page bits are set.
Warning[220] C:\PROGRAM FILES\MICROCHIP\MPLAB IDE\PBP\PBPPIC14.LIB 743 : Address exceeds maximum range for this processor.

Loaded C:\Program Files\Microchip\MPLAB IDE\Projets\gasbrain.COF.
BUILD SUCCEEDED: Sun Aug 23 16:20:23 2009




Nothing strange ???

Here , we are at the far end of the PBP program ... END statement exactly.

SLEEP is line 2048

BUT

GOTO SLEEP which should have been line ... 2049 has been cut away ...

Just a Warning ...

So, NEVER forget the END Statement !!!

Alain

[Darrel Taylor]

So, NEVER forget the END Statement !!!
I must be missing the point again ...

According to the error's, the program is crossing the page boundary, and the 16F628 only has 1 page.

How could there be anything at 2048/2049?
<br>

[Acetronics2]

I must be missing the point again ...

According to the error's, the program is crossing the page boundary, and the 16F628 only has 1 page.

How could there be anything at 2048/2049?
<br>

Hi, Darrel

Seriously ... That's THE Good Question :

Build Succeeded, but ASM generated is more than the allowed program memory ... and truncated.

No "Succeed" should arise ...

Alain

[Charles_Leo]

My testing indicates that Microchip's MPASMWIN assembler does produce hex and coff files even though the program exceeds the available code space. The program is truncated when this is the case. It does generate a warning message, but the "Build Succeeded" result is a bit misleading.

As for the reason that the program grew when compiled with 2.60, I will be happy to investigate if you will post your program or send it directly to the support address at melabs.

One of the common causes for larger code with 2.60 is the change we made to the READ and WRITE commands. This causes the commands to use more code space when many READs and WRITEs are used to handle individual bytes, but can be made more efficient if the new features are utilized to write multiple bytes with single commands.

[Acetronics2]

Hi, Charles

Program sent ...

And Prog memory Overflow verified ...

Alain