PBP 2.6/MPLab 8.33 ASM "COD" error message

[reddog24]

Compile generates:
Executing: "C:\PROGFILE\pbp\PBPMPLAB.BAT" -ampasmwin -oq -z -p16F690 "BLINK_16f690.BAS"
Executing: "C:\PROGFILE\pbp\PBPW.EXE" -ampasmwin -oq -z -p16F690 "BLINK_16f690.BAS"
PICBASIC PRO(TM) Compiler 2.60, (c) 1998, 2009 microEngineering Labs, Inc.
All Rights Reserved.

ERROR: Unable to access file D:\My Documents\PicBasicTrials\Blink\Blink_16F690\BLINK_ 16f690.COD
Error processing COD file D:\My Documents\PicBasicTrials\Blink\Blink_16F690\BLINK_ 16f690.COD
Halting build on first failure as requested.
BUILD FAILED: Sat Jul 25 16:14:42 2009

The project folder does not have a "blink_16f690.cod" file but has .asm, .mac, .err, .hex,.lst.

Path has the mpasmwin path, C:\Program Files\Microchip\MPASM Suite\

Installed "upgrade" into default directories and the MPASM & mePicBasic Pro toolsuite locations seem OK.

Why is the .cod file missing?

[Melanie]

Can you reduce the filename of BLINK_16f690 to 8 Characters or less eg BLINK001 and see what happens?

I've had problems with long filenames in the past (albeit I only compile from an XP DOS Box command line rather than from inside another program).

[BrianT]

See the Melabs web page http://www.melabs.com/support/index.htm

Technical Support

(01/26/2009) Microchip's MPLAB version 8.15a appears to be the last version that will support COD file functionality. This means that PBP will generate errors in MPLAB version 8.20 and later. The errors appear as:

ERROR: Unable to access file...
Error processing COD file...


We will be releasing a new version of PBP with COFF file compatibility in response to this surprise move by Microchip. In the meantime, MPLAB version 8.15a is available for download here:

Download MPLAB 8.15a (93M ZIP)


--------------------------------------------------------------------------------

[mackrackit]

See the Melabs web page http://www.melabs.com/support/index.htm

They did not fix that with 2.6PBP ?

[BrianT]

Latest available PBP is ver 2.50c as far as I can tell.

Cheers
Brian

[mackrackit]

Latest available PBP is ver 2.50c as far as I can tell.

Cheers
Brian
For some reason Melabs is not advertising it. But....
http://www.rentron.com/PicBasic/products/PICBASIC-PRO.htm

[Charles_Leo]

I would guess that there is a problem in your build options, or perhaps the new PBP plugin hasn't registered correctly. The executed command line should not have a "-z" in it, and MPLAB should not be trying to load a COD file. PBP 2.60 should allow you to use MPLAB 8.33.

Go to the Build Options for the project's program file and make sure it looks like the attached screenshot. If it doesn't show the same options (the plugin is old), go to Start > All Programs > PICBASIC PRO Compiler and click on "Install MPLAB Plugin". On Windows Vista and Windows 7 systems, you may need to right-click and select "Run As Administrator". Report any errors that you receive. Restart MPLAB afterwards.

As Melanie mentioned, there is a length limit when passing filenames to MPASMWIN, but it is the total number of characters in the path and filename that is the problem. I believe the limit is 63 characters. In your case, the subject of this limit is the string "D:\My Documents\PicBasicTrials\Blink\Blink_16F690\BLINK_ 16f690.ASM". I'm not sure why you don't receive an error before assembly, but this could be because of the build options setting that is suppressing the MPASMWIN progress bar (-oq). In any case, you might move your project folder closer to the root of the drive - "D:\PBPTrials\Blink_16F690\"

[reddog24]

Tnx Charlie for response; Running "MPLAB Plugin" that registers the PBPSUITE.dll and sets up MPLAB to run PBPMPLAB.BAT, adjusting the MPLAB project options per your thumbnail, and running PBRegister fixed the problem.

[FutureFAE]

The PBPMPLAB.BAT file does not seem to want to run, even when run as administrator.

The error message is as follows for running the "Install MPLAB plugin":

"The module "C:\PBPDEMO\PBPSUITE.DLL" faild to load. Make sure the binary is stored at the specified path or debug it to check for problems with the binary or dependant .DLL files. The application has fialed to start because it's side-by-side configuration is incorrect. Please see the applicaiton ecent log for more detail."

When I tried to run it from the command line, I get:

"The module "PBPSUITE.DLL" was loaded but the call to DllRegisterServer failed to load with error code 0x80070005. For more information about this problem, search online using the error code as a search term."

The configuration I was trying to run was MPLAB 8.36, and PBP v2.60, and windows Vista Home Premium.

[Darrel Taylor]

It looks like it's pointing to an old Demo version of PBP.
Try the instructions to the right of the first image on this page ...

http://www.melabs.com/support/mplab.htm
<br>