Steve: This is a good idea of placing a global copy-protect disable in
     the software; much easier than changing the silicon.

     However, I should point out that CUSTOMERs are often the people that
     you want to protect the device from. Ie, you are a small developer
     working for Honcho Technology and send hem your working prototype.
     They read out your code and sever the contract. It could happen.

     In this case, it is usually better to include the price of a couple
     OTPs in the contract...

     Norm LeMieux
     MCHIP FAE/NW



     Steve Miller wrote:

     Several good suggestions have been offered for this problem.  Here is
     my
     two cents.  The cheapest thing to change is software.  I would
     interested
     in a programming suite of tools geared specifically at the development
     environment.  I would like programming software that does not allow
     the
     protection bits to be set ever.  This development software would never
     code protect a part.  During development we could use this safe
     version,
     for customer prototypes and production we could use full featured
     programming software.

     Here is an opportunity for all the folks writing programmer software.
      Make us a version that will never intentionally set the code protect
     bits.  I would gladly pay the cost of a few JW packages just to be
     sure
     that I did not choose the wrong option.  I know that programming
     errors
     can occasionally inadvertantly code protect a part.  However,  if we
     can
     eliminate operator error, I think we can save quite a lot of chips!


      ------ Steve