Olin Lathrop a =E9crit :
> Obviously something is in the bits.  They have to be either 0 or 1.  I th=
ink
> they come from the factory in the erased state, which is 1.
>
>   =

It's possible, but it don't specified clearly in the datasheet.

> I can't think of a good need to expect the default to be anything in
> particular.  Always specify all config bits in the source code.  Any dece=
nt
> programmer can't rely on the PIC having come straight from manufacturing
> versus having been programmed to arbitrary values, so once you program in
> your firmware the original state becomes irrelevant.
>   =

I absolutely agree with you. I did it, but my subcontractor who =

programme chips and populate the pcb do bad job. I receive the cards =

with chips programmed on it, and 50% don't work. When I read the chip =

through ICD2 I can see all the programme memory, but it not possible =

because I specified the Code Protection Bit to ON. I suppose that the =

Configurations Bits are not programmed.

> If I really wanted to know I'd check the manaul, of course.
>   =

Be sure, I did it in the first place. But the default state of the =

configurations bits is not specified.
This is a 16F946.
page 220 of the datasheet =

http://ww1.microchip.com/downloads/en/DeviceDoc/41250F.pdf

Thank you all, for your responses. :)
-- =

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