PBP and PBPL

[Darrel Taylor]

.... don't be envious ... perhaps I tell you afterwords what I did during those 8 days...

WELLL.... make me turn green <hr />

The compiler doesn't actually look in the USB18 folder.

Any files in that folder that are needed for your program should be COPIED into the same folder as your project.

And your project should not be in the PBP folder. It should be in it's own separate folder somewhere else.

The macro not found error usually means that it's not finding LIBRARY "PBPUS18L" in the .bal file. If you haven't COPIED the .bal file from the USB18 folder into your project folder, then it finds the one in the PBP folder, which has the wrong library line commented.
<br>

[keymuu]

WELLL.... make me turn green <hr />

Green is one of the major colors of nature...

The compiler doesn't actually look in the USB18 folder.

Ok

Any files in that folder that are needed for your program should be COPIED into the same folder as your project.

I have learned that somewhere earlier... but ...

And your project should not be in the PBP folder. It should be in it's own separate folder somewhere else.

This is kind of new to me! I have known that that all (including your project) should be in the same in same folder, meaning all should be in C:\PBP. I was earlier wondering why MicroCode Studio has as default folder C:\Program Files\Mecanique\MCS ? Maybe this explains it then... and I should have copied things there instead of the contrary action... copying all to C:\PBP

The macro not found error usually means that it's not finding LIBRARY "PBPUS18L" in the .bal file. If you haven't COPIED the .bal file from the USB18 folder into your project folder, then it finds the one in the PBP folder, which has the wrong library line commented.
<br>

In the C:\PBP\USB18 folder I can only find PBPUS18L.LIB no other files with the name "PBPUS18L", and it looks like this:

;****************************************************************
;*  PBPUS18L.LIB                                                *
;*                                                              *
;*  Notice    : Copyright (c) 2007 microEngineering Labs, Inc.  *
;*              All Rights Reserved                             *
;*  Date      : 05/09/07                                        *
;*  Version   : 2.50                                            *
;*  Notes     : PIC18 USB library w/ longs                      *
;****************************************************************

        include "\PBP\PBPPI18L.LIB"
        goto MAINPROG
	include "USB18.INC"
	include	"USBDESC.ASM"	; Application specific descriptors
	include "USB18MEM.ASM"
	include	"USB18.ASM"

MAINPROG

Is that looking normal?

The same file is also in C:\PBP folder as well as
PBPUS18.MAC.
pbppic18.lib
pbppic18.mac
PBPPIC18.RAM
PBPUS18L.MAC
USB18.asm
USB18Mem.asm
usb18.inc
18F4550.bal
18F4550.BAS

The 18F4550.BAL looks like this:

'****************************************************************
'*  18F4550.BAL                                                 *
'*                                                              *
'*  By        : Leonard Zerman, Jeff Schmoyer                   *
'*  Notice    : Copyright (c) 2007 microEngineering Labs, Inc.  *
'*              All Rights Reserved                             *
'*  Date      : 05/09/07                                        *
'*  Version   : 2.50                                            *
'*  Notes     :                                                 *
'****************************************************************

BANKA   $0000, $005F
BANK0   $0060, $00FF
BANK1   $0100, $01FF
BANK2   $0200, $02FF
BANK3   $0300, $03FF
'BANK4   $0400, $04FF
'BANK5   $0500, $05FF
'BANK6   $0600, $06FF
'BANK7   $0700, $07FF
'EEPROM  $F00000, $F000FF
'LIBRARY "PBPPI18L"
LIBRARY "PBPUS18L"

        include "PIC18EXT.BAS"

PORTL   VAR     PORTB
PORTH   VAR     PORTC
TRISL   VAR     TRISB
TRISH   VAR     TRISC

        include "PBPPI18L.RAM"

'*-----------------------* EOF 18F4550.BAL *--------------------*

Is that looking ok?

I created a new folder C:\PBP\Proj where I copied all those files also with my project, so now something still are missing from folder "Proj" when getting those same four USBmacro errors. I can't figure out what is still missing.
What can be missing?

Can you see what is missing?

[mackrackit]

I can not help much with the USB problem, but I would store my projects in a directory some place other than a sub directory of PBP. C:\projects woud be good. Most of my projects are on a flash drive or a SD card to make it easy to move from machine to machine.

When you have projects in the PBP ditectory and it comes time to upgrade them you will have to go find all of your "stuff" before it is deleted or over written during the new install.

[keymuu]

I can not help much with the USB problem, but I would store my projects in a directory some place other than a sub directory of PBP. C:\projects woud be good. Most of my projects are on a flash drive or a SD card to make it easy to move from machine to machine.

When you have projects in the PBP ditectory and it comes time to upgrade them you will have to go find all of your "stuff" before it is deleted or over written during the new install.

Thanks Dave!

Really interesting. What you said is of course true and logical.

I moved all from C:\PBP\Proj to C:\PBProj and compiled again I got rid of those four errors and instead I got "too many errors" meaning four Error[126] \PBP\PBPPI18.LIB 722 : argument out of range (34218 not between 0 and 32767) and that line in .LIB file is "CALL Label", and that drills me, does that mean Label is too far away or what? If this is true, how can one correct that? This brings me back almost to square one

[Darrel Taylor]

argument out of range (34218 not between 0 and 32767)

That means your program is larger than the 32k bytes (16k words) available on the 4550.
<br>

[keymuu]

That means your program is larger than the 32k bytes available on the 4550.
<br>

Could that mean anything else?

When compiling with PBP (not PBPL) it is 28632 bytes and of course there can not be any longs yet involved when still struggling to get it compile with PBPL. Or, would PBPL build bigger code than PBP when not using VAR LONGs ?

[Darrel Taylor]

In PBPL, ALL system variables are LONGs. ALL intermediate math is done as LONGs. Even multiplying 2 bytes can use LONGs.

Longs take more code than words.
So a PBPL program will ALWAYS be larger than a PBPW program.
<br>