Lpc2000

Ultimately it is impossible to totally protect code. Perhaps the best 
you can prove is that somebody actually ripped you off. I routinely 
embed a copyright notice that is encrypted. The notice is functional, 
working code that cannot be removed easily. Does not appear as any kind 
of sensible ASCII, yet is revealed by a simple key. I also repeat the 
same messages in plain text. Which may help to reveal 'holes' in the 
memory map.

Al

ggindele wrote:

> 
> I think we reached the consensus (with a little Philips help) that
> code protection is available only in the 64 pin package, when the boot
> loader >= 1.63
> 
> I wonder would that be a commercially reasonable protection when 2106
> is used with an external electronic serial number. The flash can be
> customized to accept only the right serial number, but there's no code
> protection against JTAG attack.
> 
> What do you think? How long would it hold?
> 
> 
> 
> 
> 
> 
> Yahoo! Groups Sponsor
> ADVERTISEMENT
> <http://us.ard.yahoo.com/SIG=1297p65qp/M=298184.5639630.6699735.3001176/D=groups/S=1706554205:HM/EXP=1103742242/A=2495208/R=0/SIG=11egg01lg/*http://www.netflix.com/Default?mqso=60188914>
> 
> 
> ------------------------------------------------------------------------
> Yahoo! Groups Links
> 
>     * To visit your group on the web, go to:
>       http://groups.yahoo.com/group/lpc2000/
>        
>     * To unsubscribe from this group, send an email to:
>       lpc2000-unsubscribe@yahoogroups.com
>       <mailto:lpc2000-unsubscribe@yahoogroups.com?subject=Unsubscribe>
>        
>     * Your use of Yahoo! Groups is subject to the Yahoo! Terms of
>       Service <http://docs.yahoo.com/info/terms/>. 
> 
>