Here's a weird bug I encountered this week on MPLAB 8.14. I was roughing 
in a new project and found that naked udata and code directives (with no 
subsequent info) give me an "invalid n_scnum" cof linker error. Example 
- in reserving RAM regions I had the following statements:

BANK2_VARS    udata    0x120
BANK3_VARS    udata    0x190

This gave me the following message:

MPLINK 4.21, Linker
Copyright (c) 2008 Microchip Technology Inc.
Error - Coff file 'Controller.cof' symbol[232] has an invalid n_scnum.
Error - Internal Coff output file is corrupt.
Errors    : 2

The following statement eliminates the error:

BANK2_VARS    udata    0x120
LABEL_2
BANK3_VARS    udata    0x190


This also occurs if I leave a code directive at the end:

EERAM    CODE    0x2100            ; 256 bytes of eeram
; DUMMY_LABEL   ; corrects n_scnum problem
                END

Inserting a label also solves the problem. Perhaps this is a known 
problem and I just haven't encountered it. Perhaps this just me using 
absolute mode. I have reported the bug and the workaround to Microchip 
support.

Alden


Xiaofan Chen wrote:
> http://forum.microchip.com/tm.aspx?m=376355&mpage=2
>
> I think temporally it is better to avoid MPLAB 8.15 is you are
> using Geman version of Windows.
>
> Or if can use other keyboard layout while inputting German
> symbols (maybe the only problem is those special symbols).
>
> It seems that V8.xx version of MPLAB is plagued with
> many problems for various reasons.
>
> Xiaofan
>   

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist