There was a discussion regarding this a while back. I'd hazard to say any
code protection can be defeated given enough resources (that is, money and
time). It really boils down to how valuable your code is to someone else.
What magnitude of resources are worth investing in breaking the protection,
versus developing the code themselves.  In most cases I'd guess the built
in protection is adequate. IIRC, the old 'c84 was used in a smart card,
which prompted *lots* of effort to hack it (which succeeded) due to the
gains breaking the protection would yield.

So evaluate the value of your code. If you are paranoid, make the pic
difficult to identify (remove part numbers, etc.), or even better, make it
mechanically difficult to get to (ie, potting).

- Mike

At 07:43 PM 6/27/2003 -0400, you wrote:
>How secure is the code programmed into a PIC chip?  With "code protection"
>turned on, is the code truly protected or has someone somewhere figured out
>how to hack into it?
>
>--
>http://www.piclist.com hint: The list server can filter out subtopics
>(like ads or off topics) for you. See http://www.piclist.com/#topics

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.