Hello Scott,

> I believe that it's a bug in Microchip's assembly-language `.inc' file for
the
> 18F series.
>
> The include files are set up to construct a configuration byte value by
> `AND'-ing a series of options. This means that unimplemented bits (and
bytes)
> end up set to `1'. However they read as `0' when the software goes to
verify
> them, resulting in a discrepancy [ if you remove all unimplemented bits
then
> FEFF and 2600 are the same thing ].

    I think you're right.

> I manually edited the configuration words in PICALLW after the loading the
> program, to mask out the unimplemented bits, which works.

    I solved the problem using "#ROM 0x300000={0x2600, 0x000E, 0x0100,
0x0081, 0xC00F, 0xE00F, 0x400F}" instead of #FUSES. Probably the best
solution would be to change the ".inc" file ANDing all the values with just
the existing bits.

    Thanks,

    Brusque

-----------------------------------------------------------------
Edson Brusque                 C.I.Tronics Lighting Designers Ltda
Research and Development               Blumenau  -  SC  -  Brazil
Say NO to HTML mail                          www.citronics.com.br
-----------------------------------------------------------------

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email listserv@mitvma.mit.edu with SET PICList DIGEST in the body