Hi Olin and Jan-Erik,

It's strange -- my experience with the PIC10F200 and MPLAB IDE v6.62 has
been completely different. I'm not really disagreeing with both of you
here -- I'm just reporting my findings -- maybe it might help you -- maybe
not.

I just completed a small PIC10F200 project and was able to use the CONFIG
directive with no problems -- even with the PIC10F200 linker script file
that has an "error" in it. In addition, even when I import the HEX file into
MPLAB IDE, the configuration bits get set properly -- so at least it appears
that MPLAB IDE "knows" how to parse the HEX file for the configuration word
if this is indeed an oversight on Microchip's part.

I used the quotes in the word 'error' above because, although I 100% agree
that the programming specification indicates that the configuration word
address is 0x1FF for the PIC10F200/PIC10F204 and 0x3FF for the
PIC10F202/PIC10F206, MPLINK "barks" at you if you try to correct the linker
script file by adjusting the configuration word address to what is called
out in the programming specification for the particular PIC10F part in
question:

For example, if I try to correct the error in the linker script by using
this for the PIC10F200:

CODEPAGE   NAME=.config   START=0x1FF   END=0x1FF     PROTECTED

I get the following error:

----
MPLINK 3.80.03, Linker
Copyright (c) 2004 Microchip Technology Inc.
Error - section '.config' can not fit the absolute section. Section
'.config' start=0x00000fff, length=0x00000002
Errors    : 1

BUILD FAILED: Sun Nov 28 22:02:12 2004
----




I just tried a quick experiment and I did find a pretty *strange* error
message when I try to do the following however:

CONFIG  CODE

    __CONFIG    _MCLRE_OFF & _WDT_OFF & _CP_OFF


    END


The error message I get is:

-----
MPLINK 3.80.03, Linker
Copyright (c) 2004 Microchip Technology Inc.
Assertion failed: found, file ../../mplink/src/MemTarg.cpp, line 710

This application has requested the Runtime to terminate it in an unusual
way.
Please contact the application's support team for more information.
BUILD FAILED: Sun Nov 28 22:13:01 2004
----


'CONFIG' is a logical section name defined in the PIC10F200 linker script
file. If I comment out the 'CONFIG  CODE' part in the snippet above, the
error message goes away and all is fine. That's the only difference between
getting that error message or not getting it. I always just use the CONFIG
directive without encapsulating it within a CODE directive and an END
directive, but I wanted to try the experiment above. I'm not sure what is
considered better practice, but it would seem to me that the above snippet
would be better practice, but I cannot get it to work with MPASM/MPLINK. It
makes me wonder why Microchip includes a 'CONFIG' logical section name in
the linker script in the first place when the CONFIG directive works just
fine by itself...perhaps for the ability to get the address(es) of the
configuration word(s) for PICmicros that can programmatically read the
configuration word(s).


In any event, MPLAB IDE 7.0 is right around the corner and I'll be sure to
check out the PIC10F linker script files with that release. MPLAB IDE 7.0
was originally touted as being the release where component downloads is a
reality so that people would no longer need to download 30 something
megabytes.


Best regards,

Ken Pergola













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