Yahoo Groups archive

Lpc2000

Index last updated: 2026-04-28 23:31 UTC

Message

Re: FLASH Security

2005-12-14 by philips_apps

Your understanding of the LPC2000 flash security is right for the
LPC2104/2105/2106 as they exist today but wrong for any other LPC2000
subfamily as all the 64-pin and 144 pin devices and also the new
LPC2101/02/03 have Flash Security.

As Joel already pointed out in the respective User Manuals you will
find a section about code security, you don't find it in the
LPC2104/5/6 as they do not have the code security YET. 

SUMMARY: All LPC2000 excep the 2104/5/6 offer Flash Security option.

Robert

--- In lpc2000@yahoogroups.com, "jayasooriah" <jayasooriah@y...> wrote:
>
> My understanding is that LPC series do not offer any code protection
> like that in PICs or AVRs.  I know that for AVRs, you can preload the
> boot sector, lock it down, and ship the part to customers.  Customers
>  can load their code, run your code in boot sector, but still would
> not be able to read any of your code.  There is no way to do this on
> for LPC series.
> 
> Philips's idea of boot sector protection (from erasure) is hiding of
> flash progamming algorithms and providing IAP code that in the boot
> sector which will block attempts to erase or write to boot sector.
> 
> If you look at the boot loader code, say for LPC2104, upon reset,
> memory location 0x3fff8000 is witten with the part ID.  I suspect if
> you are using JTAG, this is what gets returned as the JTAG IDENT. If
> your setup can proceed even when the IDENT command does not return the
> expected value, I suspect nothing else will stop you from reading
> contents of flash.
> 
> --- In lpc2000@yahoogroups.com, "James Dabbs" <jdabbs@t...> wrote:
> >
> > Do any of the LPC series have FLASH security on par with PICs and
AVRs?
> > Or can you always just put a JTAG unit on it and copy out the memory?
> > 
> > Thanks.
> >
>

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.