PPA wrote:
> The MPLAB configuration bits dialog shows this bit set or reset in the
> result column but it cannot be changed from here.

You should never set configuration bits there anyway.  Think of that dialog
as read-only.  Always set the configuration bits in the code.  That way they
end up in the HEX file, and are documented.

> My problem is that I do not use MPLAB, but I use MPASM/MPLINK & PK2
> from
> another tool, so the DEBUG bit is cleared by default (0 is ON, too
> bad) and
> the device crashes (do not start?) as expected and I cannot find any
> way to
> build a project with this bit set...

It's just a bit.  You can set it any way you like in your code.  Remember,
the fancy __CONFIG and CONFIG directives and the mnemonics in the processor
include file are just convenience wrapper.  I never use the bit mnemonics
because they make it too difficult to document each bit and give a idea of
the available choices.  Your tools still let you write "0" and "1", right?

> Why this bit has vanished from datasheets / .inc files but is still
> functioning as expected?

Sometimes Microchip screws up.  This kind of screwup is actually quite rare,
but I've very occasionally seen a mismatch between the datasheet and the
name of a bit in the include file.  It happens.  Report it, and it will
probably be fixed in the next rev of the datasheet.  Make sure you're right
before reporting it though.


********************************************************************
Embed Inc, Littleton Massachusetts, http://www.embedinc.com/products
(978) 742-9014.  Gold level PIC consultants since 2000.
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist