Error 115 - Duplicate label

[ChrisKiwi]

Yeah, there's probably some sort of conflict between the definitions in the PBP inc file and MPASM inc file. Since the #header block is passed directly to the assembler I'm guessing that the ASM inc file ALSO includes a line defining ("aliasing") SPBRG as SPBRGL - but that's just a guess.
/Henrik.

Your comments got me thinking further so I downloaded the "Full" version of PBP3 and installed MPLAB 8.9 and got my code to compile and run with out commenting out the line in the PBPINC file. I compared the Microchip INC files and found that MPSAM 5.49 that installed from the full PBP3 download only had entries for SPBRGL and SPBRGH while MPASM 5.56 (Installed with MPLAB-X) had SPBRG (the offending one) SPBRGL and SPBRGH. The data sheet for the pic refers to SPBRGL and SPBRGH as 2 8 bit registers but refers to SPBRG as the combined value of the 2 registers. In the MPASM 5.56 inc file (MPLAB-X) SPBRG and SPBRGL have the same address, so in effect that is saying that SPBRG abd SPBRGL are the same thing, thus, you are defining the same thing twice or in different places (as per the error message) when you are using MPLAX-X with MPASM 5.56 and PBP3 but not when you are using the older version of MPLAB with MPASM 5.49 and PBP3. My solution is to comment out the line out in the PBP3 .PBPINC file on the basis that I think PBP3 should be compatible to MPASM, rather than the other way round. I wonder if this could be considered a "bug" ? - which came first - the chicken or the egg? Chris

[HenrikOlsson]

Hi,
Yey, so my guess was spot on then

My solution is to comment out the line out in the PBP3 .PBPINC file on the basis that I think PBP3 should be compatible to MPASM

I agree, though one could argue that PBP3 was, and still is, compatible with the version of MPASM available at the time of release and with the version available and included in the PBP3 download package.
Then Microchip decides to change things at their end (or possibly fixing a potential isssue that PBP3 provided a workaround for) resulting in an incompatibillity issue between the different versions.

It kind of sucks that Mecanique (if that's where you got MCSP) didn't want to help you recover the license. I'd try speaking to MELABS and see if they can help you. If you got it prior to PBP3 you'd need to upgrade it anyway.

/Henrik.