> Van: Martin Hill <eaxmjhi@NOTTINGHAM.AC.UK>
> Aan: PICLIST@MITVMA.MIT.EDU
> Onderwerp: Re: [PIC]: Code protection on 16C73B
> Datum: maandag 26 juni 2000 17:03

That would not really be a problem *if* we had the possibility to check the
*settings* ( adresses 0x2000 thru 0x200F) afterwards.  As in : having a
Write-protected, but *unscrambled* read of this area when the Read( / Write
?) -protect is set.

I do think that being able to protect my JW -chips from inadvertedly
enableing the Write-protect is a good idea.  Not being able to Read-protect
a OTP-chip is much less costly than Read-protect a JW -chip.  And a
(currently not possible) check afterwards of the configuration-data would
alert you if there was a Write-failure of the Read-protection-bit.

My 2 cents .....

Regards,
  Rudy Wieser

> I disagree,
>     If you had equal problems with this then you could end up sending
> out your valueable code to customers without any protection.
> Maybe some devices with NO code protection could be made
> available.
>
> Martin
>
> > MChip should provide a code-protect-protect-bit... so that one can
> > protect himself agains accidentally programming the code-protectbit <g>
> >
> > Regards,
> >
> > Jilles Oldenbeuving
> > jilles@rendo.dekooi.nl